From f6af52e45363a2769f1f82792644836d90b03783 Mon Sep 17 00:00:00 2001 From: Kevin Duret Date: Fri, 13 Dec 2024 13:03:51 +0100 Subject: [PATCH] chore(doc): migrate to docusaurus v3 (#3808) * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * feat(doc): migrate to docusaurus v3 * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * fix zoom * remove backslash from inline code * remove backslash from inline code * remove backslosh from coeblocks * remove backslosh from coeblocks * remove backslosh from coeblocks * Update poller-troubleshoot.md * Update poller-troubleshoot.md * Update poller-troubleshoot.md * Update using-packages.md * Update using-packages.md * Update using-packages.md * Update using-packages.md * Update using-packages.md * Update using-packages.md --------- Co-authored-by: cg-tw <83637804+cg-tw@users.noreply.github.com> --- .github/workflows/archive.yml | 26 +- .github/workflows/clean-cache.yml | 34 + .github/workflows/documentation.yml | 66 +- README.md | 20 +- babel.config.js | 3 - .../notif-configuration.md | 14 +- .../alerts-notifications/resources-status.md | 2 +- cloud/installation/poller-troubleshoot.md | 10 +- docusaurus.config.js | 57 +- .../notif-configuration.md | 14 +- .../alerts-notifications/resources-status.md | 2 +- .../installation/poller-troubleshoot.md | 10 +- .../current/service-mapping/ba-management.md | 2 +- .../how-to-guides/troubleshooting-plugins.md | 8 +- .../windows-winrm-wsman-tutorial.md | 23 +- .../procedures/applications-ansible-tower.md | 42 +- .../applications-antivirus-clamav-ssh.md | 30 +- .../applications-antivirus-kaspersky-snmp.md | 2 +- ...tions-antivirus-skyhigh-webgateway-snmp.md | 2 +- .../procedures/applications-awa-jmx.md | 2 +- .../procedures/applications-bluemind-ssh.md | 2 +- .../applications-cisco-ssms-restapi.md | 14 +- ...pplications-commvault-commserve-restapi.md | 50 +- .../applications-databases-elasticsearch.md | 22 +- .../applications-databases-firebird.md | 2 +- .../applications-databases-influxdb.md | 16 +- .../applications-databases-informix-snmp.md | 14 +- .../applications-databases-informix.md | 2 +- .../applications-databases-mongodb.md | 18 +- .../applications-databases-mssql.md | 20 +- .../applications-databases-mysql.md | 54 +- .../applications-databases-oracle.md | 46 +- .../applications-databases-postgresql.md | 2 +- .../applications-databases-redis.md | 18 +- .../applications-databases-sap-hana.md | 2 +- ...applications-databases-warp10-sensision.md | 2 +- .../procedures/applications-docker-restapi.md | 20 +- .../procedures/applications-docker-ssh.md | 10 +- .../applications-dynamics-ax-mssql.md | 2 +- .../applications-eclipse-mosquitto-mqtt.md | 12 +- .../applications-google-workspace-api.md | 4 +- .../applications-gorgone-restapi.md | 2 +- .../procedures/applications-grafana-api.md | 12 +- .../procedures/applications-haproxy-snmp.md | 2 +- .../applications-hashicorp-vault-restapi.md | 10 +- .../procedures/applications-hddtemp-tcp.md | 2 +- .../applications-infor-ion-grid-restapi.md | 22 +- .../procedures/applications-ipfabric-api.md | 10 +- .../procedures/applications-jmeter.md | 2 +- .../applications-keepalived-snmp.md | 10 +- .../procedures/applications-lmsensors-snmp.md | 2 +- .../applications-microsoft-dhcp-snmp.md | 8 +- .../applications-monitoring-alyvix-restapi.md | 4 +- ...pplications-monitoring-centreon-central.md | 10 +- ...plications-monitoring-centreon-database.md | 2 +- ...monitoring-centreon-map-engine-actuator.md | 2 +- .../applications-monitoring-centreon-mbi.md | 4 +- ...applications-monitoring-centreon-poller.md | 12 +- ...cations-monitoring-centreon-sql-metrics.md | 2 +- ...ions-monitoring-iplabel-newtest-restapi.md | 2 +- ...applications-monitoring-kadiska-restapi.md | 2 +- .../applications-monitoring-loggly-restapi.md | 2 +- ...ications-monitoring-node-exporter-linux.md | 2 +- ...ations-monitoring-node-exporter-windows.md | 10 +- .../applications-monitoring-quanta-restapi.md | 2 +- .../applications-monitoring-scom-restapi.md | 14 +- .../applications-monitoring-speedtest.md | 2 +- .../applications-monitoring-splunk-api.md | 26 +- .../applications-mulesoft-restapi.md | 4 +- .../procedures/applications-netbackup-ssh.md | 2 +- .../procedures/applications-openldap-ldap.md | 2 +- .../procedures/applications-openvpn-omi.md | 2 +- .../applications-openweathermap-restapi.md | 2 +- .../procedures/applications-oracle-ovm-api.md | 32 +- .../procedures/applications-pacemaker-ssh.md | 44 +- .../applications-pfsense-fauxapi.md | 12 +- .../applications-protocol-bgp-snmp.md | 12 +- .../procedures/applications-protocol-cifs.md | 28 +- .../procedures/applications-protocol-dns.md | 2 +- .../procedures/applications-protocol-ftp.md | 2 +- .../procedures/applications-protocol-http.md | 46 +- .../procedures/applications-protocol-ldap.md | 4 +- .../applications-protocol-modbus.md | 2 +- .../procedures/applications-protocol-ntp.md | 2 +- .../procedures/applications-protocol-ospf.md | 20 +- .../applications-protocol-radius.md | 2 +- .../procedures/applications-protocol-sftp.md | 28 +- .../procedures/applications-protocol-smtp.md | 2 +- .../procedures/applications-protocol-snmp.md | 16 +- .../procedures/applications-protocol-ssh.md | 2 +- .../procedures/applications-protocol-tcp.md | 8 +- .../applications-protocol-telnet.md | 10 +- .../procedures/applications-protocol-x509.md | 14 +- .../procedures/applications-pvx-restapi.md | 2 +- .../applications-rapidrecovery-snmp.md | 30 +- .../procedures/applications-redis-sentinel.md | 6 +- .../procedures/applications-rrdcached.md | 10 +- .../procedures/applications-rubrik-restapi.md | 50 +- .../procedures/applications-rudder-restapi.md | 2 +- .../applications-sahipro-restapi.md | 16 +- ...lications-sailpoint-identitynow-restapi.md | 10 +- .../applications-salesforce-restapi.md | 4 +- .../procedures/applications-sccm-nsclient.md | 4 +- .../procedures/applications-slack-restapi.md | 4 +- .../procedures/applications-tosca-restapi.md | 10 +- .../applications-trendmicro-iwsva-snmp.md | 10 +- .../procedures/applications-veeam-nrpe.md | 60 +- .../applications-veeam-nsclient-05-restapi.md | 60 +- .../applications-veeam-vbem-restapi.md | 12 +- .../procedures/applications-veeam-wsman.md | 60 +- .../applications-vernemq-restapi.md | 26 +- .../applications-vmware-vcsa-restapi.md | 16 +- .../applications-voip-3cx-restapi.md | 22 +- .../procedures/applications-wazuh-restapi.md | 18 +- .../applications-webservers-iis-restapi.md | 24 +- ...lications-webservers-nginx-serverstatus.md | 18 +- ...plications-webservers-tomcat-webmanager.md | 2 +- .../plugin-packs/procedures/base-generic.md | 2 +- .../procedures/cloud-aws-apigateway.md | 2 +- .../procedures/cloud-aws-backup.md | 2 +- .../procedures/cloud-aws-billing.md | 2 +- .../procedures/cloud-aws-cloudfront.md | 2 +- .../procedures/cloud-aws-cloudwatch.md | 10 +- .../procedures/cloud-aws-cloudwatchlogs.md | 14 +- .../procedures/cloud-aws-directconnect.md | 18 +- .../plugin-packs/procedures/cloud-aws-ebs.md | 2 +- .../plugin-packs/procedures/cloud-aws-ec2.md | 26 +- .../plugin-packs/procedures/cloud-aws-efs.md | 2 +- .../procedures/cloud-aws-elasticache.md | 2 +- .../plugin-packs/procedures/cloud-aws-elb.md | 2 +- .../plugin-packs/procedures/cloud-aws-fsx.md | 2 +- .../procedures/cloud-aws-kinesis.md | 2 +- .../procedures/cloud-aws-lambda.md | 2 +- .../plugin-packs/procedures/cloud-aws-rds.md | 10 +- .../plugin-packs/procedures/cloud-aws-s3.md | 2 +- .../plugin-packs/procedures/cloud-aws-ses.md | 2 +- .../plugin-packs/procedures/cloud-aws-sns.md | 2 +- .../plugin-packs/procedures/cloud-aws-sqs.md | 2 +- .../procedures/cloud-aws-transitgateway.md | 2 +- .../plugin-packs/procedures/cloud-aws-vpn.md | 2 +- .../cloud-azure-analytics-eventhubs.md | 4 +- .../procedures/cloud-azure-compute-aks.md | 18 +- .../cloud-azure-compute-functions.md | 18 +- .../cloud-azure-compute-virtualmachine.md | 6 +- .../cloud-azure-database-cosmosdb.md | 18 +- .../cloud-azure-database-elasticpool.md | 2 +- .../cloud-azure-database-mariadb.md | 2 +- .../procedures/cloud-azure-database-mysql.md | 2 +- .../cloud-azure-database-postgresql.md | 2 +- .../procedures/cloud-azure-database-redis.md | 18 +- .../cloud-azure-database-sqldatabase.md | 18 +- ...cloud-azure-database-sqlmanagedinstance.md | 18 +- .../cloud-azure-database-sqlserver.md | 12 +- .../cloud-azure-datafactory-factories.md | 2 +- .../cloud-azure-management-costs.md | 2 +- .../cloud-azure-management-monitor.md | 2 +- .../cloud-azure-management-recovery.md | 2 +- .../cloud-azure-management-resource.md | 14 +- .../cloud-azure-network-networkinterface.md | 14 +- .../cloud-azure-network-publicip.md | 4 +- .../cloud-azure-network-virtualnetwork.md | 2 +- .../cloud-azure-network-vpngateway.md | 6 +- ...cloud-azure-policyinsights-policystates.md | 2 +- .../procedures/cloud-cadvisor-api.md | 2 +- .../procedures/cloud-kubernetes-api.md | 94 +- .../cloud-microsoft-office365-exchange.md | 10 +- .../cloud-microsoft-office365-management.md | 36 +- .../cloud-microsoft-office365-onedrive.md | 2 +- .../cloud-microsoft-office365-sharepoint.md | 2 +- .../cloud-microsoft-office365-skype.md | 2 +- .../cloud-microsoft-office365-teams.md | 2 +- .../procedures/cloud-prometheus-api.md | 16 +- .../cloud-prometheus-kubernetes-api.md | 44 +- .../cloud-vmware-velocloud-restapi.md | 28 +- .../procedures/hardware-ats-apc.md | 10 +- .../procedures/hardware-ats-eaton-snmp.md | 6 +- .../hardware-device-gorgy-ntpserver-snmp.md | 26 +- .../hardware-devices-abb-cms700-snmp.md | 2 +- .../hardware-devices-camera-avigilon-snmp.md | 32 +- .../hardware-devices-camera-optelecom-snmp.md | 32 +- ...ware-devices-hms-netbiter-argos-restapi.md | 8 +- ...re-devices-pexip-infinity-managementapi.md | 4 +- .../hardware-devices-polycom-dma-snmp.md | 4 +- .../hardware-devices-video-appeartv-snmp.md | 14 +- .../hardware-kvm-avocent-acs-8000-snmp.md | 14 +- .../procedures/hardware-pdu-apc-snmp.md | 20 +- .../procedures/hardware-pdu-clever-snmp.md | 2 +- .../hardware-pdu-cyberpower-snmp.md | 34 +- .../procedures/hardware-pdu-eaton-snmp.md | 26 +- .../procedures/hardware-pdu-emerson-snmp.md | 22 +- .../procedures/hardware-pdu-gude-epc-snmp.md | 14 +- .../procedures/hardware-pdu-raritan-snmp.md | 2 +- ...ardware-pdu-schleifenbauer-gateway-snmp.md | 2 +- ...hardware-printers-standard-rfc3805-snmp.md | 28 +- .../procedures/hardware-sensors-akcp-snmp.md | 2 +- .../procedures/hardware-sensors-apc-snmp.md | 2 +- .../hardware-sensors-comet-p8000-snmp.md | 2 +- .../procedures/hardware-sensors-geist-snmp.md | 2 +- .../hardware-sensors-hwgste-snmp.md | 2 +- .../hardware-sensors-jacarta-snmp.md | 4 +- .../hardware-sensors-netbotz-snmp.md | 2 +- .../hardware-sensors-rittal-cmc3-snmp.md | 24 +- .../hardware-sensors-sensorip-snmp.md | 2 +- .../hardware-sensors-sensormetrix-em01-web.md | 2 +- ...sensors-serverscheck-sensorgateway-snmp.md | 2 +- .../hardware-servers-cisco-ucs-snmp.md | 40 +- .../hardware-servers-dell-idrac-snmp.md | 14 +- .../hardware-servers-hp-ilo-xmlapi.md | 2 +- .../hardware-servers-hp-oneview-restapi.md | 16 +- .../procedures/hardware-servers-hp-snmp.md | 2 +- .../hardware-storage-adic-tape-snmp.md | 2 +- .../hardware-storage-avid-isis-snmp.md | 10 +- .../hardware-storage-bdt-multistak-snmp.md | 2 +- .../hardware-storage-datacore-api.md | 8 +- .../hardware-storage-dell-compellent-api.md | 2 +- .../hardware-storage-dell-compellent-snmp.md | 10 +- .../hardware-storage-dell-md3000-smcli.md | 2 +- ...ardware-storage-emc-clariion-navisphere.md | 2 +- .../hardware-storage-emc-datadomain-snmp.md | 76 +- ...hardware-storage-fujitsu-eternus-dx-ssh.md | 6 +- .../hardware-storage-hitachi-hnas-snmp.md | 32 +- .../hardware-storage-hitachi-standard-snmp.md | 2 +- .../hardware-storage-hp-3par-ssh.md | 120 +- .../hardware-storage-hp-lefthand-snmp.md | 12 +- .../hardware-storage-hp-msa2000-snmp.md | 10 +- .../hardware-storage-hpe-primera-restapi.md | 20 +- .../hardware-storage-ibm-ds3000-smcli.md | 2 +- .../hardware-storage-ibm-ds4000-smcli.md | 2 +- .../hardware-storage-ibm-ds5000-smcli.md | 2 +- .../hardware-storage-ibm-storwize-ssh.md | 14 +- .../hardware-storage-ibm-ts3100-snmp.md | 2 +- .../hardware-storage-ibm-ts3200-snmp.md | 2 +- .../hardware-storage-lenovo-sseries-snmp.md | 10 +- .../hardware-storage-netapp-ontap-restapi.md | 62 +- ...dware-storage-netapp-santricity-restapi.md | 4 +- ...orage-purestorage-flasharray-v2-restapi.md | 10 +- .../hardware-storage-purestorage-snmp.md | 2 +- .../procedures/hardware-storage-qnap-snmp.md | 30 +- .../hardware-storage-quantum-scalar-snmp.md | 2 +- .../hardware-storage-synology-snmp.md | 10 +- .../hardware-storage-wd-nas-snmp.md | 10 +- .../hardware-telephony-alcatel-oxe-snmp.md | 2 +- .../procedures/hardware-ups-alpha-snmp.md | 20 +- .../procedures/hardware-ups-apc-snmp.md | 46 +- .../hardware-ups-cyberpower-snmp.md | 40 +- .../procedures/hardware-ups-ees-snmp.md | 48 +- .../procedures/hardware-ups-himoinsa-snmp.md | 42 +- .../procedures/hardware-ups-hp-snmp.md | 26 +- .../hardware-ups-inmatics-sputnik-snmp.md | 36 +- .../procedures/hardware-ups-mge-snmp.md | 6 +- .../procedures/hardware-ups-nitram-snmp.md | 40 +- .../hardware-ups-phoenixtec-snmp.md | 22 +- .../procedures/hardware-ups-powerware-snmp.md | 14 +- .../procedures/hardware-ups-riello-snmp.md | 24 +- .../hardware-ups-socomec-netvision-snmp.md | 26 +- .../hardware-ups-standard-rfc1628-snmp.md | 36 +- .../infrastructure-active-directory-nrpe.md | 2 +- ...re-active-directory-nsclient-05-restapi.md | 2 +- .../procedures/network-3com-snmp.md | 10 +- .../procedures/network-acmepacket-snmp.md | 30 +- .../procedures/network-adva-fsp150-snmp.md | 22 +- .../procedures/network-adva-fsp3000-snmp.md | 22 +- .../procedures/network-aerohive-snmp.md | 10 +- .../procedures/network-allied-snmp.md | 12 +- .../network-alvarion-breezeaccess-snmp.md | 12 +- .../procedures/network-aruba-aoscx-snmp.md | 62 +- .../procedures/network-aruba-cppm-snmp.md | 12 +- .../procedures/network-aruba-instant-snmp.md | 20 +- .../network-aruba-orchestrator-restapi.md | 26 +- .../procedures/network-athonet-epc-snmp.md | 60 +- .../network-atto-fibrebridge-snmp.md | 10 +- .../procedures/network-audiocodes-snmp.md | 20 +- .../procedures/network-backbox-restapi.md | 2 +- .../procedures/network-barracuda-bma-snmp.md | 2 +- .../network-barracuda-cloudgen-snmp.md | 36 +- .../procedures/network-beeware-snmp.md | 12 +- .../network-cambium-cnpilot-snmp.md | 26 +- .../procedures/network-cambium-epmp-snmp.md | 26 +- .../network-chapsvision-crossing-snmp.md | 22 +- .../procedures/network-cisco-apic-restapi.md | 18 +- .../network-cisco-callmanager-snmp.md | 36 +- .../network-cisco-callmanager-sxml.md | 2 +- .../procedures/network-cisco-esa-restapi.md | 2 +- .../procedures/network-cisco-esa-xmlapi.md | 16 +- .../network-cisco-firepower-fmc-restapi.md | 18 +- .../network-cisco-firepower-snmp.md | 20 +- .../procedures/network-cisco-ironport-snmp.md | 22 +- .../network-cisco-meraki-restapi.md | 76 +- .../procedures/network-cisco-meraki-snmp.md | 6 +- .../procedures/network-cisco-prime-restapi.md | 14 +- .../procedures/network-cisco-standard-snmp.md | 82 +- .../procedures/network-cisco-standard-ssh.md | 14 +- .../procedures/network-cisco-umbrella-snmp.md | 30 +- .../procedures/network-cisco-vcs-restapi.md | 20 +- .../network-cisco-voice-gateway-snmp.md | 10 +- .../procedures/network-cisco-wap-snmp.md | 24 +- .../procedures/network-cisco-wlc-snmp.md | 40 +- .../network-citrix-appacceleration-snmp.md | 2 +- .../procedures/network-citrix-sdx-snmp.md | 10 +- .../procedures/network-colubris-snmp.md | 20 +- .../procedures/network-cyberoam-snmp.md | 10 +- .../procedures/network-dell-6200-snmp.md | 8 +- .../procedures/network-dell-nseries-snmp.md | 12 +- .../procedures/network-dell-os10-snmp.md | 14 +- .../procedures/network-dell-sseries-snmp.md | 10 +- .../procedures/network-denyall-snmp.md | 22 +- .../network-digi-anywhereusb-snmp.md | 10 +- .../network-digi-portserverts-snmp.md | 10 +- .../procedures/network-digi-sarian-snmp.md | 26 +- .../procedures/network-dlink-dgs3100-snmp.md | 10 +- .../procedures/network-dlink-standard-snmp.md | 36 +- .../procedures/network-efficientip-snmp.md | 10 +- .../procedures/network-enterasys-snmp.md | 12 +- .../procedures/network-evertz-fc7800-snmp.md | 4 +- .../procedures/network-extreme-snmp.md | 34 +- .../procedures/network-fiberstore-snmp.md | 14 +- .../network-firewalls-arkoon-snmp.md | 18 +- .../network-firewalls-checkpoint-snmp.md | 34 +- .../network-firewalls-cisco-asa-snmp.md | 26 +- ...twork-firewalls-fortinet-fortigate-snmp.md | 52 +- .../network-firewalls-juniper-mag-snmp.md | 18 +- .../network-firewalls-juniper-sa-snmp.md | 16 +- .../network-firewalls-juniper-srx-snmp.md | 10 +- .../network-firewalls-juniper-ssg-snmp.md | 18 +- ...etwork-firewalls-paloalto-standard-snmp.md | 20 +- ...network-firewalls-paloalto-standard-ssh.md | 78 +- .../network-firewalls-pfsense-snmp.md | 2 +- .../network-firewalls-sonicwall-snmp.md | 2 +- .../procedures/network-firewalls-stonesoft.md | 22 +- .../network-fortinet-fortiadc-snmp.md | 32 +- ...etwork-fortinet-fortiauthenticator-snmp.md | 18 +- .../network-fortinet-fortigate-restapi.md | 20 +- .../network-fortinet-fortimail-snmp.md | 20 +- .../network-fortinet-fortimanager-snmp.md | 44 +- .../network-fortinet-fortiswitch-snmp.md | 14 +- .../network-fortinet-fortiweb-snmp.md | 20 +- .../procedures/network-freebox-restapi.md | 20 +- .../procedures/network-fritzbox-upnp.md | 6 +- .../network-generic-bluecoat-snmp.md | 2 +- .../procedures/network-h3c-snmp.md | 10 +- .../procedures/network-hp-moonshot-snmp.md | 14 +- .../procedures/network-hp-standard-snmp.md | 36 +- .../procedures/network-hp-vc-snmp.md | 10 +- .../procedures/network-huawei-snmp.md | 14 +- .../network-ibm-bladecenter-snmp.md | 18 +- .../procedures/network-infoblox-snmp.md | 22 +- .../procedures/network-juniper-ggsn-snmp.md | 2 +- .../procedures/network-juniper-isg-snmp.md | 10 +- .../network-juniper-trapeze-snmp.md | 10 +- .../network-keysight-nvos-restapi.md | 68 +- .../network-lenovo-flexsystem-snmp.md | 18 +- .../network-lenovo-rackswitch-snmp.md | 24 +- .../procedures/network-libraesva-snmp.md | 22 +- .../network-loadbalancers-a10-ax-snmp.md | 18 +- .../network-loadbalancers-f5-bigip-snmp.md | 84 +- .../network-loadbalancers-kemp-snmp.md | 44 +- .../network-loadbalancers-netscaler-snmp.md | 20 +- .../procedures/network-meru-snmp.md | 12 +- .../procedures/network-microsens-g6-snmp.md | 22 +- .../procedures/network-mikrotik-snmp.md | 12 +- .../procedures/network-mitel-3300icp-snmp.md | 10 +- .../procedures/network-moxa-switch-snmp.md | 10 +- .../network-netgear-mseries-snmp.md | 14 +- .../network-netgear-sseries-snmp.md | 14 +- .../procedures/network-nokia-isam-snmp.md | 24 +- .../procedures/network-nokia-timos-snmp.md | 64 +- .../network-nortel-standard-snmp.md | 28 +- .../procedures/network-oneaccess-snmp.md | 30 +- .../procedures/network-opengear-snmp.md | 12 +- .../network-oracle-infiniband-snmp.md | 28 +- .../network-patton-smartnode-snmp.md | 2 +- .../network-peplink-pepwave-snmp.md | 22 +- .../procedures/network-perle-ids-snmp.md | 20 +- .../procedures/network-rad-airmux-snmp.md | 20 +- .../procedures/network-radware-alteon-snmp.md | 10 +- .../procedures/network-raisecom-snmp.md | 12 +- .../network-riverbed-interceptor-snmp.md | 26 +- .../network-riverbed-steelhead-snmp.md | 26 +- .../procedures/network-routers-atrica-snmp.md | 8 +- .../network-routers-juniper-mseries-snmp.md | 42 +- .../network-routers-peplink-balance-snmp.md | 18 +- .../network-routers-redback-snmp.md | 18 +- .../procedures/network-ruckus-icx-snmp.md | 14 +- .../procedures/network-ruckus-scg-snmp.md | 26 +- .../network-ruckus-smartzone-snmp.md | 22 +- .../procedures/network-ruckus-snmp.md | 10 +- .../network-ruckus-zonedirector-snmp.md | 18 +- .../procedures/network-ruggedcom.md | 10 +- .../procedures/network-securactive-snmp.md | 2 +- .../procedures/network-silverpeak-snmp.md | 26 +- .../procedures/network-sonus-sbc-snmp.md | 28 +- .../procedures/network-sophos-es-snmp.md | 2 +- .../procedures/network-stormshield-api.md | 54 +- .../procedures/network-stormshield-snmp.md | 42 +- .../procedures/network-stormshield-ssh.md | 2 +- ...network-switchs-alcatel-omniswitch-snmp.md | 32 +- .../procedures/network-switchs-arista-snmp.md | 18 +- .../network-switchs-aruba-standard-snmp.md | 58 +- .../network-switchs-brocade-snmp.md | 24 +- ...itchs-cisco-smallbusiness-standard-snmp.md | 26 +- .../network-switchs-dell-xseries-snmp.md | 14 +- .../network-switchs-hirschmann-snmp.md | 18 +- .../network-switchs-hp-procurve-snmp.md | 70 +- .../network-switchs-juniper-ex-snmp.md | 10 +- .../network-switchs-mrv-optiswitch-snmp.md | 14 +- .../procedures/network-symbol-wing-snmp.md | 20 +- .../procedures/network-teldat-snmp.md | 24 +- .../procedures/network-teltonika-snmp.md | 22 +- .../procedures/network-tplink-snmp.md | 12 +- .../network-ubiquiti-airfiber-snmp.md | 22 +- .../procedures/network-ubiquiti-unifi-snmp.md | 26 +- .../procedures/network-ucopia-snmp.md | 66 +- .../network-versa-director-restapi.md | 2 +- .../procedures/network-watchguard-snmp.md | 30 +- .../procedures/network-zyxel-snmp.md | 18 +- .../procedures/operatingsystems-aix-snmp.md | 10 +- .../procedures/operatingsystems-aix-ssh.md | 24 +- .../operatingsystems-as400-connector.md | 50 +- .../operatingsystems-freebsd-snmp.md | 10 +- ...systems-linux-centreon-monitoring-agent.md | 32 +- .../operatingsystems-linux-nrpe4.md | 32 +- .../procedures/operatingsystems-linux-snmp.md | 18 +- .../operatingsystems-linux-snmpv3.md | 12 +- .../procedures/operatingsystems-linux-ssh.md | 52 +- .../operatingsystems-linux-telegraf-agent.md | 32 +- .../procedures/operatingsystems-mac-snmp.md | 10 +- ...stems-windows-centreon-monitoring-agent.md | 10 +- ...tingsystems-windows-nsclient-05-restapi.md | 38 +- .../operatingsystems-windows-snmp.md | 16 +- ...operatingsystems-windows-telegraf-agent.md | 10 +- .../operatingsystems-windows-wsman.md | 10 +- .../virtualization-hpe-simplivity-restapi.md | 86 +- .../virtualization-hyperv-2012-nrpe.md | 52 +- .../virtualization-hyperv-nscp-restapi.md | 52 +- .../procedures/virtualization-vmware2-esx.md | 298 +- .../virtualization-vmware2-vcenter-generic.md | 444 +- .../procedures/virtualization-vmware2-vm.md | 118 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-22.10/api/clapi.md | 1114 +- .../version-22.10/api/graph-views-api.md | 8 +- .../version-22.10/api/graph-views-map-api.md | 10 +- .../version-22.10/api/rest-api-v1.md | 4 +- .../version-22.10/connect/openid.md | 20 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../version-22.10/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 6 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-22.10/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.md | 2 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../upgrade/upgrade-from-18-10.md | 2 + .../upgrade/upgrade-from-19-04.md | 2 + .../upgrade/upgrade-from-19-10.md | 2 + .../upgrade/upgrade-from-20-04.md | 2 + .../version-22.10/upgrade/upgrade-from-3-4.md | 2 + .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-23.04/api/clapi.md | 1114 +- .../version-23.04/api/graph-views-api.md | 8 +- .../version-23.04/api/graph-views-map-api.md | 10 +- .../version-23.04/api/rest-api-v1.md | 4 +- .../version-23.04/api/rest-api-v2.md | 4 +- .../version-23.04/connect/openid.md | 20 +- .../version-23.04/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../version-23.04/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 6 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-23.04/metrology/grafana.md | 4 +- .../version-23.04/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.mdx | 11 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-23.10/api/clapi.md | 1114 +- .../version-23.10/api/graph-views-api.md | 8 +- .../version-23.10/api/graph-views-map-api.md | 10 +- .../version-23.10/api/rest-api-v1.md | 4 +- .../version-23.10/api/rest-api-v2.md | 4 +- .../version-23.10/connect/openid.md | 20 +- .../version-23.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../version-23.10/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 6 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-mip.md | 14 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-23.10/metrology/grafana.md | 4 +- .../version-23.10/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.mdx | 2 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-24.04/api/clapi.md | 1114 +- .../version-24.04/api/graph-views-api.md | 8 +- .../version-24.04/api/graph-views-map-api.md | 10 +- .../version-24.04/api/rest-api-v1.md | 4 +- .../version-24.04/api/rest-api-v2.md | 4 +- .../version-24.04/connect/openid.md | 20 +- .../version-24.04/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../version-24.04/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 10 +- .../using-packages.md | 10 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-mip.md | 2 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-24.04/metrology/grafana.md | 4 +- .../version-24.04/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-24.10/api/clapi.md | 1114 +- .../version-24.10/api/graph-views-map-api.md | 10 +- .../version-24.10/api/rest-api-v1.md | 4 +- .../version-24.10/api/rest-api-v2.md | 4 +- .../version-24.10/connect/openid.md | 20 +- .../version-24.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../using-packages.md | 10 +- .../using-packages.md | 10 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-mip.md | 2 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-24.10/metrology/grafana.md | 4 +- .../version-24.10/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-debian-to-debian.md | 12 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 8 +- .../notif-config-for-teams.md | 8 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- .../version-25.10/api/clapi.md | 1114 +- .../version-25.10/api/graph-views-map-api.md | 10 +- .../version-25.10/api/rest-api-v1.md | 4 +- .../version-25.10/api/rest-api-v2.md | 4 +- .../version-25.10/connect/openid.md | 20 +- .../version-25.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-widget.md | 2 +- .../getting-started/model-it-services.md | 2 +- .../using-packages.md | 10 +- .../using-packages.md | 10 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-datadog-events.md | 2 +- .../data-analytics/sc-datadog-metrics.md | 2 +- .../data-analytics/sc-influxdb2-metrics.md | 2 +- .../data-analytics/sc-logstash-events.md | 2 +- .../data-analytics/sc-splunk-events.md | 2 +- .../data-analytics/sc-splunk-metrics.md | 2 +- .../connector-mip.md | 2 +- .../connector-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 2 +- .../event-management/sc-pagerduty-events.md | 2 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-25.10/metrology/grafana.md | 4 +- .../version-25.10/migrate/migrate-from-3-4.md | 18 +- .../migrate/migrate-from-el-to-debian.md | 12 +- .../migrate/migrate-from-el-to-el.md | 12 +- .../poller-display-to-remote-server.md | 12 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/reports_publication_rule.md | 10 +- .../service-mapping/ba-management.md | 2 +- .../docusaurus-plugin-content-pages/index.js | 2 +- package.json | 23 +- pnpm-lock.yaml | 12583 ++++++++++++++++ .../develop-with-centreon-plugins.md | 18 +- .../how-to-guides/troubleshooting-plugins.md | 10 +- .../windows-winrm-wsman-tutorial.md | 19 +- .../procedures/applications-ansible-tower.md | 42 +- .../applications-antivirus-clamav-ssh.md | 30 +- .../applications-antivirus-kaspersky-snmp.md | 2 +- ...tions-antivirus-skyhigh-webgateway-snmp.md | 2 +- .../procedures/applications-awa-jmx.md | 2 +- .../procedures/applications-bluemind-ssh.md | 2 +- .../applications-cisco-ssms-restapi.md | 14 +- ...pplications-commvault-commserve-restapi.md | 50 +- .../applications-databases-elasticsearch.md | 22 +- .../applications-databases-firebird.md | 2 +- .../applications-databases-influxdb.md | 16 +- .../applications-databases-informix-snmp.md | 14 +- .../applications-databases-informix.md | 2 +- .../applications-databases-mongodb.md | 18 +- .../applications-databases-mssql.md | 20 +- .../applications-databases-mysql.md | 54 +- .../applications-databases-oracle.md | 46 +- .../applications-databases-postgresql.md | 2 +- .../applications-databases-redis.md | 18 +- .../applications-databases-sap-hana.md | 2 +- ...applications-databases-warp10-sensision.md | 2 +- .../procedures/applications-docker-restapi.md | 20 +- .../procedures/applications-docker-ssh.md | 10 +- .../applications-dynamics-ax-mssql.md | 2 +- .../applications-eclipse-mosquitto-mqtt.md | 12 +- .../applications-google-workspace-api.md | 4 +- .../applications-gorgone-restapi.md | 2 +- .../procedures/applications-grafana-api.md | 12 +- .../procedures/applications-haproxy-snmp.md | 2 +- .../applications-hashicorp-vault-restapi.md | 10 +- .../procedures/applications-hddtemp-tcp.md | 4 +- .../applications-infor-ion-grid-restapi.md | 22 +- .../procedures/applications-ipfabric-api.md | 10 +- .../procedures/applications-jmeter.md | 2 +- .../applications-keepalived-snmp.md | 10 +- .../procedures/applications-lmsensors-snmp.md | 2 +- .../applications-microsoft-dhcp-snmp.md | 8 +- .../applications-monitoring-alyvix-restapi.md | 4 +- ...pplications-monitoring-centreon-central.md | 10 +- ...plications-monitoring-centreon-database.md | 2 +- ...monitoring-centreon-map-engine-actuator.md | 2 +- .../applications-monitoring-centreon-mbi.md | 4 +- ...applications-monitoring-centreon-poller.md | 12 +- ...cations-monitoring-centreon-sql-metrics.md | 2 +- ...ions-monitoring-iplabel-newtest-restapi.md | 2 +- ...applications-monitoring-kadiska-restapi.md | 2 +- .../applications-monitoring-loggly-restapi.md | 2 +- ...ications-monitoring-node-exporter-linux.md | 2 +- ...ations-monitoring-node-exporter-windows.md | 10 +- .../applications-monitoring-quanta-restapi.md | 2 +- .../applications-monitoring-scom-restapi.md | 14 +- .../applications-monitoring-speedtest.md | 2 +- .../applications-monitoring-splunk-api.md | 26 +- .../applications-mulesoft-restapi.md | 4 +- .../procedures/applications-netbackup-ssh.md | 2 +- .../procedures/applications-openldap-ldap.md | 2 +- .../procedures/applications-openvpn-omi.md | 2 +- .../applications-openweathermap-restapi.md | 2 +- .../procedures/applications-oracle-ovm-api.md | 32 +- .../procedures/applications-pacemaker-ssh.md | 44 +- .../applications-pfsense-fauxapi.md | 12 +- .../applications-protocol-bgp-snmp.md | 12 +- .../procedures/applications-protocol-cifs.md | 28 +- .../procedures/applications-protocol-dns.md | 2 +- .../procedures/applications-protocol-ftp.md | 2 +- .../procedures/applications-protocol-http.md | 46 +- .../procedures/applications-protocol-ldap.md | 4 +- .../applications-protocol-modbus.md | 2 +- .../procedures/applications-protocol-ntp.md | 2 +- .../procedures/applications-protocol-ospf.md | 20 +- .../applications-protocol-radius.md | 2 +- .../procedures/applications-protocol-sftp.md | 28 +- .../procedures/applications-protocol-smtp.md | 2 +- .../procedures/applications-protocol-snmp.md | 16 +- .../procedures/applications-protocol-ssh.md | 2 +- .../procedures/applications-protocol-tcp.md | 8 +- .../applications-protocol-telnet.md | 10 +- .../procedures/applications-protocol-x509.md | 14 +- .../procedures/applications-pvx-restapi.md | 2 +- .../applications-rapidrecovery-snmp.md | 30 +- .../procedures/applications-redis-sentinel.md | 6 +- .../procedures/applications-rrdcached.md | 10 +- .../procedures/applications-rubrik-restapi.md | 50 +- .../procedures/applications-rudder-restapi.md | 2 +- .../applications-sahipro-restapi.md | 16 +- ...lications-sailpoint-identitynow-restapi.md | 10 +- .../applications-salesforce-restapi.md | 4 +- .../procedures/applications-sccm-nsclient.md | 4 +- .../procedures/applications-slack-restapi.md | 4 +- .../procedures/applications-tosca-restapi.md | 10 +- .../applications-trendmicro-iwsva-snmp.md | 10 +- .../procedures/applications-veeam-nrpe.md | 60 +- .../applications-veeam-nsclient-05-restapi.md | 60 +- .../applications-veeam-vbem-restapi.md | 12 +- .../procedures/applications-veeam-wsman.md | 60 +- .../applications-vernemq-restapi.md | 26 +- .../applications-vmware-vcsa-restapi.md | 16 +- .../applications-voip-3cx-restapi.md | 22 +- .../procedures/applications-wazuh-restapi.md | 18 +- .../applications-webservers-iis-restapi.md | 24 +- ...lications-webservers-nginx-serverstatus.md | 18 +- ...plications-webservers-tomcat-webmanager.md | 2 +- .../plugin-packs/procedures/base-generic.md | 2 +- .../procedures/cloud-aws-apigateway.md | 2 +- .../procedures/cloud-aws-backup.md | 2 +- .../procedures/cloud-aws-billing.md | 2 +- .../procedures/cloud-aws-cloudfront.md | 2 +- .../procedures/cloud-aws-cloudwatch.md | 10 +- .../procedures/cloud-aws-cloudwatchlogs.md | 14 +- .../procedures/cloud-aws-directconnect.md | 18 +- .../plugin-packs/procedures/cloud-aws-ebs.md | 2 +- .../plugin-packs/procedures/cloud-aws-ec2.md | 26 +- .../plugin-packs/procedures/cloud-aws-efs.md | 2 +- .../procedures/cloud-aws-elasticache.md | 2 +- .../plugin-packs/procedures/cloud-aws-elb.md | 2 +- .../plugin-packs/procedures/cloud-aws-fsx.md | 2 +- .../procedures/cloud-aws-kinesis.md | 2 +- .../procedures/cloud-aws-lambda.md | 2 +- .../plugin-packs/procedures/cloud-aws-rds.md | 10 +- .../plugin-packs/procedures/cloud-aws-s3.md | 2 +- .../plugin-packs/procedures/cloud-aws-ses.md | 2 +- .../plugin-packs/procedures/cloud-aws-sns.md | 2 +- .../plugin-packs/procedures/cloud-aws-sqs.md | 2 +- .../procedures/cloud-aws-transitgateway.md | 2 +- .../plugin-packs/procedures/cloud-aws-vpn.md | 2 +- .../cloud-azure-analytics-eventhubs.md | 4 +- .../procedures/cloud-azure-compute-aks.md | 18 +- .../cloud-azure-compute-functions.md | 18 +- .../cloud-azure-compute-virtualmachine.md | 6 +- .../cloud-azure-database-cosmosdb.md | 18 +- .../cloud-azure-database-elasticpool.md | 2 +- .../cloud-azure-database-mariadb.md | 2 +- .../procedures/cloud-azure-database-mysql.md | 2 +- .../cloud-azure-database-postgresql.md | 2 +- .../procedures/cloud-azure-database-redis.md | 18 +- .../cloud-azure-database-sqldatabase.md | 18 +- ...cloud-azure-database-sqlmanagedinstance.md | 18 +- .../cloud-azure-database-sqlserver.md | 12 +- .../cloud-azure-datafactory-factories.md | 2 +- .../cloud-azure-management-costs.md | 2 +- .../cloud-azure-management-monitor.md | 2 +- .../cloud-azure-management-recovery.md | 2 +- .../cloud-azure-management-resource.md | 14 +- .../cloud-azure-network-networkinterface.md | 14 +- .../cloud-azure-network-publicip.md | 4 +- .../cloud-azure-network-virtualnetwork.md | 2 +- .../cloud-azure-network-vpngateway.md | 6 +- ...cloud-azure-policyinsights-policystates.md | 2 +- .../procedures/cloud-cadvisor-api.md | 2 +- .../procedures/cloud-kubernetes-api.md | 94 +- .../cloud-microsoft-office365-exchange.md | 10 +- .../cloud-microsoft-office365-management.md | 36 +- .../cloud-microsoft-office365-onedrive.md | 2 +- .../cloud-microsoft-office365-sharepoint.md | 2 +- .../cloud-microsoft-office365-skype.md | 2 +- .../cloud-microsoft-office365-teams.md | 2 +- .../procedures/cloud-prometheus-api.md | 20 +- .../cloud-prometheus-kubernetes-api.md | 44 +- .../cloud-vmware-velocloud-restapi.md | 28 +- .../procedures/hardware-ats-apc.md | 10 +- .../procedures/hardware-ats-eaton-snmp.md | 6 +- .../hardware-device-gorgy-ntpserver-snmp.md | 26 +- .../hardware-devices-abb-cms700-snmp.md | 2 +- .../hardware-devices-camera-avigilon-snmp.md | 32 +- .../hardware-devices-camera-optelecom-snmp.md | 32 +- ...ware-devices-hms-netbiter-argos-restapi.md | 8 +- ...re-devices-pexip-infinity-managementapi.md | 4 +- .../hardware-devices-polycom-dma-snmp.md | 6 +- .../hardware-devices-video-appeartv-snmp.md | 14 +- .../hardware-kvm-avocent-acs-8000-snmp.md | 14 +- .../procedures/hardware-pdu-apc-snmp.md | 20 +- .../procedures/hardware-pdu-clever-snmp.md | 2 +- .../hardware-pdu-cyberpower-snmp.md | 34 +- .../procedures/hardware-pdu-eaton-snmp.md | 26 +- .../procedures/hardware-pdu-emerson-snmp.md | 22 +- .../procedures/hardware-pdu-gude-epc-snmp.md | 14 +- .../procedures/hardware-pdu-raritan-snmp.md | 2 +- ...ardware-pdu-schleifenbauer-gateway-snmp.md | 2 +- ...hardware-printers-standard-rfc3805-snmp.md | 28 +- .../procedures/hardware-sensors-akcp-snmp.md | 2 +- .../procedures/hardware-sensors-apc-snmp.md | 2 +- .../hardware-sensors-comet-p8000-snmp.md | 2 +- .../procedures/hardware-sensors-geist-snmp.md | 2 +- .../hardware-sensors-hwgste-snmp.md | 2 +- .../hardware-sensors-jacarta-snmp.md | 4 +- .../hardware-sensors-netbotz-snmp.md | 2 +- .../hardware-sensors-rittal-cmc3-snmp.md | 24 +- .../hardware-sensors-sensorip-snmp.md | 2 +- .../hardware-sensors-sensormetrix-em01-web.md | 2 +- ...sensors-serverscheck-sensorgateway-snmp.md | 2 +- .../hardware-servers-cisco-ucs-snmp.md | 40 +- .../hardware-servers-dell-idrac-snmp.md | 14 +- .../hardware-servers-hp-ilo-xmlapi.md | 2 +- .../hardware-servers-hp-oneview-restapi.md | 16 +- .../procedures/hardware-servers-hp-snmp.md | 2 +- .../hardware-storage-adic-tape-snmp.md | 2 +- .../hardware-storage-avid-isis-snmp.md | 10 +- .../hardware-storage-bdt-multistak-snmp.md | 2 +- .../hardware-storage-datacore-api.md | 8 +- .../hardware-storage-dell-compellent-api.md | 4 +- .../hardware-storage-dell-compellent-snmp.md | 10 +- .../hardware-storage-dell-md3000-smcli.md | 2 +- ...ardware-storage-emc-clariion-navisphere.md | 2 +- .../hardware-storage-emc-datadomain-snmp.md | 76 +- ...hardware-storage-fujitsu-eternus-dx-ssh.md | 6 +- .../hardware-storage-hitachi-hnas-snmp.md | 32 +- .../hardware-storage-hitachi-standard-snmp.md | 2 +- .../hardware-storage-hp-3par-ssh.md | 120 +- .../hardware-storage-hp-lefthand-snmp.md | 12 +- .../hardware-storage-hp-msa2000-snmp.md | 10 +- .../hardware-storage-hpe-primera-restapi.md | 20 +- .../hardware-storage-ibm-ds3000-smcli.md | 2 +- .../hardware-storage-ibm-ds4000-smcli.md | 2 +- .../hardware-storage-ibm-ds5000-smcli.md | 2 +- .../hardware-storage-ibm-storwize-ssh.md | 14 +- .../hardware-storage-ibm-ts3100-snmp.md | 2 +- .../hardware-storage-ibm-ts3200-snmp.md | 2 +- .../hardware-storage-lenovo-sseries-snmp.md | 10 +- .../hardware-storage-netapp-ontap-restapi.md | 62 +- ...dware-storage-netapp-santricity-restapi.md | 4 +- ...orage-purestorage-flasharray-v2-restapi.md | 10 +- .../hardware-storage-purestorage-snmp.md | 2 +- .../procedures/hardware-storage-qnap-snmp.md | 30 +- .../hardware-storage-quantum-scalar-snmp.md | 2 +- .../hardware-storage-synology-snmp.md | 10 +- .../hardware-storage-wd-nas-snmp.md | 10 +- .../procedures/hardware-ups-alpha-snmp.md | 20 +- .../procedures/hardware-ups-apc-snmp.md | 46 +- .../hardware-ups-cyberpower-snmp.md | 40 +- .../procedures/hardware-ups-ees-snmp.md | 48 +- .../procedures/hardware-ups-himoinsa-snmp.md | 42 +- .../procedures/hardware-ups-hp-snmp.md | 26 +- .../hardware-ups-inmatics-sputnik-snmp.md | 36 +- .../procedures/hardware-ups-mge-snmp.md | 6 +- .../procedures/hardware-ups-nitram-snmp.md | 40 +- .../hardware-ups-phoenixtec-snmp.md | 22 +- .../procedures/hardware-ups-powerware-snmp.md | 14 +- .../procedures/hardware-ups-riello-snmp.md | 24 +- .../hardware-ups-socomec-netvision-snmp.md | 26 +- .../hardware-ups-standard-rfc1628-snmp.md | 36 +- .../infrastructure-active-directory-nrpe.md | 2 +- ...re-active-directory-nsclient-05-restapi.md | 2 +- .../procedures/network-3com-snmp.md | 10 +- .../procedures/network-acmepacket-snmp.md | 30 +- .../procedures/network-adva-fsp150-snmp.md | 22 +- .../procedures/network-adva-fsp3000-snmp.md | 22 +- .../procedures/network-aerohive-snmp.md | 10 +- .../procedures/network-allied-snmp.md | 12 +- .../network-alvarion-breezeaccess-snmp.md | 12 +- .../procedures/network-aruba-aoscx-snmp.md | 62 +- .../procedures/network-aruba-cppm-snmp.md | 12 +- .../procedures/network-aruba-instant-snmp.md | 20 +- .../network-aruba-orchestrator-restapi.md | 26 +- .../procedures/network-athonet-epc-snmp.md | 60 +- .../network-atto-fibrebridge-snmp.md | 10 +- .../procedures/network-audiocodes-snmp.md | 20 +- .../procedures/network-backbox-restapi.md | 2 +- .../procedures/network-barracuda-bma-snmp.md | 2 +- .../network-barracuda-cloudgen-snmp.md | 36 +- .../procedures/network-beeware-snmp.md | 12 +- .../network-cambium-cnpilot-snmp.md | 26 +- .../procedures/network-cambium-epmp-snmp.md | 26 +- .../network-chapsvision-crossing-snmp.md | 22 +- .../procedures/network-cisco-apic-restapi.md | 18 +- .../network-cisco-callmanager-snmp.md | 36 +- .../network-cisco-callmanager-sxml.md | 2 +- .../procedures/network-cisco-esa-restapi.md | 2 +- .../procedures/network-cisco-esa-xmlapi.md | 16 +- .../network-cisco-firepower-fmc-restapi.md | 18 +- .../network-cisco-firepower-snmp.md | 20 +- .../procedures/network-cisco-ironport-snmp.md | 22 +- .../network-cisco-meraki-restapi.md | 76 +- .../procedures/network-cisco-meraki-snmp.md | 6 +- .../procedures/network-cisco-prime-restapi.md | 14 +- .../procedures/network-cisco-standard-snmp.md | 82 +- .../procedures/network-cisco-standard-ssh.md | 14 +- .../procedures/network-cisco-umbrella-snmp.md | 30 +- .../procedures/network-cisco-vcs-restapi.md | 20 +- .../network-cisco-voice-gateway-snmp.md | 10 +- .../procedures/network-cisco-wap-snmp.md | 24 +- .../procedures/network-cisco-wlc-snmp.md | 40 +- .../network-citrix-appacceleration-snmp.md | 2 +- .../procedures/network-citrix-sdx-snmp.md | 10 +- .../procedures/network-colubris-snmp.md | 20 +- .../procedures/network-cyberoam-snmp.md | 10 +- .../procedures/network-dell-6200-snmp.md | 8 +- .../procedures/network-dell-nseries-snmp.md | 12 +- .../procedures/network-dell-os10-snmp.md | 14 +- .../procedures/network-dell-sseries-snmp.md | 10 +- .../procedures/network-denyall-snmp.md | 22 +- .../network-digi-anywhereusb-snmp.md | 10 +- .../network-digi-portserverts-snmp.md | 10 +- .../procedures/network-digi-sarian-snmp.md | 26 +- .../procedures/network-dlink-dgs3100-snmp.md | 10 +- .../procedures/network-dlink-standard-snmp.md | 36 +- .../procedures/network-efficientip-snmp.md | 10 +- .../procedures/network-enterasys-snmp.md | 12 +- .../procedures/network-evertz-fc7800-snmp.md | 4 +- .../procedures/network-extreme-snmp.md | 34 +- .../procedures/network-fiberstore-snmp.md | 14 +- .../network-firewalls-arkoon-snmp.md | 18 +- .../network-firewalls-checkpoint-snmp.md | 34 +- .../network-firewalls-cisco-asa-snmp.md | 26 +- ...twork-firewalls-fortinet-fortigate-snmp.md | 52 +- .../network-firewalls-juniper-mag-snmp.md | 18 +- .../network-firewalls-juniper-sa-snmp.md | 16 +- .../network-firewalls-juniper-srx-snmp.md | 10 +- .../network-firewalls-juniper-ssg-snmp.md | 18 +- ...etwork-firewalls-paloalto-standard-snmp.md | 20 +- ...network-firewalls-paloalto-standard-ssh.md | 78 +- .../network-firewalls-pfsense-snmp.md | 2 +- .../network-firewalls-sonicwall-snmp.md | 2 +- .../procedures/network-firewalls-stonesoft.md | 22 +- .../network-fortinet-fortiadc-snmp.md | 32 +- ...etwork-fortinet-fortiauthenticator-snmp.md | 18 +- .../network-fortinet-fortigate-restapi.md | 20 +- .../network-fortinet-fortimail-snmp.md | 20 +- .../network-fortinet-fortimanager-snmp.md | 44 +- .../network-fortinet-fortiswitch-snmp.md | 14 +- .../network-fortinet-fortiweb-snmp.md | 20 +- .../procedures/network-freebox-restapi.md | 22 +- .../procedures/network-fritzbox-upnp.md | 6 +- .../network-generic-bluecoat-snmp.md | 2 +- .../procedures/network-h3c-snmp.md | 10 +- .../procedures/network-hp-moonshot-snmp.md | 14 +- .../procedures/network-hp-standard-snmp.md | 36 +- .../procedures/network-hp-vc-snmp.md | 10 +- .../procedures/network-huawei-snmp.md | 14 +- .../network-ibm-bladecenter-snmp.md | 18 +- .../procedures/network-infoblox-snmp.md | 22 +- .../procedures/network-juniper-ggsn-snmp.md | 2 +- .../procedures/network-juniper-isg-snmp.md | 10 +- .../network-juniper-trapeze-snmp.md | 10 +- .../network-keysight-nvos-restapi.md | 68 +- .../network-lenovo-flexsystem-snmp.md | 18 +- .../network-lenovo-rackswitch-snmp.md | 24 +- .../procedures/network-libraesva-snmp.md | 22 +- .../network-loadbalancers-a10-ax-snmp.md | 18 +- .../network-loadbalancers-f5-bigip-snmp.md | 84 +- .../network-loadbalancers-kemp-snmp.md | 44 +- .../network-loadbalancers-netscaler-snmp.md | 20 +- .../procedures/network-meru-snmp.md | 12 +- .../procedures/network-microsens-g6-snmp.md | 22 +- .../procedures/network-mikrotik-snmp.md | 12 +- .../procedures/network-mitel-3300icp-snmp.md | 10 +- .../procedures/network-moxa-switch-snmp.md | 10 +- .../network-netgear-mseries-snmp.md | 14 +- .../network-netgear-sseries-snmp.md | 14 +- .../procedures/network-nokia-isam-snmp.md | 24 +- .../procedures/network-nokia-timos-snmp.md | 64 +- .../network-nortel-standard-snmp.md | 28 +- .../procedures/network-oneaccess-snmp.md | 30 +- .../procedures/network-opengear-snmp.md | 12 +- .../network-oracle-infiniband-snmp.md | 28 +- .../network-patton-smartnode-snmp.md | 2 +- .../network-peplink-pepwave-snmp.md | 22 +- .../procedures/network-perle-ids-snmp.md | 20 +- .../procedures/network-rad-airmux-snmp.md | 20 +- .../procedures/network-radware-alteon-snmp.md | 10 +- .../procedures/network-raisecom-snmp.md | 12 +- .../network-riverbed-interceptor-snmp.md | 26 +- .../network-riverbed-steelhead-snmp.md | 26 +- .../procedures/network-routers-atrica-snmp.md | 8 +- .../network-routers-juniper-mseries-snmp.md | 42 +- .../network-routers-peplink-balance-snmp.md | 18 +- .../network-routers-redback-snmp.md | 18 +- .../procedures/network-ruckus-icx-snmp.md | 14 +- .../procedures/network-ruckus-scg-snmp.md | 26 +- .../network-ruckus-smartzone-snmp.md | 22 +- .../procedures/network-ruckus-snmp.md | 10 +- .../network-ruckus-zonedirector-snmp.md | 18 +- .../procedures/network-ruggedcom.md | 10 +- .../procedures/network-securactive-snmp.md | 2 +- .../procedures/network-silverpeak-snmp.md | 26 +- .../procedures/network-sonus-sbc-snmp.md | 28 +- .../procedures/network-sophos-es-snmp.md | 2 +- .../procedures/network-stormshield-api.md | 54 +- .../procedures/network-stormshield-snmp.md | 42 +- .../procedures/network-stormshield-ssh.md | 2 +- ...network-switchs-alcatel-omniswitch-snmp.md | 32 +- .../procedures/network-switchs-arista-snmp.md | 18 +- .../network-switchs-aruba-standard-snmp.md | 58 +- .../network-switchs-brocade-snmp.md | 24 +- ...itchs-cisco-smallbusiness-standard-snmp.md | 26 +- .../network-switchs-dell-xseries-snmp.md | 14 +- .../network-switchs-hirschmann-snmp.md | 18 +- .../network-switchs-hp-procurve-snmp.md | 70 +- .../network-switchs-juniper-ex-snmp.md | 10 +- .../network-switchs-mrv-optiswitch-snmp.md | 14 +- .../procedures/network-symbol-wing-snmp.md | 20 +- .../procedures/network-teldat-snmp.md | 24 +- .../procedures/network-teltonika-snmp.md | 22 +- .../procedures/network-tplink-snmp.md | 12 +- .../network-ubiquiti-airfiber-snmp.md | 22 +- .../procedures/network-ubiquiti-unifi-snmp.md | 26 +- .../procedures/network-ucopia-snmp.md | 66 +- .../network-versa-director-restapi.md | 2 +- .../procedures/network-watchguard-snmp.md | 30 +- .../procedures/network-zyxel-snmp.md | 18 +- .../procedures/operatingsystems-aix-snmp.md | 10 +- .../procedures/operatingsystems-aix-ssh.md | 26 +- .../operatingsystems-as400-connector.md | 50 +- .../operatingsystems-freebsd-snmp.md | 10 +- ...systems-linux-centreon-monitoring-agent.md | 32 +- .../operatingsystems-linux-nrpe4.md | 32 +- .../procedures/operatingsystems-linux-snmp.md | 18 +- .../operatingsystems-linux-snmpv3.md | 12 +- .../procedures/operatingsystems-linux-ssh.md | 52 +- .../operatingsystems-linux-telegraf-agent.md | 32 +- .../procedures/operatingsystems-mac-snmp.md | 10 +- ...stems-windows-centreon-monitoring-agent.md | 10 +- ...tingsystems-windows-nsclient-05-restapi.md | 38 +- .../operatingsystems-windows-snmp.md | 16 +- ...operatingsystems-windows-telegraf-agent.md | 10 +- .../operatingsystems-windows-wsman.md | 10 +- .../virtualization-hpe-simplivity-restapi.md | 86 +- .../virtualization-hyperv-2012-nrpe.md | 52 +- .../virtualization-hyperv-nscp-restapi.md | 52 +- .../procedures/virtualization-vmware2-esx.md | 298 +- .../virtualization-vmware2-vcenter-generic.md | 444 +- .../procedures/virtualization-vmware2-vm.md | 118 +- src/pages/index.js | 2 +- src/theme/DocBreadcrumbs/index.js | 8 +- src/theme/DocBreadcrumbs/styles.module.css | 6 +- src/theme/DocCard/index.tsx | 6 +- .../DocItem/Footer/{index.js => index.jsx} | 8 +- .../DocVersionBanner/{index.js => index.jsx} | 2 +- ...m.js => DocsVersionDropdownNavbarItem.jsx} | 0 src/theme/TOC/{index.js => index.jsx} | 8 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-22.10/api/clapi.md | 1114 +- .../version-22.10/api/graph-views-api.md | 8 +- .../version-22.10/api/graph-views-map-api.md | 10 +- .../version-22.10/api/rest-api-v1.md | 4 +- .../version-22.10/connect/openid.md | 20 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../version-22.10/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 4 +- .../using-packages.md | 10 +- .../using-packages.md | 16 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-22.10/migrate/migrate-from-3-4.md | 6 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.md | 2 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../upgrade/upgrade-from-18-10.md | 2 + .../upgrade/upgrade-from-19-04.md | 2 + .../upgrade/upgrade-from-19-10.md | 2 + .../upgrade/upgrade-from-20-04.md | 2 + .../version-22.10/upgrade/upgrade-from-3-4.md | 2 + .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-23.04/api/clapi.md | 1114 +- .../version-23.04/api/graph-views-api.md | 8 +- .../version-23.04/api/graph-views-map-api.md | 10 +- .../version-23.04/api/rest-api-v1.md | 4 +- .../version-23.04/api/rest-api-v2.md | 4 +- .../version-23.04/connect/openid.md | 20 +- versioned_docs/version-23.04/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../version-23.04/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 4 +- .../using-packages.md | 10 +- .../using-packages.md | 18 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-23.04/metrology/grafana.md | 4 +- .../version-23.04/migrate/migrate-from-3-4.md | 4 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.mdx | 2 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-23.10/api/clapi.md | 1118 +- .../version-23.10/api/graph-views-api.md | 8 +- .../version-23.10/api/graph-views-map-api.md | 10 +- .../version-23.10/api/rest-api-v1.md | 4 +- .../version-23.10/api/rest-api-v2.md | 4 +- .../version-23.10/connect/openid.md | 20 +- versioned_docs/version-23.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../version-23.10/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 4 +- .../using-packages.md | 10 +- .../using-packages.md | 18 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-23.10/metrology/grafana.md | 4 +- .../version-23.10/migrate/migrate-from-3-4.md | 6 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../centreon-commercial-extensions.mdx | 2 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-24.04/api/clapi.md | 1118 +- .../version-24.04/api/graph-views-api.md | 8 +- .../version-24.04/api/graph-views-map-api.md | 10 +- .../version-24.04/api/rest-api-v1.md | 4 +- .../version-24.04/api/rest-api-v2.md | 4 +- .../version-24.04/connect/openid.md | 20 +- versioned_docs/version-24.04/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../version-24.04/graph-views/install.md | 2 +- .../graph-views/troubleshooter.md | 6 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-24.04/metrology/grafana.md | 4 +- .../version-24.04/migrate/migrate-from-3-4.md | 6 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-24.10/api/clapi.md | 1118 +- .../version-24.10/api/graph-views-map-api.md | 10 +- .../version-24.10/api/rest-api-v1.md | 4 +- .../version-24.10/api/rest-api-v2.md | 4 +- .../version-24.10/connect/openid.md | 20 +- versioned_docs/version-24.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-24.10/metrology/grafana.md | 4 +- .../version-24.10/migrate/migrate-from-3-4.md | 6 +- .../migrate/migrate-from-debian-to-debian.md | 4 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../logging-configuration-changes.md | 6 +- .../administration/parameters/ldap.md | 4 +- .../administration/secure-platform.md | 6 +- .../notif-config-for-teams.md | 6 +- .../alerts-notifications/resources-status.md | 2 +- .../alerts-notifications/ticketing.md | 6 +- versioned_docs/version-25.10/api/clapi.md | 1118 +- .../version-25.10/api/graph-views-map-api.md | 10 +- .../version-25.10/api/rest-api-v1.md | 4 +- .../version-25.10/api/rest-api-v2.md | 4 +- .../version-25.10/connect/openid.md | 20 +- versioned_docs/version-25.10/connect/saml.md | 6 +- ...per-gorgone-client-server-communication.md | 2 +- .../developer/developer-translate-centreon.md | 2 +- .../developer/developer-widget.md | 4 +- .../using-packages.md | 10 +- .../using-packages.md | 14 +- .../installation/prerequisites.md | 10 +- .../data-analytics/sc-clickhouse.md | 2 +- .../data-analytics/sc-datadog-events.md | 4 +- .../data-analytics/sc-datadog-metrics.md | 4 +- .../data-analytics/sc-influxdb2-metrics.md | 4 +- .../data-analytics/sc-logstash-events.md | 4 +- .../data-analytics/sc-splunk-events.md | 4 +- .../data-analytics/sc-splunk-metrics.md | 4 +- .../pack-skylight-pvx.md | 6 +- .../event-management/sc-opsgenie.md | 6 +- .../event-management/sc-pagerduty-events.md | 4 +- .../integrations/itsm/ot-bmc-remedy.md | 2 +- .../integrations/itsm/ot-mail.md | 2 +- .../integrations/itsm/ot-serena.md | 2 +- .../notifications/plugin-telegram.md | 4 +- .../integrations/stream-connectors.md | 2 + .../version-25.10/metrology/grafana.md | 4 +- .../version-25.10/migrate/migrate-from-3-4.md | 6 +- .../migrate/migrate-from-el-to-debian.md | 4 +- .../migrate/migrate-from-el-to-el.md | 4 +- .../migrate/nagios-to-centreon.md | 2 +- .../poller-display-to-remote-server.md | 14 +- .../add-a-remote-server-to-configuration.md | 2 +- .../monitoring-servers/communications.md | 12 +- .../create-snmp-traps-definitions.md | 6 +- .../reporting/report-development.md | 3 +- .../reporting/reports-publication-rule.md | 10 +- .../version-22.10-sidebars.json | 542 +- .../version-23.04-sidebars.json | 522 +- .../version-23.10-sidebars.json | 530 +- .../version-24.04-sidebars.json | 516 +- .../version-24.10-sidebars.json | 482 +- .../version-25.10-sidebars.json | 492 +- yarn.lock | 8235 ---------- 1441 files changed, 33784 insertions(+), 23146 deletions(-) create mode 100644 .github/workflows/clean-cache.yml delete mode 100644 babel.config.js create mode 100644 pnpm-lock.yaml rename src/theme/DocItem/Footer/{index.js => index.jsx} (97%) rename src/theme/DocVersionBanner/{index.js => index.jsx} (95%) rename src/theme/NavbarItem/{DocsVersionDropdownNavbarItem.js => DocsVersionDropdownNavbarItem.jsx} (100%) rename src/theme/TOC/{index.js => index.jsx} (97%) delete mode 100644 yarn.lock diff --git a/.github/workflows/archive.yml b/.github/workflows/archive.yml index 5109430696ce..c7e01e206927 100644 --- a/.github/workflows/archive.yml +++ b/.github/workflows/archive.yml @@ -12,20 +12,28 @@ concurrency: jobs: build: - runs-on: ubuntu-22.04 + runs-on: ubuntu-24.04 steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 + with: + fetch-depth: 0 + + - uses: pnpm/action-setup@fe02b34f77f8bc703788d5817da081398fad5dd2 # v4.0.0 + with: + version: 9 + run_install: false - name: Set up Node uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4 with: - node-version: 20 + node-version: 22 + cache: pnpm + cache-dependency-path: pnpm-lock.yaml - name: Install dependencies - uses: borales/actions-yarn@3766bb1335b98fb13c60eaf358fe20811b730a88 # v5.0.0 - with: - cmd: install --frozen-lockfile + run: pnpm install --frozen-lockfile + shell: bash - name: Redirect pp and cloud links to last documentation run: | @@ -34,10 +42,10 @@ jobs: shell: bash - name: Build documentation for ${{ github.event.inputs.version }} - run: ARCHIVED_VERSION="${{ github.event.inputs.version }}" yarn build + run: ARCHIVED_VERSION="${{ github.event.inputs.version }}" pnpm build - name: Store build archived doc in cache - uses: actions/cache/save@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + uses: actions/cache/save@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: path: "./build" key: "${{ github.sha }}-${{ github.run_id }}-build-archived-doc" @@ -47,7 +55,7 @@ jobs: runs-on: [self-hosted, infra] steps: - name: Restore built archived doc from cache - uses: actions/cache/restore@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: path: "./build" key: "${{ github.sha }}-${{ github.run_id }}-build-archived-doc" diff --git a/.github/workflows/clean-cache.yml b/.github/workflows/clean-cache.yml new file mode 100644 index 000000000000..6869c166a693 --- /dev/null +++ b/.github/workflows/clean-cache.yml @@ -0,0 +1,34 @@ +name: clean-cache + +on: + pull_request: + types: + - closed + +jobs: + clean-cache: + runs-on: ubuntu-24.04 + steps: + - name: Checkout sources + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 + + - name: Clean cache + run: | + gh extension install actions/gh-actions-cache + + REPO=${{ github.repository }} + BRANCH="refs/pull/${{ github.event.pull_request.number }}/merge" + + echo "Fetching list of cache key" + cacheKeysForPR=$(gh actions-cache list -R $REPO -B $BRANCH | cut -f 1 ) + + ## Setting this to not fail the workflow while deleting cache keys. + set +e + echo "Deleting caches..." + for cacheKey in $cacheKeysForPR + do + gh actions-cache delete $cacheKey -R $REPO -B $BRANCH --confirm + done + echo "Done" + env: + GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/documentation.yml b/.github/workflows/documentation.yml index 9cef2b4ba1cc..b40098920ae5 100644 --- a/.github/workflows/documentation.yml +++ b/.github/workflows/documentation.yml @@ -26,7 +26,7 @@ jobs: steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: Get changes uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # v3.0.2 @@ -169,34 +169,60 @@ jobs: steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 with: fetch-depth: 0 + - uses: pnpm/action-setup@fe02b34f77f8bc703788d5817da081398fad5dd2 # v4.0.0 + with: + version: 9 + run_install: false + - name: Set up Node uses: actions/setup-node@0a44ba7841725637a19e28fa30b79a866c81b0a6 # v4.0.4 with: - node-version: 20 - cache: yarn + node-version: 22 + cache: pnpm + cache-dependency-path: pnpm-lock.yaml - name: Install dependencies - uses: borales/actions-yarn@3766bb1335b98fb13c60eaf358fe20811b730a88 # v5.0.0 + run: pnpm install --frozen-lockfile + shell: bash + + - name: Restore docusaurus build from cache + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: - cmd: install --frozen-lockfile + path: | + .docusaurus + build + key: docusaurus-build-${{ matrix.environment }}-${{ github.head_ref || github.ref_name }} + restore-keys: | + docusaurus-build-${{ matrix.environment }}-staging - name: Build documentation - run: yarn build + run: pnpm build env: PP: ${{ matrix.pp }} CLOUD: ${{ matrix.cloud }} VERSIONS: ${{ matrix.environment == 'staging' && matrix.versions || matrix.next_version }} BASE_URL: ${{ github.event_name == 'pull_request' && format('/previews/pr-{0}/{1}', github.event.pull_request.number, matrix.environment) || '' }} - - name: Store build in cache - uses: actions/cache/save@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + - name: Clear previous docker image from cache + run: | + curl \ + -X DELETE \ + -H "Accept: application/vnd.github.v3+json" \ + -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \ + https://api.github.com/repos/centreon/centreon-documentation/actions/caches?key=docusaurus-build-${{ matrix.environment }}-${{ github.head_ref || github.ref_name }} + shell: bash + + - name: Store docusaurus build cache in cache + uses: actions/cache/save@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: - path: "./build" - key: "${{ github.sha }}-${{ github.run_id }}-build-doc-${{ matrix.environment }}" + path: | + .docusaurus + build + key: docusaurus-build-${{ matrix.environment }}-${{ github.head_ref || github.ref_name }} deploy-preview: if: ${{ github.event_name == 'pull_request' }} @@ -212,13 +238,15 @@ jobs: steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: Restore build from cache - uses: actions/cache/restore@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: - path: "./build" - key: "${{ github.sha }}-${{ github.run_id }}-build-doc-${{ matrix.environment }}" + path: | + .docusaurus + build + key: docusaurus-build-${{ matrix.environment }}-${{ github.head_ref || github.ref_name }} fail-on-cache-miss: true - name: Setup awscli @@ -292,10 +320,10 @@ jobs: steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: Restore build from cache - uses: actions/cache/restore@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: path: "./build" key: "${{ github.sha }}-${{ github.run_id }}-build-doc-staging" @@ -324,10 +352,10 @@ jobs: steps: - name: Checkout sources - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0 + uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: Restore build from cache - uses: actions/cache/restore@0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 # v4.0.2 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4.1.2 with: path: "./build" key: "${{ github.sha }}-${{ github.run_id }}-build-doc-next" diff --git a/README.md b/README.md index a38368f71459..e222064ccff8 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ let you know so that you can rebase it. To understand how the documentation is structured, you may have a look to the [Docusaurus project](https://docusaurus.io/). -We're using version 2. +We're using version 3. ### Pull request guidelines @@ -57,7 +57,7 @@ set by the existing documentation. ## How to build the documentation locally -This website is built using [Docusaurus 2](https://docusaurus.io/), a modern static website generator. +This website is built using [Docusaurus 3](https://docusaurus.io/), a modern static website generator. ### Which branch should I base my PRs on? @@ -65,9 +65,9 @@ Use branch **staging**. We will merge the PR into production once it has gone th ### Prerequisites -1. Install **yarn**. On Windows: https://classic.yarnpkg.com/latest.msi +1. Install [**pnpm** (version 9)]: https://pnpm.io/installation -2. Install **node.js** (version 14 minimum): https://nodejs.org/en/download/ +2. Install **node.js** (version 18 minimum): https://nodejs.org/en/download/ 3. Clone the repository : @@ -85,28 +85,28 @@ Use branch **staging**. We will merge the PR into production once it has gone th git checkout ``` -4. Install dependencies: +5. Install dependencies: ``` - yarn install --frozen-lockfile + pnpm install --frozen-lockfile ``` ### Building the documentation website * Build the EN or FR version of the site (faster) - * EN: ```yarn start``` - * FR: ```yarn start --locale=fr``` + * EN: ```pnpm start``` + * FR: ```pnpm start --locale=fr``` The website opens in your browser at the following address: http://localhost:3000/. Most changes are reflected live without having to restart the server. * If you really need to build the whole website, use the following command (but be aware it takes a long time to build): ``` - yarn build + pnpm build ``` - Then use the `npm run serve` command to open the website in your browser. + Then use the `pnpm run serve` command to open the website in your browser. ## Adding files to the table of contents diff --git a/babel.config.js b/babel.config.js deleted file mode 100644 index 8edcbf0b75f2..000000000000 --- a/babel.config.js +++ /dev/null @@ -1,3 +0,0 @@ -module.exports = { - presets: [require.resolve('@docusaurus/core/lib/babel/preset')], -}; \ No newline at end of file diff --git a/cloud/alerts-notifications/notif-configuration.md b/cloud/alerts-notifications/notif-configuration.md index 4605e199399a..cd1e6cbd4141 100644 --- a/cloud/alerts-notifications/notif-configuration.md +++ b/cloud/alerts-notifications/notif-configuration.md @@ -40,12 +40,12 @@ Resources are checked according to the following parameters: | Macro | Description | Example | | ----- | ----------- |-------- | - |{{NOTIFICATIONTYPE}}| **Recovery**, **Warning**, **Critical** or **Unknown** for a service; **Recovery**, **Down** or **Unreachable** for a host. | CRITICAL | - {{NAME}}| The name of the service or host. For a service, the name of the host it is attached to is also given. | central/proc-ntpd | - {{ID}}| An internal ID for the resource. This can be used for API calls. | 41:209 | - {{STATE}}| The [status](./concepts.md) that the resource has just entered. | CRITICAL | - {{SHORTDATETIME}}| Date and time in the following format: MM/DD/YY h:mm:ss | 10/18/23 12:20:42 | - {{LONGDATETIME}}| Date and time, including the day of the week. | Wednesday October 18, 2023, 12:20:42 | - {{OUTPUT}}| The output of the check command, i.e. the text that is displayed in the **Information** column in the **Resources status** page. | CRITICAL: Number of current processes running: 0 | + |\{\{NOTIFICATIONTYPE\}\}| **Recovery**, **Warning**, **Critical** or **Unknown** for a service; **Recovery**, **Down** or **Unreachable** for a host. | CRITICAL | + \{\{NAME\}\}| The name of the service or host. For a service, the name of the host it is attached to is also given. | central/proc-ntpd | + \{\{ID\}\}| An internal ID for the resource. This can be used for API calls. | 41:209 | + \{\{STATE\}\}| The [status](./concepts.md) that the resource has just entered. | CRITICAL | + \{\{SHORTDATETIME\}\}| Date and time in the following format: MM/DD/YY h:mm:ss | 10/18/23 12:20:42 | + \{\{LONGDATETIME\}\}| Date and time, including the day of the week. | Wednesday October 18, 2023, 12:20:42 | + \{\{OUTPUT\}\}| The output of the check command, i.e. the text that is displayed in the **Information** column in the **Resources status** page. | CRITICAL: Number of current processes running: 0 | 3. Click the **Save** button at the top right of the panel. The new notification rule appears in the list. You may have to wait up to 5 minutes before the rule starts being applied. diff --git a/cloud/alerts-notifications/resources-status.md b/cloud/alerts-notifications/resources-status.md index eb97e45588b0..08500cc481f0 100644 --- a/cloud/alerts-notifications/resources-status.md +++ b/cloud/alerts-notifications/resources-status.md @@ -296,7 +296,7 @@ Graphs display metric evolution over a given period. This can be defined in the - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Whenever the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/cloud/installation/poller-troubleshoot.md b/cloud/installation/poller-troubleshoot.md index 800caa9783ff..8ddc2f82ba14 100644 --- a/cloud/installation/poller-troubleshoot.md +++ b/cloud/installation/poller-troubleshoot.md @@ -151,10 +151,10 @@ If it doesn't, check the logs for errors. ### Step 1: Test network connectivity -Check that the poller can send real-time data to the Centreon Cloud platform. Execute the following command (replace **{org-code}** by your organization code): +Check that the poller can send real-time data to the Centreon Cloud platform. Execute the following command (replace **\** by your organization code): ```shell -nc -zv -w 5 broker-{org-code}.euwest1.centreon.cloud 443 +nc -zv -w 5 broker-.euwest1.centreon.cloud 443 ``` The command should print a message like this one: @@ -227,10 +227,10 @@ Modify log levels to get more information about what Engine is doing. ### Step 5: Enable and review cbmod logs -1. Edit the Centreon Broker module configuration (replace **{hostname}** by the correct value): +1. Edit the Centreon Broker module configuration (replace **\** by the correct value): ```shell - vi /etc/centreon-broker/{hostname}-module.json + vi /etc/centreon-broker/-module.json ``` 2. Adjust the **centreonBroker.log.loggers** object to the desired log level. @@ -259,6 +259,6 @@ If all troubleshooting steps have failed, contact [our support team](https://sup | Use to debug what? | Process | File | Symptoms | |--------------------|---------|------|----------| -| Installation of the poller | | {scriptdir}/logs/register-poller.log | | +| Installation of the poller | | \/logs/register-poller.log | | | Centreon Engine | centengine | /var/log/centreon-engine/centengine.log |
  • Checks are not performed
  • Objects that have been deleted are still monitored
| | Gorgone | gorgoned | /var/log/centreon-gorgone/gorgoned.log | Actions are not triggered: acknowledgements, downtimes, force checks, autodiscovery | diff --git a/docusaurus.config.js b/docusaurus.config.js index f7c1c4c5a0dc..839474c13760 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -1,11 +1,7 @@ -// @ts-nocheck -// Note: type annotations allow type checking and IDEs autocompletion +import { themes as prismThemes } from 'prism-react-renderer'; -const lightCodeTheme = require('prism-react-renderer/themes/github'); -const darkCodeTheme = require('prism-react-renderer/themes/dracula'); - -const availableVersions = require('./versions.json'); -const archivedVersions = require('./archivedVersions.json'); +import availableVersions from './versions.json'; +import archivedVersions from './archivedVersions.json'; const archivedVersion = process.env.ARCHIVED_VERSION ?? null; @@ -55,6 +51,10 @@ const config = { version: archivedVersion ?? null, }, + future: { + experimental_faster: true, + }, + title: 'Centreon Documentation', tagline: '', url: 'https://docs.centreon.com', @@ -119,7 +119,7 @@ const config = { }, blog: false, theme: { - customCss: require.resolve('./src/css/custom.css'), + customCss: ['./src/css/custom.css'], }, gtag: { trackingID: 'G-BGL69N5GPJ', @@ -148,14 +148,14 @@ const config = { disableInDev: true, }, ], - 'plugin-image-zoom', + 'docusaurus-plugin-image-zoom', ]; if (archivedVersion) { plugins = [ ...plugins, [ - require.resolve("@cmfcmf/docusaurus-search-local"), + '@cmfcmf/docusaurus-search-local', { indexBlog: false, language: ["en", "fr"], @@ -173,7 +173,7 @@ const config = { id: 'cloud', path: 'cloud', routeBasePath: 'cloud', - sidebarPath: require.resolve('./cloud/sidebarsCloud.js'), + sidebarPath: './cloud/sidebarsCloud.js', breadcrumbs: true, editUrl: 'https://github.com/centreon/centreon-documentation/edit/staging/', editLocalizedFiles: true, @@ -192,7 +192,7 @@ const config = { id: 'pp', path: 'pp', routeBasePath: 'pp', - sidebarPath: require.resolve('./pp/sidebarsPp.js'), + sidebarPath: './pp/sidebarsPp.js', breadcrumbs: true, editUrl: 'https://github.com/centreon/centreon-documentation/edit/staging/', editLocalizedFiles: true, @@ -217,13 +217,21 @@ const config = { contextualSearch: true, }, - zoomSelector: '.markdown :not(.authority-availability) > img', + zoom: { + selector: '.markdown img', + background: { + light: 'rgb(255, 255, 255)', + dark: 'rgb(0, 0, 61)' + }, + config: {} + }, prism: { - theme: lightCodeTheme, - darkTheme: darkCodeTheme, + theme: prismThemes.github, + darkTheme: prismThemes.dracula, defaultLanguage: 'shell', additionalLanguages: [ + 'diff', 'java', 'json', 'cpp', @@ -387,23 +395,6 @@ const config = { copyright: `Copyright © 2005 - 2024 Centreon`, }, }), - webpack: { - jsLoader: (isServer) => ({ - loader: require.resolve('swc-loader'), - options: { - jsc: { - "parser": { - "syntax": "typescript", - "tsx": true - }, - target: 'es2017', - }, - module: { - type: isServer ? 'commonjs' : 'es6', - } - }, - }), - } }; -module.exports = config; +export default config; diff --git a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/notif-configuration.md b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/notif-configuration.md index a5a217f99fde..94844c29b7f0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/notif-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/notif-configuration.md @@ -40,12 +40,12 @@ Les ressources sont contrôlées selon les paramètres suivants : | Macro | Description | Exemple | | ----- | ----------- |-------- | - |{{NOTIFICATIONTYPE}}| **Recovery**, **Warning**, **Critical** or **Unknown** pour un service; **Recovery**, **Down** ou **Unreachable** pour un hôte. | CRITICAL | - {{NAME}}| Le nom du service ou de l'hôte. Pour un service, le nom de l'hôte auquel celui-ci est rattaché est également indiqué. | central/proc-ntpd | - {{ID}}| Un ID interne pour cette ressource. Cet ID peut être utilisé pour des appels API. | 41:209 | - {{STATE}}| Le [statut](./concepts.md) dans lequel la ressource vient de passer. | CRITICAL | - {{SHORTDATETIME}}| Date et heure au format suivant : MM/JJ/AA hh:mm:ss | 10/18/23 12:20:42 | - {{LONGDATETIME}}| Date et heure, avec le jour de la semaine. | Wednesday October 18, 2023, 12:20:42 | - {{OUTPUT}}| La sortie de la commande de contrôle, c'est-à-dire le texte affiché dans la colonne **Information** de la page **Statut des ressources**. | CRITICAL: Number of current processes running: 0 | + |\{\{NOTIFICATIONTYPE\}\}| **Recovery**, **Warning**, **Critical** or **Unknown** pour un service; **Recovery**, **Down** ou **Unreachable** pour un hôte. | CRITICAL | + \{\{NAME\}\}| Le nom du service ou de l'hôte. Pour un service, le nom de l'hôte auquel celui-ci est rattaché est également indiqué. | central/proc-ntpd | + \{\{ID\}\}| Un ID interne pour cette ressource. Cet ID peut être utilisé pour des appels API. | 41:209 | + \{\{STATE\}\}| Le [statut](./concepts.md) dans lequel la ressource vient de passer. | CRITICAL | + \{\{SHORTDATETIME\}\}| Date et heure au format suivant : MM/JJ/AA hh:mm:ss | 10/18/23 12:20:42 | + \{\{LONGDATETIME\}\}| Date et heure, avec le jour de la semaine. | Wednesday October 18, 2023, 12:20:42 | + \{\{OUTPUT\}\}| La sortie de la commande de contrôle, c'est-à-dire le texte affiché dans la colonne **Information** de la page **Statut des ressources**. | CRITICAL: Number of current processes running: 0 | 3. Cliquez sur le bouton **Save** en haut à droite du panneau. La nouvelle règle de notification apparaît dans la liste. Elle peut mettre jusqu'à 5 minutes pour commencer à s'appliquer. diff --git a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/resources-status.md index 2fb776f1fa5d..0f9562fa46dd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/alerts-notifications/resources-status.md @@ -312,7 +312,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/installation/poller-troubleshoot.md b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/installation/poller-troubleshoot.md index 69ab6418fc4c..83578ae9883a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/installation/poller-troubleshoot.md +++ b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/installation/poller-troubleshoot.md @@ -152,10 +152,10 @@ Si le fichier ne contient pas les lignes ci-dessus, vérifiez les autres message ### Étape 1 : Tester la connectivité réseau -Vérifiez que le collecteur peut envoyer des données temps-réel à la plateforme Centreon Cloud. Exécutez la commande suivante (remplacez **{org-code}** par le code de votre organisation) : +Vérifiez que le collecteur peut envoyer des données temps-réel à la plateforme Centreon Cloud. Exécutez la commande suivante (remplacez **\** par le code de votre organisation) : ```shell -nc -zv -w 5 broker-{org-code}.euwest1.centreon.cloud 443 +nc -zv -w 5 broker-.euwest1.centreon.cloud 443 ``` La commande devrait retourner un message similaire à celui-ci : @@ -228,10 +228,10 @@ Modifiez les niveaux de log pour obtenir plus d'informations sur ce que Engine f ### Étape 5 : Activer et inspecter les logs cbmod -1. Éditez la configuration de Centreon Broker module (remplacez **{hostname}** par la valeur correcte) : +1. Éditez la configuration de Centreon Broker module (remplacez **\** par la valeur correcte) : ```shell - vi /etc/centreon-broker/{hostname}-module.json + vi /etc/centreon-broker/-module.json ``` 2. Ajustez l'objet **centreonBroker.log.loggers** au niveau de log désiré. @@ -260,6 +260,6 @@ Si toutes ces étapes de dépannage ont échoué, contactez [notre équipe suppo | Utiliser pour débugguer quoi? | Process | Fichier | Symptômes | |--------------------|---------|------|----------| -| Installation du collecteur | | {scriptdir}/logs/register-poller.log | | +| Installation du collecteur | | \/logs/register-poller.log | | | Centreon Engine | centengine | /var/log/centreon-engine/centengine.log |
  • Les contrôles ne sont pas effectués
  • Les objets supprimés sont toujours supervisés
| | Gorgone | gorgoned | /var/log/centreon-gorgone/gorgoned.log | Les actions ne se déclenchent pas : acquittements, plages de maintenance, contrôles forcés, autodiscovery | diff --git a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/service-mapping/ba-management.md index 406951867b1d..e2c8daeedf87 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-cloud/current/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs-cloud/current/service-mapping/ba-management.md @@ -39,7 +39,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md index b9fdea83740f..4a2dc7807982 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md @@ -32,7 +32,7 @@ the binary it uses exists or doesn't contain a typo. On RPM-based systems, you can use the following command to identify what's the package is providing the missing binary: `yum whatprovides "*/the_binary_name"` -### UNKNOWN: Cannot write statefile '/var/lib/centreon/centplugins/' +### UNKNOWN: Cannot write statefile '/var/lib/centreon/centplugins/\' The most common cause is inappropriate rights on the cache directory (`/var/lib/centreon/centplugins`) or the cache file itself. It can also be the result of an inconsistent installation @@ -52,7 +52,7 @@ If directory rights are ok, check also the rights of the cache file: `stat /var/lib/centreon/centplugins/`. The expected result is: ```bash -File: '/var/lib/centreon/centplugins/' +File: '/var/lib/centreon/centplugins/\' [...] Access: (0664/-rw-rw-r--) Uid: ( 994/centreon-engine) Gid: ( 991/centreon-engine) [...] @@ -179,7 +179,7 @@ It may also happen when the API returns an error instead of the expected data st You may want to dig deeper into this by adding the `--debug` flag to your command line to get more information on the query and data received. -### UNKNOWN: 500 Can't connect to `:` () +### UNKNOWN: 500 Can't connect to `:` (\) When grabbing metrics or statuses from an API, multiple issues can show up because of proxies, remote devices' certificates, or simply the check configuration. @@ -294,7 +294,7 @@ allows your monitoring server to send remote command execution. Do not forget to restart your NRPE daemon to update the configuration. -### NRPE: Command not defined +### NRPE: Command \ not defined The NRPE Server throws this error when the client asks to run a command it doesn't understand. diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md index a217e6714a2b..934439c57b84 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md @@ -177,8 +177,9 @@ wmic useraccount where name="@USERNAME@" get name,sid ``` Output: ->

Name          SID

->@USRNAME@  S-1-5-21-3051596711-3341658857-577043467-1000 +> Name          SID +> +> @USRNAME@  S-1-5-21-3051596711-3341658857-577043467-1000 #### Récupérer le SDDL actuel pour Service Control Manager @@ -396,17 +397,17 @@ $Thumbprint=Invoke-Command -ComputerName $FQDN ` Set-WSManInstance -ResourceURI winrm/config/Listener ` - -SelectorSet @{Address="*";Transport="HTTPS"} ` + -SelectorSet @\{Address="*";Transport="HTTPS"\} ` -ComputerName $FQDN ` - -ValueSet @{CertificateThumbprint=$Thumbprint} + -ValueSet @\{CertificateThumbprint=$Thumbprint\} -winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@{Hostname=".$FQDN.".;CertificateThumbprint=".$Thumbprint."}" +winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@\{Hostname=".$FQDN.".;CertificateThumbprint=".$Thumbprint."\}" ``` * Copiez ce script à l'emplacement suivant pour pouvoir le déployer massivement : ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` Dans notre cas, voilà le résultat : @@ -619,7 +620,7 @@ $RootSecurity.PsBase.InvokeMethod("SetSd",$SdList) * Copiez ce script à l'emplacement suivant pour pouvoir déployer massivement ce script. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` Dans notre cas, le résultat est le suivant : @@ -720,7 +721,7 @@ Invoke-Expression -Command:$SetPermissionsCommand * Copiez ce script à l'emplacement suivant pour pouvoir le déployer massivement. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` * Retournez dans votre politique **Enable WinRM**. @@ -822,7 +823,7 @@ Set-Item -Path WSMan:\localhost\Service\RootSDDL -Value $new_sddl -Force * Copiez ce script à l'emplacement suivant pour pouvoir le déployer massivement. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` * Retournez dans votre politique **Enable WinRM**. @@ -865,9 +866,9 @@ Set-Item -Path WSMan:\localhost\Service\RootSDDL -Value $new_sddl -Force * Spécifiez les paramètres suivants : * Action : **Start a program** * Programme/script : **PowerShell.exe** - * Ajouter arguments : **-file C:\Windows\Temp\RootSDDL-Permision.ps1****@SERVICE_USERNAME@** + * Ajouter arguments : **-file C:\Windows\Temp\RootSDDL-Permision.ps1**\**@SERVICE_USERNAME@**\ * Ajustez ce paramètre pour qu'il corresponde au paramètre "Destination du fichier" précédemment configuré - * Dans notre exemple, l'argument est **-file C:\Windows\Temp\RootSDDL-Permision.ps1sa_centreon**. + * Dans notre exemple, l'argument est **-file C:\Windows\Temp\RootSDDL-Permision.ps1\sa_centreon\**. ![image](../../../../assets/integrations/plugin-packs/how-to-guides/windows-winrm-wsman-gpo-tutorial/windows-winrm-wsman-rootsddl-2.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ansible-tower.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ansible-tower.md index a2856ce9fcb7..a6e534e418ac 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ansible-tower.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ansible-tower.md @@ -221,12 +221,12 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /default/ | | | FILTERNAME | Filter host name (can use regexp) | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -260,7 +260,7 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /default/ | | | FILTERNAME | Filter job template name (can use regexp) | | | | WARNINGCANCELED | Threshold | | | | CRITICALCANCELED | Threshold | | | @@ -268,8 +268,8 @@ yum install centreon-plugin-Applications-Ansible-Tower | CRITICALDEFAULT | Threshold | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGNEVER | Threshold | | | | CRITICALNEVER | Threshold | | | | WARNINGPENDING | Threshold | | | @@ -309,7 +309,7 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /default/ | | | FILTERNAME | Filter schedule name (can use regexp) | | | | WARNINGCANCELED | Threshold | | | | CRITICALCANCELED | Threshold | | | @@ -317,8 +317,8 @@ yum install centreon-plugin-Applications-Ansible-Tower | CRITICALDEFAULT | Threshold | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\}=~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGNEVER | Threshold | | | | CRITICALNEVER | Threshold | | | | WARNINGPENDING | Threshold | | | @@ -355,9 +355,9 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --password='' \ --custommode='api' \ --filter-name='' \ - --unknown-job-status='%{last\_job\_status} =~ /default/' \ + --unknown-job-status='%\{last_job_status\}=~ /default/' \ --warning-job-status='' \ - --critical-job-status='%{last\_job\_status} =~ /failed/' \ + --critical-job-status='%\{last_job_status\}=~ /failed/' \ --warning-total='' \ --critical-total='' \ --warning-failed='' \ @@ -440,7 +440,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -486,9 +486,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter host name (can use regexp). | | --display-failed-hosts | Display failed hosts list in verbose output. | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'failed'. | @@ -513,9 +513,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --launch-extra-vars | yaml format text that contains extra variables to pass on. | | --launch-max-retries | Number of retries to get job result once launched (default: 5). | | --launch-retry-interval | Number of seconds between retries (default : 10). | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'successful', 'failed', 'running', 'canceled', 'pending', 'default', 'never'. | @@ -560,9 +560,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter schedule name (can use regexp). | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\}=~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\}=~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'successful', 'failed', 'running', 'canceled', 'pending', 'default', 'never', 'start-last-time' (s). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md index 84278464fba0..38605a427125 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md @@ -174,12 +174,12 @@ yum install centreon-plugin-Applications-Clamav-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------|:-----------:| -| CRITICALDAILYDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | %{last\_dailydb\_version} ne %{current\_dailydb\_version} \|\| %{current\_dailydb\_timediff} \> 432000 | | -| WARNINGDAILYDBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | | | -| WARNINGENGINESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | | | -| CRITICALENGINESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_engine\_version} ne %{current\_engine\_version}'). You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | | | -| CRITICALMAINDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | %{last\_maindb\_version} ne %{current\_maindb\_version} | | -| WARNINGMAINDBSTATUS | Define the conditions to match for the status to be WARNING.You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | | | +| CRITICALDAILYDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | %\{last_dailydb_version\}ne %\{current_dailydb_version\}\|\| %\{current_dailydb_timediff\}\> 432000 | | +| WARNINGDAILYDBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | | | +| WARNINGENGINESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | | | +| CRITICALENGINESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_engine_version\}ne %\{current_engine_version\}'). You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\}| | | +| CRITICALMAINDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | %\{last_maindb_version\}ne %\{current_maindb_version\} | | +| WARNINGMAINDBSTATUS | Define the conditions to match for the status to be WARNING.You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -207,9 +207,9 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-engine-status='' \ --critical-engine-status='' \ --warning-maindb-status='' \ - --critical-maindb-status='%{last_maindb_version} ne %{current_maindb_version}' \ + --critical-maindb-status='%\{last_maindb_version\} ne %\{current_maindb_version\}' \ --warning-dailydb-status='' \ - --critical-dailydb-status='%{last_dailydb_version} ne %{current_dailydb_version} || %{current_dailydb_timediff} > 432000' + --critical-dailydb-status='%\{last_dailydb_version\} ne %\{current_dailydb_version\} || %\{current_dailydb_timediff\} > 432000' ``` La commande devrait retourner un message de sortie similaire à : @@ -268,7 +268,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -309,12 +309,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --nameservers | Set nameserver to query (can be multiple). The system configuration is used by default. | | --maindb-file | Antivirus main.cvd file (default: '/var/lib/clamav/main.cvd'). | | --dailydb-file | Antivirus daily.cvd file (default: '/var/lib/clamav/daily.cvd'). | -| --warning-engine-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | -| --critical-engine-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_engine\_version} ne %{current\_engine\_version}'). You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | -| --warning-maindb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | -| --critical-maindb-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_maindb\_version} ne %{current\_maindb\_version}'). You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | -| --warning-dailydb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | -| --critical-dailydb-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_dailydb\_version} ne %{current\_dailydb\_version} \|\| %{current\_dailydb\_timediff} \> 432000'). You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | +| --warning-engine-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | +| --critical-engine-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_engine_version\}ne %\{current_engine_version\}'). You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | +| --warning-maindb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | +| --critical-maindb-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_maindb_version\}ne %\{current_maindb_version\}'). You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | +| --warning-dailydb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | +| --critical-dailydb-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_dailydb_version\}ne %\{current_dailydb_version\}\|\| %\{current_dailydb_timediff\}\> 432000'). You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md index 567003f96225..108e57cf25cf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md @@ -151,7 +151,7 @@ de commande depuis un collecteur Centreon en vous connectant avec l'utilisateur /usr/lib/centreon/plugins//centreon_kaspersky_snmp.pl \ --plugin=apps::antivirus::kaspersky::snmp::plugin --mode=protection \ --hostname=10.0.0.1 --snmp-version='2c' --snmp-community='kaseprsky_ro' \ - --warning-status='%{status} =~ /Warning/i' --critical-status='%{status} =~ /Critical/i' + --warning-status='%\{status\} =~ /Warning/i' --critical-status='%\{status\} =~ /Critical/i' --warning-no-antivirus='0' --critical-no-antivirus='' --warning-no-real-time='0' --critical-no-real-time='' \ --warning-not-acceptable-level='0' --critical-not-acceptable-level='' \ --warning-not-cured-objects='0' --critical-not-cured-objects='' \ diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md index 8a1c6d26a27c..7b9e78cfb05c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md @@ -491,7 +491,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-awa-jmx.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-awa-jmx.md index 91e58b29d7d6..23fe99e4173e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-awa-jmx.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-awa-jmx.md @@ -115,7 +115,7 @@ l'utilisateur **centreon-engine**: --password='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /GREEN/i' \ + --critical-status='%\{status\} !~ /GREEN/i' \ --use-new-perfdata ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-bluemind-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-bluemind-ssh.md index 7c4d2fce28c2..7f54859b0fbd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-bluemind-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-bluemind-ssh.md @@ -502,7 +502,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md index 600b81699846..6231d5ce9a1b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md @@ -198,8 +198,8 @@ yum install centreon-plugin-Applications-Cisco-Ssms-Restapi | ACCOUNT | Check account name (required. Multiple option) | | X | | FILTERCOUNTERS | Only display some counters (regexp can be used). Example: --filter-counters='status' | | | | FILTERLICENSENAME | Filter license name (can be a regexp) | | | -| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in compliance/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /in compliance/i | | -| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in compliance/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /in compliance/i | | +| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -234,7 +234,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-counters= \ --filter-license-name='' \ --warning-license-status='' \ - --critical-license-status='%{status} !~ /in compliance/i' \ + --critical-license-status='%\{status\} !~ /in compliance/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -298,7 +298,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -365,9 +365,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --account | Check account name (required. Multiple option). | | --filter-license-name | Filter license name (can be a regexp). | -| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-license-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-license-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in compliance/i'). You can use the following variables: %{status}, %{display} | +| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-license-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-license-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in compliance/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md index 237c902bb9b2..4e7a21137e60 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md @@ -231,8 +231,8 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | CRITICALALERTSINFO | Threshold | | | | WARNINGALERTSTOTAL | Threshold | | | | CRITICALALERTSTOTAL | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | %{severity} =~ /warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | %{severity} =~ /critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | %\{severity\} =~ /warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | %\{severity\} =~ /critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -248,10 +248,10 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | TIMEFRAME | Set timeframe in seconds (E.g '3600' to check last 60 minutes) | | | | WARNINGJOBSTOTAL | Threshold | | | | CRITICALJOBSTOTAL | Threshold | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type} | %{status} =~ /abnormal/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status}, %{type} | %{status} =~ /errors\|failed/i | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\} | %\{status\} =~ /abnormal/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\}, %\{type\} | %\{status\} =~ /errors\|failed/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -261,15 +261,15 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| | FILTERMEDIAAGENTID | Filter media agents by ID (can be a regexp) | | | | FILTERMEDIAAGENTNAME | Filter media agents by name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | | | WARNINGMEDIAAGENTSOFFLINE | Threshold | | | | CRITICALMEDIAAGENTSOFFLINE | Threshold | | | | WARNINGMEDIAAGENTSONLINE | Threshold | | | | CRITICALMEDIAAGENTSONLINE | Threshold | | | | WARNINGMEDIAAGENTSTOTAL | Threshold | | | | CRITICALMEDIAAGENTSTOTAL | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | %{is\_maintenance} eq "no" and %{status} eq "offline" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | %\{is_maintenance\} eq "no" and %\{status\} eq "offline" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -278,8 +278,8 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter storage pools by name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Threshold | | | | CRITICALUSAGE | Threshold | | | | WARNINGUSAGEFREE | Threshold | | | @@ -312,7 +312,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --proto='https' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /online/i' \ + --critical-status='%\{status\} !~ /online/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -382,7 +382,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -444,8 +444,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-alert-name | Filter alerts by name (can be a regexp). | | --filter-alert-type | Filter alerts by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning/') You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical/'). You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning/') You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical/'). You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | | --memory | Only check new alerts. | @@ -459,10 +459,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-client-name | Filter jobs by client name (can be a regexp). | | --filter-client-group | Filter jobs by client groups (can be a regexp). | | --timeframe | Set timeframe in seconds (E.g '3600' to check last 60 minutes). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /abnormal/i') You can use the following variables: %{display}, %{status}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /errors\|failed/i'). You can use the following variables: %{display}, %{status}, %{type} | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /abnormal/i') You can use the following variables: %\{display\}, %\{status\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /errors\|failed/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\} | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-total'. | @@ -472,9 +472,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-media-agent-id | Filter media agents by ID (can be a regexp). | | --filter-media-agent-name | Filter media agents by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_maintenance} eq "no" and %{status} eq "offline"'). You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_maintenance\} eq "no" and %\{status\} eq "offline"'). You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'media-agents-total', 'media-agents-online', 'media-agents-offline'. | @@ -484,9 +484,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter storage pools by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /online/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /online/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md index e1abdcb68d12..f267b1547034 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md @@ -254,8 +254,8 @@ yum install centreon-plugin-Applications-Databases-Elasticsearch | CRITICALSHARDSTOTAL | Critical threshold | | | | WARNINGSHARDSUNASSIGNED | Warning threshold | | | | CRITICALSHARDSUNASSIGNED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{status} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{status} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{status\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\} | %\{status\} =~ /red/i | | | WARNINGTASKSPENDING | Warning threshold | | | | CRITICALTASKSPENDING | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -283,8 +283,8 @@ yum install centreon-plugin-Applications-Databases-Elasticsearch | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds} | %{status} !~ /active/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\} | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -394,7 +394,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -439,8 +439,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* | Warning threshold. Can be: 'nodes-total', 'nodes-data', 'nodes-coordinating', 'nodes-master', 'nodes-ingest', 'indices-total', 'shards-total', 'shards-active-count', 'shards-active-percentage', 'shards-unassigned', 'shards-relocating', 'shards-initializing', 'tasks-pending', 'documents-total', 'data-size'. | | --critical-* | Critical threshold. Can be: 'nodes-total', 'nodes-data', 'nodes-coordinating', 'nodes-master', 'nodes-ingest', 'indices-total', 'shards-total', 'shards-active-count', 'shards-active-percentage', 'shards-unassigned', 'shards-relocating', 'shards-initializing', 'tasks-pending', 'documents-total', 'data-size'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}. | @@ -451,16 +451,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* | Warning threshold. Can be: 'documents-total', 'data-size-primaries', 'data-size-total', 'shards-active', 'shards-unassigned'. | | --critical-* | Critical threshold. Can be: 'documents-total', 'data-size-primaries', 'data-size-total', 'shards-active', 'shards-unassigned'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{display}, %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{display}, %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{display\}, %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{display\}, %\{status\}. | | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-firebird.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-firebird.md index c25e00924ffb..02708d1487e4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-firebird.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-firebird.md @@ -16,7 +16,7 @@ yum install centreon-plugin-Applications-Databases-Firebird ### Dependencies Please install perl module DBD::Firebird: - Follow the readme, because you need +\ Follow the readme, because you need to install the Firebird C library also. ## Centreon Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-influxdb.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-influxdb.md index 1f1c353b7ca5..0ea6b5196fee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-influxdb.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-influxdb.md @@ -279,10 +279,10 @@ yum install centreon-plugin-Applications-Databases-Influxdb | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | INSTANCE | Set the instance label for which the results should be calculated (Example: --instance='name'). The instance label must be the same label as the "GROUP BY" keyword | | X | -| OUTPUT | Set the output for each instance (Example: --output='Object %{instance} value is {label}') | | X | +| OUTPUT | Set the output for each instance (Example: --output='Object %\{instance\} value is \{label\}') | | X | | MULTIPLEOUTPUT | Set the global output in case everything is fine for multiple instances (Example: --multiple-output='All instance values are ok') | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %{instance} and any other labels you set through --query | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %{instance} and any other labels you set through --query | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -394,7 +394,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -419,7 +419,7 @@ Les options génériques sont listées ci-dessous : | --username | Specify username for authentication. | | --password | Specify password for authentication. | | --timeout | Set timeout in seconds (Default: 10). | -| --unknown-http-status | Threshold unknown for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-http-status | Threshold unknown for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-http-status | Warning threshold for http response code. | | --critical-http-status | Critical threshold for http response code. | | --http-peer-addr | Set the address you want to connect to. Useful if hostname is only a vhost, to avoid IP resolution. | @@ -478,10 +478,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --query | Set a InfluxQL query. Query option must be like--query='label,query'. Query must contain an "AS" keyword to rename the column of the selected data, and must match the label. (Example: --query='mymetric,SELECT the\_data AS "mymetric" FROM "database"."retention"."measurement" GROUP BY "instance"') | | --instance | Set the instance label on which the results should be calculate for (Example: --instance='name'). The instance label must be the same label as the "GROUP BY" keyword. | -| --output | Set the output for each instances (Example: --output='Object %{instance} value is {label}'). | +| --output | Set the output for each instances (Example: --output='Object %\{instance\} value is \{label\}'). | | --multiple-output | Set the global output in case everything is fine for multiple instances (Example: --multiple-output='All instance values are ok'). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %{instance} and any other labels you set through --query. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %{instance} and any other labels you set through --query. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query. | | --aggregation | Set the aggregation on metric values (Can be: 'average', 'min', 'max', 'sum') (Default: 'average'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md index 882505230258..311fbbae7243 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md @@ -255,9 +255,9 @@ yum install centreon-plugin-Applications-Databases-Informix-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERNAME | Filter chunk name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /inconsistent/'). You can use the following variables: %{status}, %{display} | %{status} =~ /inconsistent/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /inconsistent/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /inconsistent/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -397,7 +397,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -461,9 +461,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter chunk name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /inconsistent/'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /inconsistent/'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix.md index 7aa36513fbe1..eaa90e1a8655 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-informix.md @@ -44,7 +44,7 @@ To compile DBD Informix, you need an access to an Informix Database, run: # cd DBD-Informix-2013.0521 # export INFORMIXDIR=/home/informix/sdkclient # export LD\_LIBRARY\_PATH=$ORACLE\_HOME/lib - # export PATH=${PATH}:/home/informix/sdkclient/bin + # export PATH=$\{PATH\}:/home/informix/sdkclient/bin # export LD\_LIBRARY\_PATH=/home/informix/sdkclient/lib/esql/:/home/informix/sdkclient/lib/ # export DBD\_INFORMIX\_USERNAME=root # export DBD\_INFORMIX\_PASSWORD=xxxx # export DBD\_INFORMIX\_DATABASE=xxxx diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mongodb.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mongodb.md index 947c78262cf7..6d4e54cecf0e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mongodb.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mongodb.md @@ -357,12 +357,12 @@ yum install centreon-plugin-Applications-Databases-Mongodb | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority} | %{state} !~ /PRIMARY\|SECONDARY/ | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /up/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority} | %{health} !~ /up/ | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\} | %\{state\} !~ /PRIMARY\|SECONDARY/ | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /up/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\} | %\{health\} !~ /up/ | | | WARNINGREPLICATIONLAG | Thresholds | | | | CRITICALREPLICATIONLAG | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{sync\_host} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{sync\_host} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{sync_host\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{sync_host\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -452,7 +452,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -555,10 +555,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{sync\_host}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{sync\_host}. | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{state} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority}. | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /up/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{sync_host\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{sync_host\}. | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\}. | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /up/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\}. | | --warning-* --critical-* | Thresholds. Can be: 'members-primary', 'members-secondary', 'members-arbiter', 'replication-lag'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mssql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mssql.md index 5cccd8584b03..6a2eb90da200 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mssql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mssql.md @@ -419,8 +419,8 @@ yum install centreon-plugin-Applications-Databases-Mssql | CRITICALJOBSSUCCESS | Thresholds | | | | WARNINGJOBSTOTAL | Thresholds | | | | CRITICALJOBSTOTAL | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{duration} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{duration} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -461,8 +461,8 @@ yum install centreon-plugin-Applications-Databases-Mssql |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -579,7 +579,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -691,8 +691,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | Filter job. | | --lookback | Check job history in minutes. | | --add-duration-perfdata | Display job duration time. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{duration} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{duration} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-total', 'jobs-failed', 'jobs-success', 'jobs-canceled', 'jobs-running', 'jobs-retry'. | @@ -734,9 +734,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mysql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mysql.md index 29367b249ac6..1aafc0ee0242 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mysql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-mysql.md @@ -332,8 +332,8 @@ yum install centreon-plugin-Applications-Databases-Mysql | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|:-----------:| | FILTERTYPE | Filter backups by type (regexp can be used) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR"'). You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | %{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR"'). You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | %\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | | | | WARNINGTIMELASTEXECUTION | Thresholds | | | | CRITICALTIMELASTEXECUTION | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -410,13 +410,13 @@ yum install centreon-plugin-Applications-Databases-Mysql | PEERPORT | | 3306 | | | PEERUSERNAME | | USERNAME | | | PEERPASSWORD | | PASSWORD | | -| UNKNOWNREPLICATIONSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{replication\_status} =~ /configurationIssue/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /configurationIssue/i | | +| UNKNOWNREPLICATIONSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{replication_status\} =~ /configurationIssue/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /configurationIssue/i | | | PEERHOST | | | | -| UNKNOWNCONNECTIONSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{error\_message}, %{display} | | | -| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "ok"'). You can use the following variables: %{status}, %{error\_message}, %{display} | %{status} ne "ok" | | -| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{error\_message}, %{display} | | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{replication\_status} =~ /inProgress/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /inProgress/i | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{replication\_status} =~ /connectIssueToMaster/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /connectIssueToMaster/i | | +| UNKNOWNCONNECTIONSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | | | +| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "ok"'). You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | %\{status\} ne "ok" | | +| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{replication_status\} =~ /inProgress/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /inProgress/i | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{replication_status\} =~ /connectIssueToMaster/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /connectIssueToMaster/i | | | WARNINGSLAVELATENCY | Thresholds | | | | CRITICALSLAVELATENCY | Thresholds | | | | CRITICALSLAVESRUNNING | Thresholds | 1:1 | | @@ -450,8 +450,8 @@ yum install centreon-plugin-Applications-Databases-Mysql | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{expire} ne "never" and %{expire\_time} == 0'). You can use the following variables: %{user}, %{expire}, %{expire\_time} | %{expire} ne "never" and %{expire\_time} == 0 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{user}, %{expire}, %{expire\_time} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{expire\} ne "never" and %\{expire_time\} == 0'). You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | %\{expire\} ne "never" and %\{expire_time\} == 0 | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -498,8 +498,8 @@ yum install centreon-plugin-Applications-Databases-Mysql |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -607,7 +607,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -645,9 +645,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-type | Filter backups by type (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR"'). You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR"'). You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'time-last-execution'. | @@ -712,12 +712,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-connection-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{error\_message}, %{display} | -| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{error\_message}, %{display} | -| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "ok"'). You can use the following variables: %{status}, %{error\_message}, %{display} | -| --unknown-replication-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{replication\_status} =~ /configurationIssue/i'). You can use the following variables: %{replication\_status}, %{display} | -| --warning-replication-status | Define the conditions to match for the status to be WARNING (Default: '%{replication\_status} =~ /inProgress/i'). You can use the following variables: %{replication\_status}, %{display} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (Default: '%{replication\_status} =~ /connectIssueToMaster/i'). You can use the following variables: %{replication\_status}, %{display} | +| --unknown-connection-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "ok"'). You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --unknown-replication-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{replication_status\} =~ /configurationIssue/i'). You can use the following variables: %\{replication_status\}, %\{display\} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING (Default: '%\{replication_status\} =~ /inProgress/i'). You can use the following variables: %\{replication_status\}, %\{display\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{replication_status\} =~ /connectIssueToMaster/i'). You can use the following variables: %\{replication_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'slaves-running', 'slave-latency' (s). | @@ -754,8 +754,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{user}, %{expire}, %{expire\_time} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{expire} ne "never" and %{expire\_time} == 0'). You can use the following variables: %{user}, %{expire}, %{expire\_time} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{expire\} ne "never" and %\{expire_time\} == 0'). You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | @@ -840,9 +840,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-oracle.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-oracle.md index 8d6889eaf717..3bba7ad63ecc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-oracle.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-oracle.md @@ -674,10 +674,10 @@ yum install centreon-plugin-Applications-Databases-Oracle | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------|:-----------:| -| WARNINGONLINESTATUS | Set warning threshold for online status (Default: '%{online\_status} =~ /sysoff/i'). You can use the following variables: %{display}, %{online\_status} | %{online\_status} =~ /sysoff/i | | -| CRITICALONLINESTATUS | Set critical threshold for online status (Default: '%{online\_status} =~ /offline\|recover/i'). You can use the following variables: %{display}, %{online\_status} | %{online\_status} =~ /offline\|recover/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %{display}, %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline\|invalid/i'). You can use the following variables: %{display}, %{status} | | | +| WARNINGONLINESTATUS | Set warning threshold for online status (Default: '%\{online_status\} =~ /sysoff/i'). You can use the following variables: %\{display\}, %\{online_status\} | %\{online_status\} =~ /sysoff/i | | +| CRITICALONLINESTATUS | Set critical threshold for online status (Default: '%\{online_status\} =~ /offline\|recover/i'). You can use the following variables: %\{display\}, %\{online_status\} | %\{online_status\} =~ /offline\|recover/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %\{display\}, %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline\|invalid/i'). You can use the following variables: %\{display\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -767,8 +767,8 @@ yum install centreon-plugin-Applications-Databases-Oracle | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -874,8 +874,8 @@ yum install centreon-plugin-Applications-Databases-Oracle |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -1015,7 +1015,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1056,11 +1056,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-usage | Critical threshold. | | --warning-usage-failure | Warning threshold. | | --critical-usage-failure | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | -| --warning-offline-disks | Set warning threshold for offline disks (Default: '(%{offline\_disks} \> 0 && %{type} eq "extern") \|\| (%{offline\_disks} \> 1 && %{type} eq "high")'). You can use the following variables: %{offline\_disks}, %{type}, %{display} | -| --critical-offline-disks | Set critical threshold for offline disks (Default: '%{offline\_disks} \> 0 && %{type} =~ /^normal\|high$/'). You can use the following variables: %{offline\_disks}, %{type}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | +| --warning-offline-disks | Set warning threshold for offline disks (Default: '(%\{offline_disks\} \> 0 && %\{type\} eq "extern") \|\| (%\{offline_disks\} \> 1 && %\{type\} eq "high")'). You can use the following variables: %\{offline_disks\}, %\{type\}, %\{display\} | +| --critical-offline-disks | Set critical threshold for offline disks (Default: '%\{offline_disks\} \> 0 && %\{type\} =~ /^normal\|high$/'). You can use the following variables: %\{offline_disks\}, %\{type\}, %\{display\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | | --filter-name | Filter by name (regexp can be used). | @@ -1109,10 +1109,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). | | --filter-tablespace | Filter tablespace name (can be a regexp). | | --filter-data-file | Filter data file name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %{display}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline\|invalid/i'). You can use the following variables: %{display}, %{status} | -| --warning-online-status | Set warning threshold for online status (Default: '%{online\_status} =~ /sysoff/i'). You can use the following variables: %{display}, %{online\_status} | -| --critical-online-status | Set critical threshold for online status (Default: '%{online\_status} =~ /offline\|recover/i'). You can use the following variables: %{display}, %{online\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %\{display\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline\|invalid/i'). You can use the following variables: %\{display\}, %\{status\} | +| --warning-online-status | Set warning threshold for online status (Default: '%\{online_status\} =~ /sysoff/i'). You can use the following variables: %\{display\}, %\{online_status\} | +| --critical-online-status | Set critical threshold for online status (Default: '%\{online_status\} =~ /offline\|recover/i'). You can use the following variables: %\{display\}, %\{online_status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-traffic'. | @@ -1233,8 +1233,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | --timezone | Timezone of oracle server (If not set, we use current server execution timezone). | | --memory | Only check new queries. | @@ -1344,9 +1344,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-postgresql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-postgresql.md index 005b89435e22..b24bd6ae1a48 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-postgresql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-postgresql.md @@ -524,7 +524,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-redis.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-redis.md index a41ac8d3e36f..74fffdc629e6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-redis.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-redis.md @@ -336,8 +336,8 @@ yum install centreon-plugin-Applications-Databases-Redis | CRITICALLASTSAVEDURATION | Critical threshold | | | | WARNINGSAVESIZE | Warning threshold | | | | CRITICALSAVESIZE | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{progress\_status} =~ /in progress/i'). You can use the following variables: %{progress\_status}, %{status} | %{sync\_status} =~ /in progress/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /fail/i'). You can use the following variables: %{progress\_status}, %{status} | %{link\_status} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{progress_status\} =~ /in progress/i'). You can use the following variables: %\{progress_status\}, %\{status\} | %\{sync_status\} =~ /in progress/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /fail/i'). You can use the following variables: %\{progress_status\}, %\{status\} | %\{link_status\} =~ /down/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -357,8 +357,8 @@ yum install centreon-plugin-Applications-Databases-Redis | CRITICALSLAVEREADONLY | Critical threshold | | | | WARNINGSLAVEREPLOFFSET | | | | | CRITICALSLAVEREPLOFFSET | | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{sync\_status} =~ /in progress/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | %{sync\_status} =~ /in progress/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /down/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | %{link\_status} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{sync_status\} =~ /in progress/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | %\{sync_status\} =~ /in progress/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /down/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | %\{link_status\} =~ /down/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -472,7 +472,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -659,8 +659,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{progress\_status} =~ /in progress/i'). You can use the following variables: %{progress\_status}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /fail/i'). You can use the following variables: %{progress\_status}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{progress_status\} =~ /in progress/i'). You can use the following variables: %\{progress_status\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /fail/i'). You can use the following variables: %\{progress_status\}, %\{status\} | | --warning-* | Warning threshold. Can be: 'changes', 'last-save', 'save-size', 'last-save-duration', 'current-save-duration'. | | --critical-* | Critical threshold. Can be: 'changes', 'last-save', 'save-size', 'last-save-duration', 'current-save-duration'. | @@ -669,8 +669,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{sync\_status} =~ /in progress/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /down/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{sync_status\} =~ /in progress/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /down/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | | --warning-* | Warning threshold. Can be: 'connected-slaves', 'master-repl-offset', 'master-last-io', 'slave-priority', 'slave-read-only'. | | --critical-* | Critical threshold. Can be: 'connected-slaves', 'master-repl-offset', 'master-last-io', 'slave-priority', 'slave-read-only'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-sap-hana.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-sap-hana.md index 48e7d24e7ac2..3db77049e7ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-sap-hana.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-sap-hana.md @@ -439,7 +439,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md index cf52c746214d..6168ee58559c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md @@ -375,7 +375,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-restapi.md index e9ad2f9dbbd3..36b536915b3c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-restapi.md @@ -219,8 +219,8 @@ yum install centreon-plugin-Applications-Docker-Restapi | CONTAINERID | Exact container ID | | | | CONTAINERNAME | Exact container name (if multiple names: names separated by ':') | | | | FILTERNAME | Filter by container name (can be a regexp) | | | -| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{state}, %{health} | | | -| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{state}, %{health} | | | +| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{state\}, %\{health\} | | | +| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{state\}, %\{health\} | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGMEMORY | Warning threshold | | | @@ -246,8 +246,8 @@ yum install centreon-plugin-Applications-Docker-Restapi | CRITICALCONTAINERSRUNNING | Critical threshold | | | | WARNINGCONTAINERSSTOPPED | Warning threshold | | | | CRITICALCONTAINERSSTOPPED | Critical threshold | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/'). You can use the following variables: %{display}, %{status}, %{manager\_status} | %{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/ | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %{display}, %{status}, %{manager\_status} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/'). You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\} | %\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/ | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -270,7 +270,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --hostname='10.0.0.1' \ --port='' \ --warning-node-status='' \ - --critical-node-status='%{status} !~ /ready/ || %{manager_status} !~ /reachable|-/' \ + --critical-node-status='%\{status\} !~ /ready/ || %\{manager_status\} !~ /reachable|-/' \ --verbose ``` @@ -331,7 +331,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -403,8 +403,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --no-stats | Don't get container statistics. | | --filter-name | Filter by container name (can be a regexp). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^container-status$' | -| --warning-container-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{state}, %{health}. | -| --critical-container-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{state}, %{health}. | +| --warning-container-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{state\}, %\{health\}. | +| --critical-container-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{state\}, %\{health\}. | | --warning-* --critical-* | Thresholds. Can be: 'read-iops', 'write-iops', 'traffic-in', 'traffic-out', 'cpu' (%), 'memory' (%). | @@ -412,8 +412,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-node-status | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %{display}, %{status}, %{manager\_status}. | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/'). You can use the following variables: %{display}, %{status}, %{manager\_status}. | +| --warning-node-status | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\}. | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/'). You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\}. | | --warning-* | Warning threshold. Can be: 'containers-running', 'containers-paused', 'containers-stopped'. | | --critical-* | Critical threshold. Can be: 'containers-running', 'containers-paused', 'containers-stopped'., | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-ssh.md index 3a8228f0912d..e6982eca33eb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-docker-ssh.md @@ -199,8 +199,8 @@ yum install centreon-plugin-Applications-Docker-Ssh |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | FILTERID | Filter by container ID (can be a regexp) | | | | FILTERNAME | Filter by container name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -304,7 +304,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -353,8 +353,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by container name (can be a regexp). | | --filter-id | Filter by container ID (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{name} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{name\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md index e7a16aab879d..159ac97a4dc1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md @@ -280,7 +280,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md index 1f8cac4fa5ae..bf7358054e54 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md @@ -258,13 +258,13 @@ yum install centreon-plugin-Applications-Eclipse-Mosquitto-MQTT | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| FORMATOK | Threshold | value: %{value} | | -| FORMATUNKNOWN | Threshold | value: %{value} | | +| FORMATOK | Threshold | value: %\{value\} | | +| FORMATUNKNOWN | Threshold | value: %\{value\} | | | TOPIC | Topic value to check | | X | | FORMATCUSTOM | Apply a custom change on the value | | | | UNKNOWNREGEXP | | | | -| FORMATWARNING | Threshold | value: %{value} | | -| FORMATCRITICAL | Threshold | value: %{value} | | +| FORMATWARNING | Threshold | value: %\{value\} | | +| FORMATCRITICAL | Threshold | value: %\{value\} | | | WARNINGREGEXP | Return Warning if the topic value match the regexp | | | | CRITICALREGEXP | Return Critical if the topic value match the regexp | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -366,7 +366,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp.Example: adding --filter-perfdata='avg' will remove all metrics that do not contain'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables:label, value, unit, warning, critical, min, max.Variables must be written either %{variable} or %(variable).Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' willremove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables:label, value, unit, warning, critical, min, max.Variables must be written either %\{variable\} or %(variable).Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' willremove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The newmetric will be named identically with a '\_max' suffix).Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata.Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\]Common examples:=over 4Convert storage free perfdata into used: --change-perfdata='free,used,invert()'Convert storage free perfdata into used: --change-perfdata='used,free,invert()'Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)'Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps'Change traffic values in percent: --change-perfdata='traffic\_in,,percent()'=back | | --change-perfdata | Change or extend perfdata.Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\]Common examples:=over 4Convert storage free perfdata into used: --change-perfdata='free,used,invert()'Convert storage free perfdata into used: --change-perfdata='used,free,invert()'Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)'Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps'Change traffic values in percent: --change-perfdata='traffic\_in,,percent()'=back | @@ -459,7 +459,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --warning-regexp | Return Warning if the topic value match the regexp. | | --critical-regexp | Return Critical if the topic value match the regexp. | | --regexp-insensitive | Allows to use case-insensitive regexp. | -| --format-* | Output format according to the threshold.Can be:'ok' (default: 'value: %{value}'),'warning' (default: 'value: %{value}'),'critical' (default: 'value: %{value}'),'unknown' (default: 'value: %{value}'). | +| --format-* | Output format according to the threshold.Can be:'ok' (default: 'value: %\{value\}'),'warning' (default: 'value: %\{value\}'),'critical' (default: 'value: %\{value\}'),'unknown' (default: 'value: %\{value\}'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-google-workspace-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-google-workspace-api.md index 2e81356d55c4..70e084c8977d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-google-workspace-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-google-workspace-api.md @@ -122,8 +122,8 @@ depuis un collecteur Centreon en vous connectant avec l'utilisateur *centreon-en --port='443' \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-name='mail|drive|meet' \ - --warning-status='%{status} eq "disruption"' \ - --critical-status='%{status} eq "outage"' \ + --warning-status='%\{status\} eq "disruption"' \ + --critical-status='%\{status\} eq "outage"' \ --verbose ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-gorgone-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-gorgone-restapi.md index 554e66f519bc..7861fe94a9a4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-gorgone-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-gorgone-restapi.md @@ -291,7 +291,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-grafana-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-grafana-api.md index 6691b15e50da..b43a845bf8d2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-grafana-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-grafana-api.md @@ -160,8 +160,8 @@ yum install centreon-plugin-Applications-Grafana-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "ok"'). You can use the following variables: %{state}, %{version} | %{state} ne "ok" | | -| WARNING | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{version} | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "ok"'). You can use the following variables: %\{state\}, %\{version\} | %\{state\} ne "ok" | | +| WARNING | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{version\} | | | @@ -186,7 +186,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --username='' \ --password='' \ --warning-status='' \ - --critical-status='%{state} ne "ok"' + --critical-status='%\{state\} ne "ok"' ``` La commande devrait retourner un message de sortie similaire à : @@ -245,7 +245,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -277,8 +277,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --http-backend | Perl library to use for HTTP transactions. Possible values are: lwp (default) and curl. | | --ssl-opt | Set SSL Options (--ssl-opt="SSL\_version =\> TLSv1" --ssl-opt="SSL\_verify\_mode =\> SSL\_VERIFY\_NONE"). | | --curl-opt | Set CURL Options (--curl-opt="CURLOPT\_SSL\_VERIFYPEER =\> 0" --curl-opt="CURLOPT\_SSLVERSION =\> CURL\_SSLVERSION\_TLSv1\_1" ). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{version} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "ok"'). You can use the following variables: %{state}, %{version} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{version\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "ok"'). You can use the following variables: %\{state\}, %\{version\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-haproxy-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-haproxy-snmp.md index d648924f89cc..c98a11fa7c8d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-haproxy-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-haproxy-snmp.md @@ -120,7 +120,7 @@ yum install centreon-pack-applications-haproxy-snmp --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /OPEN/i' \ + --critical-status='%\{status\} !~ /OPEN/i' \ --warning-total-sessions='' \ --critical-total-sessions='' \ --warning-current-sessions='' \ diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md index 30f3df97cf0a..9868f7dc3eb1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md @@ -196,9 +196,9 @@ yum install centreon-plugin-Applications-HashiCorp-Vault-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:---------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| CRITICALINITSTATUS | Set critical threshold for initialization status (default: '%{init} ne "initialized"') | %{init} ne "initialized" | | +| CRITICALINITSTATUS | Set critical threshold for initialization status (default: '%\{init\} ne "initialized"') | %\{init\} ne "initialized" | | | WARNINGINITSTATUS | Set warning threshold for initialization status (default: none) | | | -| CRITICALSEALSTATUS | Set critical threshold for seal status (default: '%{sealed} ne "unsealed"') | %{sealed} ne "unsealed" | | +| CRITICALSEALSTATUS | Set critical threshold for seal status (default: '%\{sealed\} ne "unsealed"') | %\{sealed\} ne "unsealed" | | | WARNINGSEALSTATUS | Set warning threshold for seal status (default: none) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -305,7 +305,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -363,9 +363,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:-------------------------------------------------------------------------------------------| | --warning-seal-status | Set warning threshold for seal status (default: none). | -| --critical-seal-status | Set critical threshold for seal status (default: '%{sealed} ne "unsealed"'). | +| --critical-seal-status | Set critical threshold for seal status (default: '%\{sealed\} ne "unsealed"'). | | --warning-init-status | Set warning threshold for initialization status (default: none). | -| --critical-init-status | Set critical threshold for initialization status (default: '%{init} ne "initialized"'). | +| --critical-init-status | Set critical threshold for initialization status (default: '%\{init\} ne "initialized"'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md index b276196f0579..6893a88a91f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md @@ -102,7 +102,7 @@ l'utilisateur **centreon-engine**: --filter-name='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /ok/i' \ + --critical-status='%\{status\} !~ /ok/i' \ --warning-temperature='30' \ --critical-temperature='50' \ --verbose \ diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md index 30e39fc84647..276d0b6c72d2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md @@ -191,8 +191,8 @@ yum install centreon-plugin-Applications-Infor-Ion-Grid-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| | FILTERNAME | Filter by application name (regexp can be used). Example: --filter-name='^application1$' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{online} =~ /true/ && %{state} !~ /^(OK)/i'). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --critical-status='%{started} ne "true"' | %{online} =~ /true/ && %{state} !~ /^(OK)/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --warning-status='%{state} ne "OK"' | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i'). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --critical-status='%\{started\} ne "true"' | %\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --warning-status='%\{state\} ne "OK"' | | | | WARNINGTOTAL | Define the conditions to match for the total to be WARNING (default: ''). | | | | CRITICALTOTAL | Define the conditions to match for the total to be CRITICAL (default: ''). | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -214,8 +214,8 @@ yum install centreon-plugin-Applications-Infor-Ion-Grid-Restapi | CRITICALLOGWARNING | Set critical thresholds on log-warning | | | | WARNINGLOGERROR | Set warning thresholds on log-error | | | | CRITICALLOGERROR | Set critical thresholds on log-error | | | -| CRITICALSTATUS | Set critical threshold for status. Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type} | '%{state} !~ /online/' | | -| WARNINGSTATUS | Set warning threshold for status (Default: "%{state} !~ /online/"). Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status. Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\} | '%\{state\} !~ /online/' | | +| WARNINGSTATUS | Set warning threshold for status (Default: "%\{state\} !~ /online/"). Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\} | | | | WARNINGUPTIME | Set warning thresholds on uptime | | | | CRITICALUPTIME |Set critical thresholds on uptime | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -246,8 +246,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-type='' \ --filter-application-name='^SYSTEM$' \ --filter-host-name='^THEHOST$' \ - --warning-status='%{state} !~ /online/' \ - --critical-status=''%{state} !~ /online/'' \ + --warning-status='%\{state\} !~ /online/' \ + --critical-status=''%\{state\} !~ /online/'' \ --warning-log-error='' \ --critical-log-error='' \ --warning-log-warning='' \ @@ -317,7 +317,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -360,8 +360,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by application name (regexp can be used). Example: --filter-name='^application1$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --warning-status='%{state} ne "OK"' | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{online} =~ /true/ && %{state} !~ /^(OK)/i'). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --critical-status='%{started} ne "true"' | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --warning-status='%\{state\} ne "OK"' | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i'). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --critical-status='%\{started\} ne "true"' | | --warning-total | Define the conditions to match for the total to be WARNING (default: ''). | | --critical-total | Define the conditions to match for the total to be CRITICAL (default: ''). | @@ -374,8 +374,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter by node name. | | --filter-application-name | Filter by application name. | | --filter-host-name | Filter by host name. | -| --warning-status | Set warning threshold for status (Default: "%{state} !~ /online/"). Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type}. | -| --critical-status | Set critical threshold for status. Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type}. | +| --warning-status | Set warning threshold for status (Default: "%\{state\} !~ /online/"). Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\}. | +| --critical-status | Set critical threshold for status. Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'log-error', 'log-warning', 'uptime' (s), 'cpu-usage', 'heap-usage' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ipfabric-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ipfabric-api.md index 8c55a4a2b180..70465749020c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ipfabric-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-ipfabric-api.md @@ -191,8 +191,8 @@ yum install centreon-plugin-Applications-Ipfabric-Api | CRITICALPATHSSTATENONE | Thresholds | | | | WARNINGPATHSSTATEPART | Thresholds | | | | CRITICALPATHSSTATEPART | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%{expected\_state} ne %{state}'). Can use special variables like: %{state}, %{expected\_state} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%{state} eq 'all'" | %{expected\_state} ne %{state} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{state}, %{expected\_state} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%{state} eq 'all'" | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expected_state\} ne %\{state\}'). Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%\{state\} eq 'all'" | %\{expected_state\} ne %\{state\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%\{state\} eq 'all'" | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --http-backend=curl | | @@ -322,7 +322,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -358,8 +358,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-src-port | Filter paths by source port (regexp can be used). | | --filter-dst-ip | Filter paths by destionation ip (regexp can be used). | | --filter-dst-port | Filter paths by destionation port (regexp can be used). | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{state}, %{expected\_state} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%{state} eq 'all'" | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{expected\_state} ne %{state}'). Can use special variables like: %{state}, %{expected\_state} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%{state} eq 'all'" | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%\{state\} eq 'all'" | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expected_state\} ne %\{state\}'). Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%\{state\} eq 'all'" | | --warning-* --critical-* | Thresholds. Can be: 'paths-detected', 'paths-mismatch', 'paths-state-all', 'paths-state-part', 'paths-state-none', 'paths-state-error'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-jmeter.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-jmeter.md index bd32f72e9189..6b9cb5717511 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-jmeter.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-jmeter.md @@ -254,7 +254,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-keepalived-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-keepalived-snmp.md index 3549411b191c..4e82be7b47d7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-keepalived-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-keepalived-snmp.md @@ -178,8 +178,8 @@ yum install centreon-plugin-Applications-Keepalived-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{instanceState} ne %{instanceWantedState} or %{instanceState} ne %{instanceStateLast}'). You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{instanceState\} ne %\{instanceWantedState\} or %\{instanceState\} ne %\{instanceStateLast\}'). You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -260,7 +260,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -316,8 +316,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{instanceState} ne %{instanceWantedState} or %{instanceState} ne %{instanceStateLast}'). You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{instanceState\} ne %\{instanceWantedState\} or %\{instanceState\} ne %\{instanceStateLast\}'). You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md index ce4709c34acb..102e0a43baf5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md @@ -259,7 +259,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md index d0df837b53c3..b361c5ef6736 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md @@ -287,7 +287,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -333,9 +333,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --snmp-tls-trust-cert | A trusted CA certificate used to verify a remote host's certificate. If you use this option, you must also define --snmp-tls-their-hostname. | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='pending' | | --filter-subnet-address | Filter subnets by address (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'addresses-usage', 'addresses-usage-free', 'addresses-usage-prct', 'pending-offers'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md index e76134169f11..951cca4b2ba1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md @@ -141,8 +141,8 @@ depuis un collecteur Centreon en vous connectant avec l'utilisateur *centreon-en --port='80' \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-testcase='case_app1|case_app2' \ - --critical-testcase-state='%{state} eq "FAILED"' \ - --critical-transaction-state='%{state} eq "FAILED"' \ + --critical-testcase-state='%\{state\} eq "FAILED"' \ + --critical-transaction-state='%\{state\} eq "FAILED"' \ --warning-testcase-duration='40000' \ --critical-testcase-duration='60000' \ --critical-testcase-freshness='600' \ diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md index c37d801be519..d8dc8aa9e918 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md @@ -356,8 +356,8 @@ yum install centreon-plugin-Applications-Monitoring-Centreon-Central | CRITICALQUEUEDEVENTS | Thresholds | | | | WARNINGSPEEDEVENTS | Thresholds | | | | CRITICALSPEEDEVENTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | %{type} eq "output" and %{queue\_file\_enabled} =~ /true\|yes/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{type\} eq "output" and %\{queue_file_enabled\}=~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | %\{type\} eq "output" and %\{queue_file_enabled\}=~ /true\|yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | | | | WARNINGUNACKNOWLEDGEDEVENTS | Thresholds | | | | CRITICALUNACKNOWLEDGEDEVENTS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -606,7 +606,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -653,8 +653,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --broker-stats-file | Specify the centreon-broker json stats file (Required). Can be multiple. | | --filter-name | Filter endpoint name. | | --warning-* --critical-* | Thresholds. Can be: 'speed-events', 'queued-events', 'unacknowledged-events'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{type\} eq "output" and %\{queue_file_enabled\}=~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md index 5877492961cb..87a0acf55ca8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md @@ -304,7 +304,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md index 6bdc9ad79b3d..4127cbf6da2f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md @@ -404,7 +404,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md index c986beed6fb0..e01e860d2ae9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md @@ -77,11 +77,11 @@ With the `root` user, install the following package and its dependencies: Try to execute this command: - $ snmpwalk -v 1 -c .1.3.6.1.2.1.1.1 + $ snmpwalk -v 1 -c \ \ .1.3.6.1.2.1.1.1 You should get a response looking like the following: - SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 + SNMPv2-MIB::sysDescr.0 = STRING: Linux \ 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 ### SNMP Permissions diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md index 9bef49362046..f93db655433a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md @@ -238,8 +238,8 @@ yum install centreon-plugin-Applications-Monitoring-Centreon-Poller | CRITICALQUEUEDEVENTS | Thresholds | | | | WARNINGSPEEDEVENTS | Thresholds | | | | CRITICALSPEEDEVENTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | %{type} eq "output" and %{queue\_file\_enabled} =~ /true\|yes/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "output" and %\{queue_file_enabled\}=~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | %\{type\} eq "output" and %\{queue_file_enabled\}=~ /true\|yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | | | | WARNINGUNACKNOWLEDGEDEVENTS | Thresholds | | | | CRITICALUNACKNOWLEDGEDEVENTS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --ssh-username='centreon' | | @@ -319,7 +319,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-unacknowledged-events='' \ --critical-unacknowledged-events='' \ --warning-status='' \ - --critical-status='%{type} eq "output" and %{queue_file_enabled} =~ /true|yes/i' \ + --critical-status='%\{type\} eq "output" and %\{queue_file_enabled\} =~ /true|yes/i' \ --verbose \ --ssh-username='centreon' ``` @@ -403,7 +403,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale"Mbps",mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -450,8 +450,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --broker-stats-file | Specify the centreon-broker json stats file (required). Can be multiple. | | --filter-name | Filter endpoint name. | | --warning-* --critical-* | Thresholds. Can be: 'speed-events', 'queued-events', 'unacknowledged-events'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "output" and %\{queue_file_enabled\}=~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md index fa0ae6e2461c..d72c7fe6c856 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md @@ -450,7 +450,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale"Mbps",mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md index f19e85148f41..7f8b2347bf0b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md @@ -314,7 +314,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md index f7645823fdb2..0a2b85f7d9a8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md @@ -733,7 +733,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md index c0bd08ba0a0e..28e529d5b515 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md @@ -284,7 +284,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md index 43dac228feed..021d84fa130e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md @@ -385,7 +385,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md index d283058cf000..27096d761af0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md @@ -255,8 +255,8 @@ yum install centreon-plugin-Applications-Monitoring-Nodeexporter-Windows | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------|:-----------:| | SERVICENAME | Specify which service to monitor. Can be a regex. Default: all services are monitored | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{start\_mode} =~ /auto/ && %{status} !~ /^running$/'). You can use the following variables: %{status}, %{start\_mode} | %{start\_mode} =~ /auto/ && %{status} !~ /^running$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{start\_mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/'). You can use the following variables: %\{status\}, %\{start_mode\} | %\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{start_mode\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -382,7 +382,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -457,8 +457,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --service | Specify which service to monitor. Can be a regex. Default: all services are monitored. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{start\_mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{start\_mode} =~ /auto/ && %{status} !~ /^running$/'). You can use the following variables: %{status}, %{start\_mode} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{start_mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/'). You can use the following variables: %\{status\}, %\{start_mode\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md index a83618ca621e..beaa9c824a74 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md @@ -263,7 +263,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md index 3283232a0490..39f42da3aeca 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md @@ -183,8 +183,8 @@ yum install centreon-plugin-Applications-Monitoring-Scom-Restapi | CRITICALRESOLVED | Threshold | | | | WARNINGSCHEDULED | Threshold | | | | CRITICALSCHEDULED | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | %{severity} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | %{severity} =~ /critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -211,8 +211,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --port='80' \ --proto='http' \ --filter-host='' \ - --warning-status='%{severity} =~ /warning/i' \ - --critical-status='%{severity} =~ /critical/i' \ + --warning-status='%\{severity\} =~ /warning/i' \ + --critical-status='%\{severity\} =~ /critical/i' \ --warning-new='' \ --critical-new='' \ --warning-closed='' \ @@ -288,8 +288,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-host | Filter by host name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning/i') You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical/i'). You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning/i') You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical/i'). You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | | --warning-* --critical-* | Thresholds. Can be: 'new', 'closed', 'resolved', 'scheduled', 'awaiting-evidence', 'assigned-to-engineering', 'acknowledge'. | | --memory | Only check new alarms. | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | @@ -304,7 +304,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md index 8519b0f4b7ea..eca1486e12e8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md @@ -249,7 +249,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md index 0f7e880495b5..04cb5477eb52 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md @@ -211,16 +211,16 @@ yum install centreon-plugin-Applications-Monitoring-Splunk-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:---------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGFILEMONITORINPUTSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALFILEMONITORINPUTSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGINDEXPROCESSORSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALINDEXPROCESSORSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGRESOURCEUSAGESTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALRESOURCEUSAGESTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGSEARCHSCHEDULERSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALSEARCHSCHEDULERSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGWORKLOADMANAGEMENTSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALWORKLOADMANAGEMENTSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | +| WARNINGFILEMONITORINPUTSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALFILEMONITORINPUTSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGINDEXPROCESSORSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALINDEXPROCESSORSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGRESOURCEUSAGESTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALRESOURCEUSAGESTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGSEARCHSCHEDULERSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALSEARCHSCHEDULERSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGWORKLOADMANAGEMENTSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALWORKLOADMANAGEMENTSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | @@ -304,7 +304,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,8 +378,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Warning thresholds for features status. (default: '%{status} =~ /yellow/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | -| --critical-* | Critical thresholds for features status. (default: '%{status} =~ /red/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | +| --warning-* | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | +| --critical-* | Critical thresholds for features status. (default: '%\{status\} =~ /red/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md index ac8df4bd23df..d34b6c0f7c48 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md @@ -158,8 +158,8 @@ Une fois le Plugin installé, vous pouvez tester celui-ci directement en ligne d --api-username='myapiuser' \ --api-password='myapipassword' \ --filter-name='myapplication1' \ - --warning-status='%{status} =~ /STOPPED/' \ - --critical-status='%{status} =~ /FAILED/' \ + --warning-status='%\{status\} =~ /STOPPED/' \ + --critical-status='%\{status\} =~ /FAILED/' \ --verbose diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-netbackup-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-netbackup-ssh.md index 185210a0aa6e..19f0c2c2cec6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-netbackup-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-netbackup-ssh.md @@ -196,7 +196,7 @@ Une fois le Plugin installé, vous pouvez tester celui-ci directement en ligne d --ssh-username=centreon \ --ssh-password='centreon-password' \ --ssh-backend=sshcli \ - --critical-status='%{status} !~ /up/i' \ + --critical-status='%\{status\} !~ /up/i' \ --verbose ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openldap-ldap.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openldap-ldap.md index 349c29450a57..d311969da6e6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openldap-ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openldap-ldap.md @@ -281,7 +281,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openvpn-omi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openvpn-omi.md index 269266acc79d..454f57d68573 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openvpn-omi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openvpn-omi.md @@ -257,7 +257,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md index 282aa0804d27..4ccf71167bba 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md @@ -16,7 +16,7 @@ yum install centreon-plugin-Applications-Openweathermap-Restapi ### API token A token is mandatory to access the API. More information can be found on the -official OpenWeatherMap website : . +official OpenWeatherMap website : \. ## Centreon Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md index faf959f82b80..01d057520393 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md @@ -230,8 +230,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCEEDED | Thresholds | | | | CRITICALJOBSSUCCEEDED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /running/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /running/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -272,8 +272,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | CRITICALSERVERSRUNNING | Thresholds | | | | WARNINGSERVERSSTOPPED | Thresholds | | | | CRITICALSERVERSSTOPPED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -282,8 +282,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter virtual machines by name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{name\} | | | | WARNINGVMRUNNING | Thresholds | | | | CRITICALVMRUNNING | Thresholds | | | | WARNINGVMSTOPPED | Thresholds | | | @@ -387,7 +387,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -440,9 +440,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-succeeded', 'jobs-failed'. | @@ -461,9 +461,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | | --filter-name | Filter servers by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'servers-running', 'servers-stopped', 'memory-usage' (B), 'memory-usage-free' (B), 'memory-usage-prct' (%). | @@ -473,9 +473,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter virtual machines by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{running\_status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{running_status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'vm-running', 'vm-stopped'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md index ed3d73d056ce..6b91b33ae86f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md @@ -223,26 +223,26 @@ yum install centreon-plugin-Applications-Pacemaker-Ssh | CRITICALCLONERESOURCEACTIONSFAILED | Thresholds | | | | WARNINGCLONERESOURCEMIGRATIONFAILED | Thresholds | | | | CRITICALCLONERESOURCEMIGRATIONFAILED | Thresholds | | | -| CRITICALCLONERESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | %{status} =~ /failed/i | | -| WARNINGCLONERESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | | | +| CRITICALCLONERESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | %\{status\} =~ /failed/i | | +| WARNINGCLONERESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | | | | CRITICALCLUSTERACTIONSFAILED | Thresholds | 0 | | | WARNINGCLUSTERACTIONSFAILED | Thresholds | | | -| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /failed/i'). You can use the following variables: %{connection\_status}, %{connection\_error} | %{connection\_status} =~ /failed/i | | -| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_status}, %{connection\_error} | | | +| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /failed/i'). You can use the following variables: %\{connection_status\}, %\{connection_error\} | %\{connection_status\} =~ /failed/i | | +| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_status\}, %\{connection_error\} | | | | CRITICALNODESOFFLINE | Thresholds | 0 | | | WARNINGNODESOFFLINE | Thresholds | | | | WARNINGNODESONLINE | Thresholds | | | | CRITICALNODESONLINE | Thresholds | | | | WARNINGNODESSTANDBY | Thresholds | | | | CRITICALNODESSTANDBY | Thresholds | | | -| CRITICALQUORUMSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{quorum\_status} =~ /noQuorum/i'). You can use the following variables: %{quorum\_status} | %{quorum\_status} =~ /noQuorum/i | | -| WARNINGQUORUMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{quorum\_status} | | | +| CRITICALQUORUMSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{quorum_status\} =~ /noQuorum/i'). You can use the following variables: %\{quorum_status\} | %\{quorum_status\} =~ /noQuorum/i | | +| WARNINGQUORUMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{quorum_status\} | | | | WARNINGRESOURCEACTIONSFAILED | Thresholds | | | | CRITICALRESOURCEACTIONSFAILED | Thresholds | | | | CRITICALRESOURCEMIGRATIONFAILED | Thresholds | 0 | | | WARNINGRESOURCEMIGRATIONFAILED | Thresholds | | | -| CRITICALRESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /stopped\|failed/i'). You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | %{status} =~ /stopped\|failed/i | | -| WARNINGRESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | | | +| CRITICALRESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /stopped\|failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | %\{status\} =~ /stopped\|failed/i | | +| WARNINGRESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -292,23 +292,23 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-nodes-standby='' \ --critical-nodes-standby='' \ --warning-clone-resource-status='' \ - --critical-clone-resource-status='%{status} =~ /failed/i' \ + --critical-clone-resource-status='%\{status\} =~ /failed/i' \ --warning-clone-resource-actions-failed='' \ --critical-clone-resource-actions-failed='' \ --warning-clone-resource-migration-failed='' \ --critical-clone-resource-migration-failed='' \ --warning-connection-status='' \ - --critical-connection-status='%{connection_status} =~ /failed/i' \ + --critical-connection-status='%\{connection_status\} =~ /failed/i' \ --warning-cluster-actions-failed='' \ --critical-cluster-actions-failed='0' \ --warning-resource-status='' \ - --critical-resource-status='%{status} =~ /stopped|failed/i' \ + --critical-resource-status='%\{status\} =~ /stopped|failed/i' \ --warning-resource-actions-failed='' \ --critical-resource-actions-failed='' \ --warning-resource-migration-failed='' \ --critical-resource-migration-failed='0' \ --warning-quorum-status='' \ - --critical-quorum-status='%{quorum_status} =~ /noQuorum/i' \ + --critical-quorum-status='%\{quorum_status\} =~ /noQuorum/i' \ --verbose ``` @@ -367,7 +367,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -415,14 +415,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-resource-name | Filter resource (also clone resource) by name (can be a regexp). | -| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_status}, %{connection\_error} | -| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /failed/i'). You can use the following variables: %{connection\_status}, %{connection\_error} | -| --warning-quorum-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{quorum\_status} | -| --critical-quorum-status | Define the conditions to match for the status to be CRITICAL (default: '%{quorum\_status} =~ /noQuorum/i'). You can use the following variables: %{quorum\_status} | -| --warning-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | -| --critical-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /stopped\|failed/i'). You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | -| --warning-clone-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | -| --critical-clone-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | +| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_status\}, %\{connection_error\} | +| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /failed/i'). You can use the following variables: %\{connection_status\}, %\{connection_error\} | +| --warning-quorum-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{quorum_status\} | +| --critical-quorum-status | Define the conditions to match for the status to be CRITICAL (default: '%\{quorum_status\} =~ /noQuorum/i'). You can use the following variables: %\{quorum_status\} | +| --warning-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | +| --critical-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /stopped\|failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | +| --warning-clone-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | +| --critical-clone-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | | --ignore-failed-actions | Failed actions errors (that match) are skipped. | | --resources | If resources not started on the node specified, send a warning message: (format: \:\,\:\,...) | | --warning-* --critical-* | Thresholds. Can be: 'cluster-actions-failed', 'clone-resource-actions-failed', 'clone-resource-migration-failed', 'nodes-online', 'nodes-offline', 'nodes-standby', 'resource-actions-failed', 'resource-migration-failed'. | @@ -433,7 +433,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* | Can be ('group','node') Define the conditions to match for the status to be WARNING. | -| --critical-* | Can be ('group','node') Define the conditions to match for the status to be CRITICAL. (default: --critical-node '%{state} !~ /up\|clean/' --critical-group '%{state} !~ /started\|starting/') | +| --critical-* | Can be ('group','node') Define the conditions to match for the status to be CRITICAL. (default: --critical-node '%\{state\} !~ /up\|clean/' --critical-group '%\{state\} !~ /started\|starting/') | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md index b49dec0cfda0..645825f57337 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md @@ -223,8 +223,8 @@ yum install centreon-plugin-Applications-Pfsense-Fauxapi | CRITICALPACKETSLOSS | Thresholds | | | | WARNINGPACKETSSTDDEV | Thresholds | | | | CRITICALPACKETSSTDDEV | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /none/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /none/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /none/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /none/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -336,7 +336,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -388,9 +388,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter gateway name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /none/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /none/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'packets-delay' (ms), 'packets-loss' (%), 'packets-stddev' (ms). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md index 3000e9a058c0..b64c2f7dce20 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md @@ -183,8 +183,8 @@ yum install centreon-plugin-Applications-Protocol-Bgp-Snmp | FILTERAS | Filter based on AS number (regexp allowed) | .* | | | FILTERPEER | Filter based on IP of peers (regexp allowed) | .* | | | CRITCALUPDATES | Critical threshold on last update (seconds) | | | -| CRITICALSTATUS | Specify admin and peer state that trigger a critical. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '%{adminstate} =~ /start/ && %{peerstate} !~ /established/') | %{adminstate} !~ /stop/ and %{peerstate} !~ /established/ | | -| WARNINGSTATUS | Specify admin and peer state that trigger a warning. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '') | | | +| CRITICALSTATUS | Specify admin and peer state that trigger a critical. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '%\{adminstate\} =~ /start/ && %\{peerstate\} !~ /established/') | %\{adminstate\} !~ /stop/ and %\{peerstate\} !~ /established/ | | +| WARNINGSTATUS | Specify admin and peer state that trigger a warning. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '') | | | | WARNINGUPDATES | Warning threshold on last update (seconds) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --filter-perfdata '^(?!(seconds))' | | @@ -213,7 +213,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-updates '' \ --critical-updates '' \ --warning-status '' \ - --critical-status '%{adminstate} !~ /stop/ and %{peerstate} !~ /established/' \ + --critical-status '%\{adminstate\} !~ /stop/ and %\{peerstate\} !~ /established/' \ --verbose \ --filter-perfdata '^(?!(seconds))' ``` @@ -271,7 +271,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -319,8 +319,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-peer | Filter based on IP of peers (regexp allowed) | | --warning-updates | Warning threshold on last update (seconds) | | --critical-updates | Critical threshold on last update (seconds) | -| --warning-status | Specify admin and peer state that trigger a warning. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '') | -| --critical-status | Specify admin and peer state that trigger a critical. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '%{adminstate} =~ /start/ && %{peerstate} !~ /established/') | +| --warning-status | Specify admin and peer state that trigger a warning. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '') | +| --critical-status | Specify admin and peer state that trigger a critical. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '%\{adminstate\} =~ /start/ && %\{peerstate\} !~ /established/') | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-cifs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-cifs.md index 4059b1edf991..3aae661c37a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-cifs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-cifs.md @@ -208,8 +208,8 @@ yum install centreon-plugin-Applications-Protocol-Cifs | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| | DIRECTORY | Set the share directory. | | X | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | %{message} !~ /authentication succeeded/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | %\{message\} !~ /authentication succeeded/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGTIME | Warning threshold in seconds. | | | | CRITICALTIME | Critical threshold in seconds. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -257,10 +257,10 @@ yum install centreon-plugin-Applications-Protocol-Cifs | SCENARIO | Scenario used. Can be a file or json content. | | X | | WARNINGERRORS | Thresholds. | | | | CRITICALERRORS | Thresholds. | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}. | %{status} ne "success" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | | | -| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | -| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}. | %\{status\} ne "success" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | | | +| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | +| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGSTEPTIME | Thresholds. | | | | CRITICALSTEPTIME | Thresholds. | | | | WARNINGTOTALSTEPS | Thresholds. | | | @@ -292,7 +292,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --timeout='' \ --scenario='' \ --warning-status='' \ - --critical-status='%{status} ne "success"' \ + --critical-status='%\{status\} ne "success"' \ --warning-total-time='' \ --critical-total-time='' \ --warning-total-steps='' \ @@ -364,7 +364,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -400,8 +400,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --directory | Set the share directory. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{message} !~ /authentication succeeded/i' You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{message\} !~ /authentication succeeded/i' You can use the following variables: %\{status\}, %\{message\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -444,10 +444,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------| | --scenario | Scenario used (required). Can be a file or json content. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} ne "success"') You can use the following variables: %{status} | -| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} ne "success"') You can use the following variables: %\{status\} | +| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\} | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'errors', 'step-time'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-dns.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-dns.md index 7f1deeeef66e..a4fd3e316c5e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-dns.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-dns.md @@ -248,7 +248,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ftp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ftp.md index 3cadadc0eadb..daf7dd59c9b9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ftp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ftp.md @@ -301,7 +301,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-http.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-http.md index 7f3de1922fdc..4187c13b1729 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-http.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-http.md @@ -222,7 +222,7 @@ yum install centreon-plugin-Applications-Protocol-Http | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| EXPECTEDCONTENT | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%{content} !~ /mypattern/mi'. It is recommended to use --critical-content directly | | | +| EXPECTEDCONTENT | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%\{content\} !~ /mypattern/mi'. It is recommended to use --critical-content directly | | | | URLPATH | Define the path of the web page to get (default: '/') | / | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -234,11 +234,11 @@ yum install centreon-plugin-Applications-Protocol-Http | URLPATH | Set path to get Webpage (default: '/') | / | | | HEADER | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx' | Content-Type: text/xml;charset=UTF-8 | | | THRESHOLDVALUE | Define the scope to which the numeric thresholds apply. Possible values for this option: 'value' to check numeric values, 'count' to check the number of values (default: count) | count | | -| FORMATOK | Customize the format of the output when the status is OK (default: '%{count} element(s) found'). You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | %{count} element(s) found | | +| FORMATOK | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found'). You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | %\{count\} element(s) found | | | DATAFILE | Set file with JSON request | | | | LOOKUP | What to lookup in JSON response (JSON XPath string) (can be multiple) See: http://goessner.net/articles/JsonPath/ | | | -| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | -| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | +| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | +| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | | WARNINGNUMERIC | Warning threshold (default: on total matching elements) | | | | CRITICALNUMERIC | Critical threshold (default: on total matching elements) | | | | WARNINGSTRING | Returns a WARNING status if the value matches the string | | | @@ -266,9 +266,9 @@ yum install centreon-plugin-Applications-Protocol-Http | DATAFILE | Set file with SOAP request (required) | | | | LOOKUP | What to lookup in XML response (XPath string) (can be multiple) FORMAT OPTIONS: | | | | THRESHOLDVALUE | Define the scope to which the numeric thresholds apply. Possible values for this option: 'value' to check numeric values, 'count' to check the number of values (default: count) | count | | -| FORMATOK | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | %{count} element(s) found | | -| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | -| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | +| FORMATOK | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | %\{count\} element(s) found | | +| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | +| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | | WARNINGNUMERIC | Warning threshold (default: on total matching elements) | | | | CRITICALNUMERIC | Critical threshold (default: on total matching elements) | | | | WARNINGSTRING | Returns a WARNING status if the value matches the string | | | @@ -355,7 +355,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -423,8 +423,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --post-param | Set POST params (multiple option. Example: --post-param='key=value') | | --cookies-file | Save cookies in a file (example: '/tmp/lwp\_cookies.dat') | | --extracted-pattern | Define a pattern to extract a number from the returned page (use --warning-extracted and --critical-extracted option). | -| --expected-string | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%{content} !~ /mypattern/mi'. It is recommended to use --critical-content directly. | -| --unknown-status | Warning threshold for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --expected-string | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%\{content\} !~ /mypattern/mi'. It is recommended to use --critical-content directly. | +| --unknown-status | Warning threshold for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code | | --critical-status | Critical threshold for http response code | | --warning-time | Warning threshold in seconds (Webpage response time) | @@ -433,9 +433,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-size | Critical threshold for content size | | --warning-extracted | Warning threshold for extracted value | | --critical-extracted | Critical threshold for extracted value | -| --unknown-content | Set warning conditions for content page (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | -| --warning-content | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | -| --critical-content | Set critical threshold for content page (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | +| --unknown-content | Set warning conditions for content page (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | +| --warning-content | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | +| --critical-content | Set critical threshold for content page (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | @@ -453,10 +453,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --lookup | What to lookup in JSON response (JSON XPath string) (can be multiple) See: http://goessner.net/articles/JsonPath/ | | --lookup-perfdatas-nagios | Take perfdatas from the JSON response (JSON XPath string) Chain must be formated in Nagios format. Ex : "rta=10.752ms;50.000;100.000;0; pl=0%;20;40;; rtmax=10.802ms;;;;" FORMAT OPTIONS: | | --format-lookup | Take the output message from the JSON response (JSON XPath string) Override all the format options but substitute are still applied. | -| --format-ok | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | -| --format-warning | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-unknown | Customize the format of the output when the status is UNKNOWN (default: '%{count} element(s) found') You can use the variables described in --format-ok | +| --format-ok | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | +| --format-warning | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-unknown | Customize the format of the output when the status is UNKNOWN (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | | --values-separator | Separator used for values in format option (default: ', ') THRESHOLD OPTIONS: | | --warning-numeric | Warning threshold (default: on total matching elements) | | --critical-numeric | Critical threshold (default: on total matching elements) | @@ -483,7 +483,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --cert-pkcs12 | Specify that the type of certificate is PKCS1. | | --get-param | Set GET params (multiple option. Example: --get-param='key=value'). | | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | @@ -520,7 +520,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | | --post-param | Set POST params (multiple option. Example: --post-param='key=value'). | | --cookies-file | Save cookies in a file (example: '/tmp/lwp\_cookies.dat'). | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | | --extra-stats | Add detailed time statistics (only with curl backend). | @@ -541,9 +541,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --service-soap | Service Soap Action (required) | | --data | Set file with SOAP request (required) | | --lookup | What to lookup in XML response (XPath string) (can be multiple) FORMAT OPTIONS: | -| --format-ok | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | -| --format-warning | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | +| --format-ok | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | +| --format-warning | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | | --values-separator | Separator used for values in format option (default: ', ') THRESHOLD OPTIONS: | | --warning-numeric | Warning threshold (default: on total matching elements) | | --critical-numeric | Critical threshold (default: on total matching elements) | @@ -568,7 +568,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --cert-pwd | Specify certificate's password. | | --cert-pkcs12 | Specify that the type of certificate is PKCS1. | | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ldap.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ldap.md index 7f6ce5aff11e..8ad1d85c824b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ldap.md @@ -274,7 +274,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -325,7 +325,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --ldap-starttls-options | Add custom start tls options (need --tls option): An example --ldap-starttls-options='verify=none' | | --ldap-bind-options | Add custom bind options (can force noauth) (not really useful now). | | --ldap-search-options | Add custom search options (can change the scope for example). | -| --display-entry | Display ldap entries (with --verbose option) (example: '%{cn} account locked') | +| --display-entry | Display ldap entries (with --verbose option) (example: '%\{cn\} account locked') | | --username | Specify username for authentification (can be a DN) | | --password | Specify password for authentification | | --timeout | Connection timeout in seconds (default: 30) | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-modbus.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-modbus.md index 1b3db4958162..c2b2100c2b3e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-modbus.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-modbus.md @@ -237,7 +237,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ntp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ntp.md index bd4e04bf3c0f..afff4444f717 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ntp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ntp.md @@ -248,7 +248,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ospf.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ospf.md index 784501814108..cf10d3d46ad6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ospf.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ospf.md @@ -169,12 +169,12 @@ yum install centreon-plugin-Applications-Protocol-Ospf | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{NbrState} =~ /down/i'). You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | %{NbrState} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{NbrState\} =~ /down/i'). You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | %\{NbrState\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | -| WARNINGTOTALCHANGE | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | | | -| CRITICALTOTALCHANGE | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | | | +| WARNINGTOTALCHANGE | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | | +| CRITICALTOTALCHANGE | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -202,7 +202,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-total-change='' \ --critical-total-change='' \ --warning-status='' \ - --critical-status='%{NbrState} =~ /down/i' \ + --critical-status='%\{NbrState\} =~ /down/i' \ --verbose ``` @@ -259,7 +259,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -316,10 +316,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{NbrState} =~ /down/i'). You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | -| --warning-total-change | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | -| --critical-total-change | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{NbrState\} =~ /down/i'). You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | +| --warning-total-change | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | +| --critical-total-change | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | --warning-* | Warning threshold. Can be: 'total'. | | --critical-* | Critical threshold. Can be: 'total'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-radius.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-radius.md index da34b8f494c2..0c2ad90ee119 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-radius.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-radius.md @@ -107,7 +107,7 @@ yum install centreon-pack-applications-protocol-radius --username='' \ --password='' \ --warning-status='' \ - --critical-status='%{status} ne "accepted"' \ + --critical-status='%\{status\} ne "accepted"' \ --warning-time='2' \ --critical-time='3' \ --use-new-perfdata diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-sftp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-sftp.md index 771949138c1b..0d5224d4550c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-sftp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-sftp.md @@ -199,8 +199,8 @@ yum install centreon-plugin-Applications-Protocol-Sftp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | %{message} !~ /authentication succeeded/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | %\{message\} !~ /authentication succeeded/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGTIME | Warning threshold in seconds. | | | | CRITICALTIME | Critical threshold in seconds. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -236,10 +236,10 @@ yum install centreon-plugin-Applications-Protocol-Sftp | SCENARIO | Scenario used (required). Can be a file or json content | | X | | WARNINGERRORS | Thresholds. | | | | CRITICALERRORS | Thresholds. | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}. | %{status} ne "success" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | | | -| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | -| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}. | %\{status\} ne "success" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | | | +| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | +| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGSTEPTIME | Thresholds. | | | | CRITICALSTEPTIME | Thresholds. | | | | WARNINGTOTALSTEPS | Thresholds. | | | @@ -270,7 +270,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --ssh-password='my-password' \ --scenario='' \ --warning-status='' \ - --critical-status='%{status} ne "success"' \ + --critical-status='%\{status\} ne "success"' \ --warning-total-time='' \ --critical-total-time='' \ --warning-total-steps='' \ @@ -340,7 +340,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -377,8 +377,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{message} !~ /authentication succeeded/i' You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{message\} !~ /authentication succeeded/i' You can use the following variables: %\{status\}, %\{message\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -409,10 +409,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| | --scenario | Scenario used (required). Can be a file or json content. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "success"') You can use the following variables: %{status} | -| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "success"') You can use the following variables: %\{status\} | +| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\} | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'errors', 'step-time'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-smtp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-smtp.md index 5d41a8b2111e..9057fada51af 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-smtp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-smtp.md @@ -259,7 +259,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-snmp.md index 6576e17c1b3d..987fe96ecbf7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-snmp.md @@ -237,13 +237,13 @@ yum install centreon-plugin-Applications-Protocol-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| -| FORMATOK | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | %{filter\_rows} value(s) | | -| FORMATUNKNOWN | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_unknown} | | +| FORMATOK | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | %\{filter_rows\} value(s) | | +| FORMATUNKNOWN | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_unknown\} | | | OID | OID value to check (numeric format only) | | | | WARNING | Return Warning if an oid value match the regexp | | | | CRITICAL | Return Critical if an oid value match the regexp | | | -| FORMATWARNING | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_warning} | | -| FORMATCRITICAL | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_critical} | | +| FORMATWARNING | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_warning\} | | +| FORMATCRITICAL | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_critical\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -335,7 +335,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -415,14 +415,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --perfdata-name | Perfdata name in perfdata output (Default: 'value') | | --perfdata-min | Minimum value to add in perfdata output (Default: '') | | --perfdata-max | Maximum value to add in perfdata output (Default: '') | -| --config-json | JSON format to configure the mode. Can check multiple OID. Example: --config-json='\[ { "oid": ".1.3.6.1.2.1.1.3.0", "perfdata\_name": "oid1", "format": "current oid1 value is %s"}, { "oid": ".1.3.6.1.2.1.1.3.2", "perfdata\_name": "oid2", "format": "current oid2 value is %s"} \]' | +| --config-json | JSON format to configure the mode. Can check multiple OID. Example: --config-json='\[ \{ "oid": ".1.3.6.1.2.1.1.3.0", "perfdata\_name": "oid1", "format": "current oid1 value is %s"\}, \{ "oid": ".1.3.6.1.2.1.1.3.2", "perfdata\_name": "oid2", "format": "current oid2 value is %s"\} \]' | | Option | Description | |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --oid or <--oid-leef> | OID value to check (numeric format only). | +| --oid or \<--oid-leef\> | OID value to check (numeric format only). | | --oid-table | OID table value to check (numeric format only). | | --oid-instance | OID table value for the instance (numeric format only). Can be used to have human readable instance name. | | --filter-table-value | Filter value from --oid-table option (can be a regexp). | @@ -430,7 +430,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --warning-regexp | Return Warning if an oid value match the regexp. | | --critical-regexp | Return Critical if an oid value match the regexp. | | --regexp-isensitive | Allows to use regexp non case-sensitive. | -| --format-* | Output format according to the threshold. Can be: 'ok' (default: '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | +| --format-* | Output format according to the threshold. Can be: 'ok' (default: '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | | --map-values | Use to transform an integer value in most common case. Example: --map-values='1=\>ok,10=\>fan failed,11=\>psu recovery' | | --map-value-other | Use to transform an integer value not defined in --map-values option. | | --map-values-separator | Separator uses between values (default: coma). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ssh.md index 327e30a02d03..3b5530fafac6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-ssh.md @@ -106,7 +106,7 @@ de commande depuis votre collecteur Centreon en vous connectant avec --ssh-username='' \ --ssh-password='' \ --warning-status='' \ - --critical-status='%{message} !~ /authentification succeeded/i' \ + --critical-status='%\{message\} !~ /authentification succeeded/i' \ --warning-time='2' \ --critical-time='3' \ --use-new-perfdata diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-tcp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-tcp.md index 75d1324b7cc6..6dfe216c5914 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-tcp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-tcp.md @@ -309,7 +309,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -342,9 +342,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --port | Port used | | --ssl | Use SSL connection. (no attempt is made to check the certificatevalidity by default). | | --timeout | Connection timeout in seconds (default: 3) | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{port}, %{error\_message} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{port}, %{error\_message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "failed"'). You can use the following variables: %{status}, %{port}, %{error\_message} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "failed"'). You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | | --warning-time | Warning threshold in seconds | | --critical-time | Critical threshold in seconds | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-telnet.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-telnet.md index 872987fc9bec..ff2ba65497fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-telnet.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-telnet.md @@ -19,11 +19,11 @@ The remote server must have a Telnet service running and available. You need to create a JSON scenario file. An example: [ - {"cmd": "open", "options": { "Host": "10.0.0.1", "Port": "23", "Timeout": "30" } }, - {"cmd": "login", "options": { "Name": "admin", "Password": "pass", "Timeout": "5" } }, - {"cmd": "waitfor", "options": { "Match": "/string/", "Timeout": "5" } }, - {"cmd": "put", "options": { "String": "/mystring/", "Timeout": "5" } }, - {"cmd": "close" } + \{"cmd": "open", "options": \{ "Host": "10.0.0.1", "Port": "23", "Timeout": "30" \} \}, + \{"cmd": "login", "options": \{ "Name": "admin", "Password": "pass", "Timeout": "5" \} \}, + \{"cmd": "waitfor", "options": \{ "Match": "/string/", "Timeout": "5" \} \}, + \{"cmd": "put", "options": \{ "String": "/mystring/", "Timeout": "5" \} \}, + \{"cmd": "close" \} ] ## Centreon Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-x509.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-x509.md index 031ce83b28f9..384a5814aef7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-x509.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-protocol-x509.md @@ -156,8 +156,8 @@ yum install centreon-plugin-Applications-Protocol-X509 |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | CUSTOMMODE | | tcp | | | PORT | Port used by host | 443 | X | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (Default: '%{expiration} \< 60'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects} | %{expiration} \< 60 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%{expiration} \< 30'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%{expiration} \< 30 \|\| %{alt\_subjects} !~ /my.app.com/' | %{expiration} \< 30 | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (Default: '%\{expiration\} \< 60'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\} | %\{expiration\} \< 60 | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expiration\} \< 30'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%\{expiration\} \< 30 \|\| %\{alt_subjects\} !~ /my.app.com/' | %\{expiration\} \< 30 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -180,8 +180,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --custommode='tcp' \ --hostname='www.google.com' \ --port=443 \ - --warning-status='%{expiration} < 60' \ - --critical-status='%{expiration} < 30' + --warning-status='%\{expiration\} < 60' \ + --critical-status='%\{expiration\} < 30' ``` La commande devrait retourner un message de sortie similaire à : @@ -326,7 +326,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -345,8 +345,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --disco-show | Applies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery. | | --float-precision | Define the float precision for thresholds (default: 8). | | --source-encoding | Define the character encoding of the response sent by the monitored resource Default: 'UTF-8'. | -| --warning-status | Define the conditions to match for the status to be WARNING. (Default: '%{expiration} \< 60'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{expiration} \< 30'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%{expiration} \< 30 \|\| %{alt\_subjects} !~ /my.app.com/' | +| --warning-status | Define the conditions to match for the status to be WARNING. (Default: '%\{expiration\} \< 60'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expiration\} \< 30'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%\{expiration\} \< 30 \|\| %\{alt_subjects\} !~ /my.app.com/' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pvx-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pvx-restapi.md index 5b71fcd0a211..c4292182053d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pvx-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-pvx-restapi.md @@ -91,7 +91,7 @@ Le connecteur a été testé avec la version suivante : \* PVX version 5.1.1. Pour interroger les instances via l'API, une clé d'accès est nécessaire. Cette clé n'a pas de date d'expiration. La procédure suivante, extrait de la -[documentation officielle](), +[documentation officielle](http://docs.performancevision.com/api_use.html), permet de la générer. A chaque étape, remplacez les valeurs des macro '< \>' avec les vôtres. diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md index 1bede69d4496..a06d9182922d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md @@ -189,12 +189,12 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | %{status} =~ /unreachable/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /unreachable/i | | | FILTERNAME | Filter agent name (can be a regexp) | | | | WARNINGRECOVERYPOINTS | Thresholds | | | | CRITICALRECOVERYPOINTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /failed\|authenticationError/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /failed\|authenticationError/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -204,7 +204,7 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /unknown/i | | | FILTERNAME | Filter repository name (can be a regexp) | | | | WARNINGSPACEUSAGE | Thresholds | | | | CRITICALSPACEUSAGE | Thresholds | | | @@ -212,8 +212,8 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /error/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -237,9 +237,9 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --filter-name='' \ - --unknown-status='%{status} =~ /unknown/i' \ + --unknown-status='%\{status\} =~ /unknown/i' \ --warning-status='' \ - --critical-status='%{status} =~ /error/i' \ + --critical-status='%\{status\} =~ /error/i' \ --warning-space-usage='' \ --critical-space-usage='' \ --warning-space-usage-free='' \ @@ -301,7 +301,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -355,9 +355,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unreachable/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed\|authenticationError/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unreachable/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed\|authenticationError/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'recoverypoints'. | | --filter-name | Filter agent name (can be a regexp). | @@ -366,9 +366,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /error/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage' (B), 'space-usage-free' (B), 'space-usage-prct' (%). | | --filter-name | Filter repository name (can be a regexp). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-redis-sentinel.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-redis-sentinel.md index 02e9028179a8..9009a5e13070 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-redis-sentinel.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-redis-sentinel.md @@ -60,10 +60,10 @@ Il apporte les Modèles de Service suivants : Afin de superviser Redis Sentinel, le collecteur doit pouvoir réaliser des requêtes avec l'utilitaire **redis-cli** sur le port TCP/26379 (par défaut). Voici la liste des commandes utilisées: -* sentinel ckquorum +* sentinel ckquorum \ * sentinel masters -* sentinel replicas -* sentinel sentinels +* sentinel replicas \ +* sentinel sentinels \ ## Installation diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rrdcached.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rrdcached.md index dcb3e434688f..619d83f0a583 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rrdcached.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rrdcached.md @@ -302,8 +302,8 @@ yum install centreon-plugin-Applications-RRDCached | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:---------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| CRITICALRESPONSE | Define the conditions to match for the status to be CRITICAL. You can use the variable '%{response}'. | %{response} !~ /PONG/ | | -| WARNINGRESPONSE | Define the conditions to match for the status to be WARNING. You can use the variable '%{response}'. | | | +| CRITICALRESPONSE | Define the conditions to match for the status to be CRITICAL. You can use the variable '%\{response\}'. | %\{response\} !~ /PONG/ | | +| WARNINGRESPONSE | Define the conditions to match for the status to be WARNING. You can use the variable '%\{response\}'. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -398,7 +398,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -451,8 +451,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------|:------------| -| --warning-response | Define the conditions to match for the status to be WARNING. You can use the variable '%{response}'. | -| --critical-response | Define the conditions to match for the status to be CRITICAL. You can use the variable '%{response}'. Default: '%{response} !~ /PONG/'. | +| --warning-response | Define the conditions to match for the status to be WARNING. You can use the variable '%\{response\}'. | +| --critical-response | Define the conditions to match for the status to be CRITICAL. You can use the variable '%\{response\}'. Default: '%\{response\} !~ /PONG/'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rubrik-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rubrik-restapi.md index 5ded539a77c1..f428322414e6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rubrik-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rubrik-restapi.md @@ -144,7 +144,7 @@ L'API peut être utilisée pour interroger, configurer et contrôler presque tou Si vous avez accès à un cluster Rubrik, vous pouvez également utiliser l'aire de jeu Rubrik API à l'adresse suivante: -https://{{node_ip}}/docs/{{v1|v2|internal}}/playground +https://\{\{node_ip\}\}/docs/\{\{v1|v2|internal\}\}/playground _Note : les paramètres internes de l'API peuvent changer entre les versions du MDP2_ @@ -269,13 +269,13 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | CLUSTERID | Which cluster to check (default: 'me') | me | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGREAD | Threshold | | | | CRITICALREAD | Threshold | | | | WARNINGREADIOPS | Threshold | | | | CRITICALREADIOPS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGWRITE | Threshold | | | | CRITICALWRITE | Threshold | | | | WARNINGWRITEIOPS | Threshold | | | @@ -305,8 +305,8 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | CRITICALCLUSTERDISKSACTIVE | Threshold | | | | WARNINGCLUSTERDISKSTOTAL | Threshold | | | | CRITICALCLUSTERDISKSTOTAL | Threshold | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{id} | %{status} !~ /active/i | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{id\} | %\{status\} !~ /active/i | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -319,8 +319,8 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | FILTERJOBTYPE | Filter jobs by job type | | | | FILTEROBJECTTYPE | Filter jobs by object type | | | | FILTERLOCATIONNAME | Filter jobs by location name | | | -| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (default: %{status} =~ /Failure/i). You can use the following variables: %{status}, %{jobName} | %{status} =~ /failure/i | | -| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | | | +| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (default: %\{status\} =~ /Failure/i). You can use the following variables: %\{status\}, %\{jobName\} | %\{status\} =~ /failure/i | | +| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | | | | WARNINGJOBEXECUTIONLAST | Threshold | | | | CRITICALJOBEXECUTIONLAST | Threshold | | | | WARNINGJOBEXECUTIONSFAILEDPRCT | Threshold | | | @@ -338,13 +338,13 @@ yum install centreon-plugin-Applications-Rubrik-Restapi |:--------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | CLUSTERID | Which cluster to check (default: 'me') | me | | | FILTERNODEID | Filter nodes by node ID (can be a regexp) | | | -| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{ip\_address}, %{id} | | | +| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | | | WARNINGCLUSTERNODESOK | Threshold | | | | CRITICALCLUSTERNODESOK | Threshold | | | | WARNINGCLUSTERNODESTOTAL | Threshold | | | | CRITICALCLUSTERNODESTOTAL | Threshold | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{ip\_address}, %{id} | %{status} !~ /ok/i | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{ip\_address}, %{id} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | %\{status\} !~ /ok/i | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -411,7 +411,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-jobs-executions-detected='' \ --critical-jobs-executions-detected='' \ --warning-execution-status='' \ - --critical-execution-status='%{status} =~ /failure/i' \ + --critical-execution-status='%\{status\} =~ /failure/i' \ --verbose ``` @@ -477,7 +477,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -541,9 +541,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --cluster-id | Which cluster to check (default: 'me'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'read' (B/s), 'write' (B/s), 'read-iops', 'write-iops'. | @@ -562,9 +562,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='disk-status' | | --cluster-id | Which cluster to check (default: 'me'). | | --filter-disk-id | Filter disks by disk ID (can be a regexp). | -| --unknown-disks-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{id} | -| --warning-disk-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{id} | +| --unknown-disks-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{id\} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'cluster-disks-total', 'cluster-disks-active'. | @@ -580,9 +580,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --unit | Select the time unit for last execution time thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --limit | Define the number of entries to retrieve for the pagination (default: 500). | | --check-retention | Use the retention file to check if a job have been detected once but does not appear in the API response. | -| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --warning-execution-status | Set warning threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --critical-execution-status | Set critical threshold for last job execution status (default: %{status} =~ /Failure/i). You can use the following variables: %{status}, %{jobName} | +| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --warning-execution-status | Set warning threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --critical-execution-status | Set critical threshold for last job execution status (default: %\{status\} =~ /Failure/i). You can use the following variables: %\{status\}, %\{jobName\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-executions-detected', 'job-executions-failed-prct', 'job-execution-last', 'job-running-duration'. | @@ -593,9 +593,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='node-status' | | --cluster-id | Which cluster to check (default: 'me'). | | --filter-node-id | Filter nodes by node ID (can be a regexp). | -| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{ip\_address}, %{id} | -| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{ip\_address}, %{id} | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{ip\_address}, %{id} | +| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | +| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'cluster-nodes-total', 'cluster-nodes-ok'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rudder-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rudder-restapi.md index 19d1992e7bae..af87a6b9a25d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rudder-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-rudder-restapi.md @@ -18,7 +18,7 @@ yum install centreon-plugin-Applications-Rudder-Restapi A token needs to be created to acces the API. To do so, follow the official documentation here : -. +\. ## Centreon Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sahipro-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sahipro-restapi.md index 57897d650df5..71fa2730c327 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sahipro-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sahipro-restapi.md @@ -177,19 +177,19 @@ yum install centreon-plugin-Applications-Sahipro-Restapi | SAHIBROWSERTYPE | Browser used for script executions (Default: chrome) | chrome | | | RETRIESSCENARIOSTATUS | Define the number of retries to get scenario status (if we fail to get the status) | 0 | | | INTERVALSCENARIOSTATUS | Define time interval to get scenario status in seconds (default: 10) | 10 | | -| UNKNOWNRUNSTATUS | Unknown threshold for running scenario rest api response. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | %{http\_code} \< 200 or %{http\_code} \>= 300 | | +| UNKNOWNRUNSTATUS | Unknown threshold for running scenario rest api response. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | %\{http_code\} \< 200 or %\{http_code\} \>= 300 | | | SAHISUITE | Define path for scenario files (required. Example: 'sahitests/small.suite') | | | | SAHIBASEURL | Define default Start URL for scripts | | | | TIMEOUT | Define the global script timeout. If timeout is reached, scenario is killed | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | | WARNINGERRORS | Thresholds | | | | CRITICALERRORS | Thresholds | | | | WARNINGFAILURES | Thresholds | | | | CRITICALFAILURES | Thresholds | | | | WARNINGRUNSTATUS | Warning threshold for running scenario rest api response | | | | CRITICALRUNSTATUS | Critical threshold for running scenario rest api response | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "SUCCESS"'). You can use the following variables: %{status} | %{status} ne "SUCCESS" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "SUCCESS"'). You can use the following variables: %\{status\} | %\{status\} ne "SUCCESS" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | WARNINGSTEPTIME | Thresholds | | | | CRITICALSTEPTIME | Thresholds | | | | WARNINGTOTALSTEPS | Thresholds | | | @@ -280,7 +280,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -319,11 +319,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --timeout | Define the global script timeout. If timeout is reached, scenario is killed. | | --retries-scenario-status | Define the number of retries to get scenario status (if we fail to get the status). | | --interval-scenario-status | Define time interval to get scenario status in seconds (default: 10). | -| --unknown-run-status | Unknown threshold for running scenario rest api response. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-run-status | Unknown threshold for running scenario rest api response. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-run-status | Warning threshold for running scenario rest api response. | | --critical-run-status | Critical threshold for running scenario rest api response. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "SUCCESS"'). You can use the following variables: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "SUCCESS"'). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'failures', 'errors', 'step-time'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md index 02b188d90130..aaefaec663e3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md @@ -194,7 +194,7 @@ yum install centreon-plugin-Applications-Sailpoint-Identitynow-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:----------------------------------------------------------------------------------------------------|:----------------------------|:------------| -| OUTPUT | Output to print after retrieving the count of results (Default: "Number of results: %{count}") | Number of results: %{count} | | +| OUTPUT | Output to print after retrieving the count of results (Default: "Number of results: %\{count\}") | Number of results: %\{count\} | | | QUERY | Query parameters used to construct an Elasticsearch query object (see documentation) | | | | WARNINGRESULTSCOUNT | | | | | CRITICALRESULTSCOUNT | | | | @@ -208,7 +208,7 @@ yum install centreon-plugin-Applications-Sailpoint-Identitynow-Restapi | SOURCEID | Define source ID to retrieve only one source health status (useful with service discovery) | | | | FILTERNAME | Filter source name (Can be a regexp) | | | | FILTERTYPE | Filter source type (Can be a regexp) | | | -| CRITICALHEALTHSTATUS | Set critical threshold for each source health status (Default: '%{status} ne "SOURCE\_STATE\_HEALTHY"') | %{status} ne "SOURCE_STATE_HEALTHY" | | +| CRITICALHEALTHSTATUS | Set critical threshold for each source health status (Default: '%\{status\} ne "SOURCE\_STATE\_HEALTHY"') | %\{status\} ne "SOURCE_STATE_HEALTHY" | | | WARNINGHEALTHSTATUS | Set warning threshold for each source health status (Default: none) | | | | WARNINGSOURCESERROR | Set threshold for each status counter | | | | CRITICALSOURCESERROR | Set threshold for each status counter | | | @@ -307,7 +307,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -363,7 +363,7 @@ Les options spécifiques aux modes sont listées ci-dessous : | Option | Description | Type | |:-------------------------------------------------|:--------------------------------------------------------------------------------------------------|:-----| | --query | Query parameters used to construct an Elasticsearch query object(see documentation). | Mode | -| --output | Output to print after retrieving the count of results (Default: "Number of results: %{count}"). | Mode | +| --output | Output to print after retrieving the count of results (Default: "Number of results: %\{count\}"). | Mode | | --warning-results-count --critical-results-count | Thresholds on count of results. | Mode | @@ -375,7 +375,7 @@ Les options spécifiques aux modes sont listées ci-dessous : | --filter-name | Filter source name (Can be a regexp). | Mode | | --filter-type | Filter source type (Can be a regexp). | Mode | | --warning-health-status | Set warning threshold for each source health status (Default: none). | Mode | -| --critical-health-status | Set critical threshold for each source health status (Default: '%{status} ne "SOURCE\_STATE\_HEALTHY"'). | Mode | +| --critical-health-status | Set critical threshold for each source health status (Default: '%\{status\} ne "SOURCE\_STATE\_HEALTHY"'). | Mode | | --warning-sources-* --critical-sources-* | Set threshold for each status counter. Can be: 'healthy', 'error', 'failure', 'unchecked'. | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-salesforce-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-salesforce-restapi.md index f71e99bd5c77..385a046ccb58 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-salesforce-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-salesforce-restapi.md @@ -242,7 +242,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -275,7 +275,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --alias | Add this option if your want to use your instance alias | | --unknown-status | Set unknown threshold for instance status (default: ''). | | --warning-status | Set warning threshold for instance status (default: ''). | -| --critical-status | Set critical threshold for instance status (default: '%{status} !~ /OK/'). | +| --critical-status | Set critical threshold for instance status (default: '%\{status\} !~ /OK/'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sccm-nsclient.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sccm-nsclient.md index db82877b3054..0ebd3bf3718b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sccm-nsclient.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-sccm-nsclient.md @@ -154,7 +154,7 @@ depuis un collecteur Centreon en vous connectant avec l'utilisateur *centreon-en -p 5666 \ -t 30 \ -u -m 8192 \ - -c check_centreon_plugins -a 'apps::sccm::local::plugin' 'site-status' '--critical-status="%{status} eq FAILED"' + -c check_centreon_plugins -a 'apps::sccm::local::plugin' 'site-status' '--critical-status="%\{status\} eq FAILED"' ``` La commande devrait retourner un message de sortie de la forme ci-dessous: @@ -191,7 +191,7 @@ en ajoutant le paramètre ```--help``` à la commande: --command=check_centreon_plugins \ --arg='apps::sccm::local::plugin' \ --arg='site-status' \ - --arg='--critical-status="%{status} eq FAILED"' + --arg='--critical-status="%\{status\} eq FAILED"' ``` La commande devrait retourner un message de sortie de la forme ci-dessous: diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-slack-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-slack-restapi.md index 8e0df07eda03..1d42428031a6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-slack-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-slack-restapi.md @@ -124,8 +124,8 @@ depuis un collecteur Centreon en vous connectant avec l'utilisateur *centreon-en --mode=services \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-name='Connections|Messaging' \ - --warning-status='%{status} eq "active" and %{type} eq "incident"' \ - --critical-status='%{status} eq "active" and %{type} eq "outage"' \ + --warning-status='%\{status\} eq "active" and %\{type\} eq "incident"' \ + --critical-status='%\{status\} eq "active" and %\{type\} eq "outage"' \ --verbose ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-tosca-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-tosca-restapi.md index 92b1a33d46b6..5f84679dfed7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-tosca-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-tosca-restapi.md @@ -200,8 +200,8 @@ yum install centreon-plugin-Applications-Tosca-Restapi | SCENARIOID | Scenario unique ID | | | | WARNINGDURATION | Thresholds | | | | CRITICALDURATION | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{result} !~ /Passed/'). You can use the following variables: %{result} | %{result} !~ /Passed/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{result} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{result\} !~ /Passed/'). You can use the following variables: %\{result\} | %\{result\} !~ /Passed/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{result\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -279,7 +279,7 @@ Les options génériques aux modes sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -333,8 +333,8 @@ Les options spécifiques aux modes sont listées ci-dessous : |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:-----| | --workspace | Workspace name of the provided scenario. | Mode | | --scenario-id | Scenario unique ID. | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{result} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{result} !~ /Passed/'). You can use the following variables: %{result} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{result\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{result\} !~ /Passed/'). You can use the following variables: %\{result\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'duration'. | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md index 335e3e7c5d28..c0f55d1980f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md @@ -333,7 +333,7 @@ yum install centreon-plugin-Applications-TrendMicro-Iwsva | CRITICALIN | Critical thresholds for in traffic | 90 | | | WARNINGOUT | Warning thresholds for out traffic | 80 | | | CRITICALOUT | Critical thresholds for out traffic | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -438,7 +438,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -599,9 +599,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nrpe.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nrpe.md index 03f245238e02..530f68b9172f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nrpe.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nrpe.md @@ -216,11 +216,11 @@ yum install centreon-nrpe3-plugin | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter job with start time greater than current time less value in seconds | | | | FILTERCOUNTERS | Only display some counters (regexp can be used). | | | -| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -240,8 +240,8 @@ yum install centreon-nrpe3-plugin | CRITICALLICENSEINSTANCESUSAGE | Thresholds | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Thresholds | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -259,8 +259,8 @@ yum install centreon-nrpe3-plugin | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -269,8 +269,8 @@ yum install centreon-nrpe3-plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -290,8 +290,8 @@ yum install centreon-nrpe3-plugin | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCESS | Thresholds | | | | CRITICALJOBSSUCCESS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -311,7 +311,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : /usr/lib64/nagios/plugins//check_centreon_nrpe -H 10.0.0.1 -p 5666 -t 55 -c check_centreon_plugins -a 'apps::backup::veeam::local::plugin' 'tape-jobs' ' \ --filter-name="" \ --warning-status="" \ - --critical-status="%{enabled} == 1 and not %{last_result} =~ /Success|None/i" \ + --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \ --warning-total="" \ --critical-total="" \ --verbose' @@ -373,7 +373,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -414,11 +414,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (default: 86400). | -| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -437,8 +437,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the time unit for the expiration thresholds. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -457,8 +457,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -476,9 +476,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -497,9 +497,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md index d6fe4c6ecccc..23d05ae66f90 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md @@ -222,11 +222,11 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter job with start time greater than current time less value in seconds | | | | FILTERCOUNTERS | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\ |yyyy$' | | | -| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -246,8 +246,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALLICENSEINSTANCESUSAGE | Threshold | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Threshold | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -265,8 +265,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALSPACEUSAGEFREE | Threshold | | | | WARNINGSPACEUSAGEPRCT | Threshold | | | | CRITICALSPACEUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -275,8 +275,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -296,8 +296,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALJOBSFAILED | Threshold | | | | WARNINGJOBSSUCCESS | Threshold | | | | CRITICALJOBSSUCCESS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,7 +336,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-jobs-warning="" \ --critical-jobs-warning="" \ --warning-status="" \ - --critical-status="not %{status} =~ /success/i" \ + --critical-status="not %\{status\} =~ /success/i" \ --verbose' ``` @@ -396,7 +396,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -442,11 +442,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (default: 86400). | -| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -465,8 +465,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the time unit for the expiration thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -485,8 +485,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -504,9 +504,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -525,9 +525,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md index 0bd5df0d259a..aa6fe078be79 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md @@ -204,8 +204,8 @@ yum install centreon-plugin-Applications-Veeam-Vbem-Restapi | FILTERUID | Filter jobs by UID | | | | FILTERNAME | Filter jobs by name | | | | FILTERTYPE | Filter jobs by type | | | -| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status (Default: %{status} =~ /warning/i). You can use the following variables like: %{status}, %{jobName} | %{status} =~ /warning/i | | -| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (Default: %{status} =~ /failed/i). You can use the following variables: %{status}, %{jobName} | %{status} =~ /failed/i | | +| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status (Default: %\{status\} =~ /warning/i). You can use the following variables like: %\{status\}, %\{jobName\} | %\{status\} =~ /warning/i | | +| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (Default: %\{status\} =~ /failed/i). You can use the following variables: %\{status\}, %\{jobName\} | %\{status\} =~ /failed/i | | | WARNINGJOBEXECUTIONLAST | Thresholds | | | | CRITICALJOBEXECUTIONLAST | Thresholds | | | | WARNINGJOBEXECUTIONSFAILEDPRCT | Thresholds | | | @@ -318,7 +318,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,9 +378,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-type | Filter jobs by type. | | --timeframe | Timeframe to get BackupJobSession (in seconds. Default: 86400). | | --unit | Select the unit for last execution time threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | -| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --warning-execution-status | Set warning threshold for last job execution status (Default: %{status} =~ /warning/i). You can use the following variables like: %{status}, %{jobName} | -| --critical-execution-status | Set critical threshold for last job execution status (Default: %{status} =~ /failed/i). You can use the following variables: %{status}, %{jobName} | +| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --warning-execution-status | Set warning threshold for last job execution status (Default: %\{status\} =~ /warning/i). You can use the following variables like: %\{status\}, %\{jobName\} | +| --critical-execution-status | Set critical threshold for last job execution status (Default: %\{status\} =~ /failed/i). You can use the following variables: %\{status\}, %\{jobName\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-executions-detected', 'job-executions-failed-prct', 'job-execution-last', 'job-running-duration'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-wsman.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-wsman.md index 9eb1a9c568d3..15a23320db97 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-wsman.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-veeam-wsman.md @@ -213,11 +213,11 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter out jobs whose start date is older than the value specified in seconds | | | | FILTERCOUNTERS | | | | -| OKSTATUS | Set ok threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Set ok threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -237,8 +237,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALLICENSEINSTANCESUSAGE | Thresholds | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Thresholds | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -256,8 +256,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: 'not %{status} =~ /ordinal\|maintenance/i'). Can use special variables like: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: 'not %\{status\} =~ /ordinal\|maintenance/i'). Can use special variables like: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -266,8 +266,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -287,8 +287,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCESS | Thresholds | | | | CRITICALJOBSSUCCESS | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: 'not %{status} =~ /success/i'). Can use special variables like: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: 'not %\{status\} =~ /success/i'). Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -317,7 +317,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --wsman-auth-method='basic' \ --filter-name="" \ --warning-status="" \ - --critical-status="%{enabled} == 1 and not %{last_result} =~ /Success|None/i" \ + --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \ --warning-total="" \ --critical-total="" \ --verbose @@ -379,7 +379,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -428,11 +428,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (Default: 86400). | -| --ok-status | Set ok threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Set warning threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Set critical threshold for status (Default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Set ok threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Set critical threshold for status (Default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -446,8 +446,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Set warning threshold for status. Can use special variables like: %{to}, %{status}, %{type}. | -| --critical-status | Set critical threshold for status (Default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{to}, %{status}, %{type}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Set critical threshold for status (Default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the unit for expires threshold. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -461,8 +461,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Set warning threshold for status. Can use special variables like: %{status}, %{name}, %{type}. | -| --critical-status | Set critical threshold for status (Default: 'not %{status} =~ /ordinal\|maintenance/i'). Can use special variables like: %{status}, %{name}, %{type}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Set critical threshold for status (Default: 'not %\{status\} =~ /ordinal\|maintenance/i'). Can use special variables like: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -475,9 +475,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Set unknown threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Set warning threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Set critical threshold for status (Default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Set unknown threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Set warning threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Set critical threshold for status (Default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -491,9 +491,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Set unknown threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Set warning threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Set critical threshold for status (Default: 'not %{status} =~ /success/i'). Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Set unknown threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Set critical threshold for status (Default: 'not %\{status\} =~ /success/i'). Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vernemq-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vernemq-restapi.md index 3930e123d28d..df6dd4693575 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vernemq-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vernemq-restapi.md @@ -207,13 +207,13 @@ yum install centreon-plugin-Applications-Vernemq-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | FILTERNAME | Filter cluster name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGNOTRUNNING | Thresholds | | | | CRITICALNOTRUNNING | Thresholds | | | | WARNINGRUNNING | Thresholds | | | | CRITICALRUNNING | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "notRunning"'). You can use the following variables: %{status}, %{display} | %{status} eq "notRunning" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "notRunning"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "notRunning" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -222,13 +222,13 @@ yum install centreon-plugin-Applications-Vernemq-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERTYPE | Filter listener type (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGNOTRUNNING | Thresholds | | | | CRITICALNOTRUNNING | Thresholds | | | | WARNINGRUNNING | Thresholds | | | | CRITICALRUNNING | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "running"'). You can use the following variables: %{status}, %{display} | %{status} ne "running" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "running"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} ne "running" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,7 +336,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,9 +378,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter cluster name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "notRunning"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "notRunning"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'running', 'notrunning'. | @@ -389,9 +389,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-type | Filter listener type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "running"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "running"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'running', 'notrunning'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md index 7a69bc7060b0..1d3866ca7418 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md @@ -160,9 +160,9 @@ yum install centreon-plugin-Applications-Vmware-Vcsa-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERSERVICE | Define which services should be monitored based on the services' names. This option will be treated as a regular expression. | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{health} !~ /green/'). You can use the following variables: %{health}, %{display} | %{health} !~ /green/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{health\} !~ /green/'). You can use the following variables: %\{health\}, %\{display\} | %\{health\} !~ /green/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -190,7 +190,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-service='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{health} !~ /green/' \ + --critical-status='%\{health\} !~ /green/' \ --verbose ``` @@ -250,7 +250,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -295,9 +295,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-service | Define which services should be monitored based on the services' names. This option will be treated as a regular expression. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{health} !~ /green/'). You can use the following variables: %{health}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{health\} !~ /green/'). You can use the following variables: %\{health\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md index ebf43dc3106f..611a90091e14 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md @@ -174,7 +174,7 @@ yum install centreon-plugin-Applications-Voip-3cx-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{error}, %{service} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{error\}, %\{service\} | | | | WARNINGCALLSACTIVEFREE | Thresholds | | | | CRITICALCALLSACTIVEFREE | Thresholds | | | | WARNINGCALLSACTIVEUSAGE | Thresholds | | | @@ -183,8 +183,8 @@ yum install centreon-plugin-Applications-Voip-3cx-Restapi | CRITICALCALLSACTIVEUSAGEPRCT | Thresholds | | | | WARNINGEXTENSIONSREGISTERED | Thresholds | | | | CRITICALEXTENSIONSREGISTERED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{error} =~ /false/'). You can use the following variables: %{error}, %{service} | %{error} =~ /true/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{error}, %{service} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{error\} =~ /false/'). You can use the following variables: %\{error\}, %\{service\} | %\{error\} =~ /true/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{error\}, %\{service\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -212,7 +212,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --3cx-version='18.0.9.20' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{error} =~ /true/' \ + --critical-status='%\{error\} =~ /true/' \ --warning-calls-active-usage='' \ --critical-calls-active-usage='' \ --warning-calls-active-free='' \ @@ -280,7 +280,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -306,9 +306,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --api-username | Define the username for authentication. | | --api-password | Define the password associated with the username. | | --timeout | Define the timeout in seconds (default: 30). | -| --unknown-http-status | Define the conditions to match on the HTTP Status for the returned status to be UNKNOWN. Default: '%{http\_code} \< 200 or %{http\_code} \>= 300' | -| --warning-http-status | Define the conditions to match on the HTTP Status for the returned status to be WARNING. Example: '%{http\_code} == 500' | -| --critical-http-status | Define the conditions to match on the HTTP Status for the returned status to be CRITICAL. Example: '%{http\_code} == 500' | +| --unknown-http-status | Define the conditions to match on the HTTP Status for the returned status to be UNKNOWN. Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300' | +| --warning-http-status | Define the conditions to match on the HTTP Status for the returned status to be WARNING. Example: '%\{http_code\} == 500' | +| --critical-http-status | Define the conditions to match on the HTTP Status for the returned status to be CRITICAL. Example: '%\{http_code\} == 500' | | --http-peer-addr | Set the address you want to connect to. Useful if hostname is only a vhost, to avoid IP resolution. | | --proxyurl | Proxy URL. Example: http://my.proxy:3128 | | --proxypac | Proxy pac file (can be a URL or a local file). | @@ -329,9 +329,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-category | Filter updates' category. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{error}, %{service} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{error}, %{service} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{error} =~ /false/'). You can use the following variables: %{error}, %{service} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{error\}, %\{service\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{error\}, %\{service\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{error\} =~ /false/'). You can use the following variables: %\{error\}, %\{service\} | | --warning-* --critical-* | Thresholds. Can be: 'calls-active-usage', 'calls-active-free', 'calls-active-usage-prct', 'extensions-registered'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-wazuh-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-wazuh-restapi.md index 5c67f2cf58fe..bb2fe6560c8d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-wazuh-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-wazuh-restapi.md @@ -187,8 +187,8 @@ yum install centreon-plugin-Applications-Wazuh-Restapi | CRITICALNEVERCONNECTED | Thresholds | | | | WARNINGPENDING | Thresholds | | | | CRITICALPENDING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -208,8 +208,8 @@ yum install centreon-plugin-Applications-Wazuh-Restapi | CRITICALPROCESSESRUNNING | Thresholds | | | | WARNINGPROCESSESSTOPPED | Thresholds | | | | CRITICALPROCESSESSTOPPED | Thresholds | | | -| WARNINGPROCESSSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALPROCESSSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{display} | | | +| WARNINGPROCESSSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALPROCESSSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -302,7 +302,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -359,8 +359,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter agent name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'active', 'pending', 'neverconnected', 'disconnected'. | @@ -371,8 +371,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-process | Filter process name (can be a regexp). | | --filter-log | Filter log name (can be a regexp). | -| --warning-process-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | -| --critical-process-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{display} | +| --warning-process-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-process-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'processes-running', 'processes-stopped', 'log-error', 'log-critical', 'log-warning'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md index a047f9afa87e..a82eb32d4cb6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md @@ -203,8 +203,8 @@ yum install centreon-plugin-Applications-Webservers-Iis-Restapi | FILTERNAME | Filter application pool name (can be a regexp) | .* | | | WARNINGREQUESTS | Thresholds | | | | CRITICALREQUESTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{auto\_start} eq "true" and %{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{auto\_start}, %{display} | %{auto\_start} eq "true" and %{status} !~ /starting\|started/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{auto\_start}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | %\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -219,8 +219,8 @@ yum install centreon-plugin-Applications-Webservers-Iis-Restapi | CRITICALCONNECTIONSTOTAL | Thresholds | | | | WARNINGREQUESTS | Thresholds | | | | CRITICALREQUESTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{display} | %{status} !~ /starting\|started/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /starting\|started/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -252,7 +252,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --api-token='' \ --filter-name='.*' \ --warning-status='' \ - --critical-status='%{status} !~ /starting|started/' \ + --critical-status='%\{status\} !~ /starting|started/' \ --warning-requests='' \ --critical-requests='' \ --warning-traffic-in='' \ @@ -322,7 +322,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -379,9 +379,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter application pool name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{auto\_start}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{auto\_start}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{auto\_start} eq "true" and %{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{auto\_start}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'requests'. | @@ -391,9 +391,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter website name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'requests', 'traffic-in', 'traffic-out', 'connections-current', 'connections-total'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md index f304b798e93b..8d4860f594b0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md @@ -54,16 +54,16 @@ Pour activer ce module, vous devez ouvrir votre fichier de configuration nginx. and ajouter les lignes suivantes dans la parenthèse 'server': - server { - ... - location /nginx_status { - stub_status on; + server \{ + ... + location /nginx_status \{ + stub_status on; access_log off; - allow ; - deny all; - } + allow \; + deny all; + \} ... - } + \} Assurez-vous que le collecteur est authorisé à accéder à cette URL. @@ -79,7 +79,7 @@ Nginx doit être rechargé pour prendre en compte cette modification : Accéder à l'url suivante pour contrôler le résultat : - http:///nginx_status + http://\/nginx_status ## Installation diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md index f7615949e412..c9c0ff7627da 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md @@ -36,7 +36,7 @@ You need to configure an account with the manage role. Add in */usr/share/tomcat6/conf/tomcat-users.xml* file: - + \ Tomcat must be restarted: diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/base-generic.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/base-generic.md index fd28a8472312..de44d912d941 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/base-generic.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/base-generic.md @@ -166,7 +166,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-apigateway.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-apigateway.md index 12c8c005b4c2..b7c499713799 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-apigateway.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-apigateway.md @@ -334,7 +334,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-backup.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-backup.md index d874b40a4e45..3f54af96220c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-backup.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-backup.md @@ -335,7 +335,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-billing.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-billing.md index 9159f6fab0a2..26d169b23c0f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-billing.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-billing.md @@ -302,7 +302,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md index 1587edd5ed97..e9ad3114c8f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md @@ -362,7 +362,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md index ef91731f8b04..0cabc5d7a788 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md @@ -214,8 +214,8 @@ yum install centreon-plugin-Cloud-Aws-Cloudwatch-Api | AWSCUSTOMMODE | When a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option | awscli | | | AWSREGION | Set the region name (required) | | X | | FILTERALARMNAME | Filter by alarm name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | %{state\_value} =~ /INSUFFICIENT\_DATA/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | %{state\_value} =~ /ALARM/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | %\{state_value\} =~ /INSUFFICIENT\_DATA/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | %\{state_value\} =~ /ALARM/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -324,7 +324,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -389,8 +389,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-alarm-name | Filter by alarm name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state\_value} =~ /INSUFFICIENT\_DATA/i') You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state\_value} =~ /ALARM/i'). You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state_value\} =~ /INSUFFICIENT\_DATA/i') You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state_value\} =~ /ALARM/i'). You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | | --memory | Only check new alarms. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md index 82fdca18c0f8..0ecaaa45b7e3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md @@ -216,9 +216,9 @@ yum install centreon-plugin-Cloud-Aws-Cloudwatchlogs-Api | GROUPNAME | Set log group name (required) | | | | STREAMNAME | Filters the results to only logs from the log stream (multiple option) | | | | STARTTIMESINCE | Lookup logs last X seconds ago. If not set: lookup logs since the last execution | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{message}, %{stream\_name}, %{since} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -316,9 +316,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --group-name | Set log group name (required). | | --stream-name | Filters the results to only logs from the log stream (multiple option). | | --start-time-since | Lookup logs last X seconds ago. If not set: lookup logs since the last execution. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{message}, %{stream\_name}, %{since} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | | --dyn-mode | Specify a mode with the module's path (advanced). | | --list-mode | List all available modes. | @@ -331,7 +331,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-directconnect.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-directconnect.md index 8616aca4cb99..4b82975838d9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-directconnect.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-directconnect.md @@ -252,8 +252,8 @@ yum install centreon-plugin-Cloud-Aws-Directconnect-Api | CRITICALCONNECTIONPACKETSEGRESS | Threshold | | | | WARNINGCONNECTIONPACKETSINGRESS | Threshold | | | | CRITICALCONNECTIONPACKETSINGRESS | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -265,8 +265,8 @@ yum install centreon-plugin-Cloud-Aws-Directconnect-Api | TIMEFRAME | Set timeframe in seconds | 600 | | | PERIOD | Set period in seconds | 60 | | | FILTERVIRTUALINTERFACEID | Filter virtual interface ID (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | | | WARNINGVIRTUALINTERFACEEGRESS | Threshold | | | | CRITICALVIRTUALINTERFACEEGRESS | Threshold | | | | WARNINGVIRTUALINTERFACEINGRESS | Threshold | | | @@ -382,7 +382,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -436,8 +436,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-connection-id | Filter connection ID (can be a regexp). | | --filter-metric | Filter metrics (can be: 'ConnectionBpsEgress', 'ConnectionBpsIngress', 'ConnectionPpsEgress', 'ConnectionPpsIngress', 'ConnectionLightLevelTx', 'ConnectionLightLevelRx') (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | --warning-* --critical-* | Thresholds. Can be 'connection-egress', 'connection-ingress', 'connection-packets-egress', 'connection-packets-ingress', 'connection-ligh-level-outbound', 'connection-ligh-level-inbound. | @@ -448,8 +448,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-connection-id | Filter connection ID (can be a regexp). | | --filter-virtual-interface-id | Filter virtual interface ID (can be a regexp). | | --filter-metric | Filter metrics (can be: 'VirtualInterfaceBpsEgress', 'VirtualInterfaceBpsIngress', 'VirtualInterfacePpsEgress', 'VirtualInterfacePpsIngress') (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | --warning-* --critical-* | Thresholds. Can be 'virtual-interface-egress', 'virtual-interface-ingress', 'virtual-interface-packets-egress', 'virtual-interface-packets-ingress'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ebs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ebs.md index 68a0ef69741c..7de783c9de16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ebs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ebs.md @@ -368,7 +368,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ec2.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ec2.md index 11f9db1fca9d..f09bdf5aec7a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ec2.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ec2.md @@ -395,8 +395,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | FILTERASG | Filter by autoscaling group name (can be a regexp) | .* | | | WARNINGCOUNT | Warning threshold about number of instances in the autoscaling group | | | | CRITICALCOUNT | Critical threshold about number of instances in the autoscaling group | | | -| CRITICALINSTANCES | Set critical threshold for instances states (Default: '%{health} =~ /Healthy/ && %{lifecycle} !~ /InService/'). Can use special variables like: %{health}, %{lifecycle} | %{health} =~ /Healthy/ && %{lifecycle} !~ /InService/ | | -| WARNINGINSTANCES | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %{health}, %{lifecycle} | | | +| CRITICALINSTANCES | Set critical threshold for instances states (Default: '%\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/'). Can use special variables like: %\{health\}, %\{lifecycle\} | %\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/ | | +| WARNINGINSTANCES | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %\{health\}, %\{lifecycle\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -472,8 +472,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | CRITICALRUNNING | Thresholds | | | | WARNINGSHUTTINGDOWN | Thresholds | | | | CRITICALSHUTTINGDOWN | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGSTOPPED | Thresholds | | | | CRITICALSTOPPED | Thresholds | | | | WARNINGSTOPPING | Thresholds | | | @@ -515,8 +515,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. 'status' can be: 'passed', 'failed' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /failed/i'). You can use the following variables: %{status}. 'status' can be: 'passed', 'failed' | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed' | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -642,7 +642,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -727,8 +727,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Possible values: asg / instances | | --filter-asg | Filter by autoscaling group name (can be a regexp). | -| --warning-instances | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %{health}, %{lifecycle} | -| --critical-instances | Set critical threshold for instances states (Default: '%{health} =~ /Healthy/ && %{lifecycle} !~ /InService/'). Can use special variables like: %{health}, %{lifecycle} | +| --warning-instances | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %\{health\}, %\{lifecycle\} | +| --critical-instances | Set critical threshold for instances states (Default: '%\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/'). Can use special variables like: %\{health\}, %\{lifecycle\} | | --warning-asg-instance-current | Warning threshold about number of instances in the autoscaling group | | --critical-asg-instance-current | Critical threshold about number of instances in the autoscaling group | @@ -773,8 +773,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-instanceid | Filter by instance id (can be a regexp). | | --add-uptime | Monitor instances uptime. | | --uptime-unit | Select the unit for uptime threshold. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'pending', 'running', 'shuttingdown', 'terminated', 'stopping', 'stopped', 'uptime'. | @@ -805,8 +805,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --type | Set the instance type (Required) (Can be: 'asg', 'instance'). | | --name | Set the instance name (Required) (can be defined multipletimes). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. 'status' can be: 'passed', 'failed'. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /failed/i'). You can use the following variables: %{status}. 'status' can be: 'passed', 'failed'. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed'. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-efs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-efs.md index 482bf98e40ff..2625adc532c7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-efs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-efs.md @@ -360,7 +360,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elasticache.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elasticache.md index 82dd95896ae6..b2b2fa128daa 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elasticache.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elasticache.md @@ -612,7 +612,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elb.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elb.md index 04fa226b21b7..f0fef784e886 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elb.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-elb.md @@ -580,7 +580,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-fsx.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-fsx.md index f01445426753..b71455ec318e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-fsx.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-fsx.md @@ -359,7 +359,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-kinesis.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-kinesis.md index 9c3fafc89927..84cf112cf8c0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-kinesis.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-kinesis.md @@ -353,7 +353,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-lambda.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-lambda.md index b8c83f5c7e7a..c7c9e0a73ac6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-lambda.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-lambda.md @@ -333,7 +333,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-rds.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-rds.md index 8b8454509f02..2a322df1d6bf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-rds.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-rds.md @@ -617,8 +617,8 @@ yum install centreon-plugin-Cloud-Aws-Rds-Api | AWSCUSTOMMODE | | awscli | | | AWSREGION | | | X | | FILTERINSTANCEID | Filter by instance id (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGTOTALAVAILABLE | Warning threshold | | | | CRITICALTOTALAVAILABLE | Critical threshold | | | | WARNINGTOTALBACKINGUP | Warning threshold | | | @@ -874,7 +874,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -996,8 +996,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^total-available$' | | --filter-instanceid | Filter by instance id (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'total-available', 'total-backing-up', 'total-failed', 'total-maintenance', 'total-stopped', 'total-storage-full'. | | --critical-* | Critical threshold. Can be: 'total-available', 'total-backing-up', 'total-failed', 'total-maintenance', 'total-stopped', 'total-storage-full'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-s3.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-s3.md index 7b33c7440a35..3141afc70415 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-s3.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-s3.md @@ -378,7 +378,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ses.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ses.md index 039bad1cc328..0f2ce95d52cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ses.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-ses.md @@ -302,7 +302,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sns.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sns.md index 0a62a0ee133c..ac43624bc413 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sns.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sns.md @@ -321,7 +321,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sqs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sqs.md index 64b93c89f82f..58049b223fbd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sqs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-sqs.md @@ -341,7 +341,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md index bacee14f63a6..6dbb0b53ddce 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md @@ -340,7 +340,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-vpn.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-vpn.md index 41a0639f3ce7..0eadf585e5b1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-vpn.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-aws-vpn.md @@ -353,7 +353,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md index b084c9e4212d..a5af4d10a6f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md @@ -167,7 +167,7 @@ dans Centreon. Afin d'utiliser le custom-mode 'azcli', installez le binaire associé sur tous les Collecteurs Centreon devant superviser des resources Azure: -- La CLI requiert une version de Python >= 2.7 () +- La CLI requiert une version de Python >= 2.7 (\) Sur un système utilisant le packaging RPM, utilisez les commandes ci-dessous avec l'utilisateur *root* ou un utilisateur avec les droits 'sudo' adéquats: @@ -191,7 +191,7 @@ La commande retourne le message ci-dessous contenant un code: *To sign in, use a web browser to open the page https://microsoft.com/devicelogin* *and enter the code CWT4WQZAD to authenticate.* -Rendez-vous sur afin de saisir le code obtenu, puis connectez vous avec le compte de service dédié à la supervision. +Rendez-vous sur \ afin de saisir le code obtenu, puis connectez vous avec le compte de service dédié à la supervision. Une fois ces actions effectuées, des informations d'auhtentification de la forme suivante devraient s'afficher dans le terminal du collecteur Centreon: diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md index 0cbb777b7f19..f1a9ba75f4c4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md @@ -316,10 +316,10 @@ yum install centreon-plugin-Cloud-Azure-Compute-Aks-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| STATUSOK | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| STATUSOK | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -515,7 +515,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -632,10 +632,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md index 06f6cbfcb7ba..5eac608180e6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md @@ -423,10 +423,10 @@ yum install centreon-plugin-Cloud-Azure-Compute-Functions-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (Default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (Default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -655,7 +655,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -810,10 +810,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %{status}, %{summary}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary}. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary}. | -| --ok-status | Define the conditions to match for the status to be OK (Default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %\{status\}, %\{summary\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --ok-status | Define the conditions to match for the status to be OK (Default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md index 9d54d7465fea..87628bfbd2fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md @@ -197,10 +197,10 @@ l'utilisateur **centreon-engine** (`su - centreon-engine`) : --client-id='xxxxxxxxx' \ --client-secret='xxxxxxxxx' \ --proxyurl='' \ - --ok-status='%{status} =~ /^Available$/' \ + --ok-status='%\{status\} =~ /^Available$/' \ --warning-status='' \ - --critical-status='%{status} =~ /^Unavailable$/' \ - --unknown-status='%{status} =~ /^Unknown$/' \ + --critical-status='%\{status\} =~ /^Unavailable$/' \ + --unknown-status='%\{status\} =~ /^Unknown$/' \ --api-version=2017-07-01\ --use-new-perfdata ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md index 6474807f123e..5b7b659d9a2b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md @@ -325,10 +325,10 @@ yum install centreon-plugin-Cloud-Azure-Database-CosmosDb-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -507,7 +507,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -632,10 +632,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md index 4e675d8f2af0..b83bf2dc26f4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md @@ -458,7 +458,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md index 3817ed5b8d02..5fafef0d5a63 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md @@ -483,7 +483,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md index 442e2e99a34c..d7b609f036b0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md @@ -531,7 +531,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md index b3993de265dd..56ef2f8891d2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md @@ -462,7 +462,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-redis.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-redis.md index 0bdcebb158bc..36351a74ffd2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-redis.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-redis.md @@ -373,10 +373,10 @@ yum install centreon-plugin-Cloud-Azure-Database-Redis-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -535,7 +535,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -690,10 +690,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md index 4b85db6d7f31..814fbb2726dd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md @@ -331,10 +331,10 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlDatabase-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| STATUSOK | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | | | -| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| STATUSOK | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | | | +| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -487,7 +487,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -625,10 +625,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md index bd5399b1edfa..0551c6a74761 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md @@ -274,10 +274,10 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlManagedInstance-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -406,7 +406,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -521,10 +521,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %{status}, %{summary}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary}. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary}. | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %\{status\}, %\{summary\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md index c7c8834aae6f..ae5b9e83006a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md @@ -209,8 +209,8 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlServer-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "Ready"'). You can use the following variables: %{state}, %{fqdn}, %{display} | %{state} ne "Ready" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{fqdn}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "Ready"'). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | %\{state\} ne "Ready" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -240,7 +240,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --location='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{state} ne "Ready"' + --critical-status='%\{state\} ne "Ready"' ``` La commande devrait retourner un message de sortie similaire à : @@ -378,7 +378,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -400,8 +400,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --resource-group | Set resource group. | | --location | Set resource location. | | --filter-name | Filter server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{fqdn}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "Ready"'). You can use the following variables: %{state}, %{fqdn}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "Ready"'). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md index 2c63857058cc..5f8927d5ad7f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md @@ -329,7 +329,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-costs.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-costs.md index 1b9c8d524941..b6b78d0f496b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-costs.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-costs.md @@ -406,7 +406,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md index a7ee2dfd5ffc..d9fcf4a1b5f9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md @@ -306,7 +306,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md index f1b04b23174e..dda0bfe0f651 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md @@ -157,7 +157,7 @@ l'utilisateur **centreon-engine** (`su - centreon-engine`) : --proxyurl='' \ --vault-name='vault123' \ --warning-status='' \ - --critical-status='%{status} eq "Failed"' \ + --critical-status='%\{status\} eq "Failed"' \ --warning-total-completed='' \ --critical-total-completed='' \ --warning-total-failed='' \ diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-resource.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-resource.md index 739c7acafd2d..8773b6957aa8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-resource.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-management-resource.md @@ -32,7 +32,7 @@ The login and access token handling will be made by the plugin itself. ### Azure CLI 2.0 (for 'azcli' custom mode) The CLI needs at least Python version 2.7 -(). +(\). On CentOS/RedHat, install with following commands: @@ -47,7 +47,7 @@ The shell should prompt: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code CWT4WQZAD to authenticate. -Go to and enter the given code. +Go to \ and enter the given code. Log in with your account credentials. You should use a service account. Application is not yet supported. @@ -55,18 +55,18 @@ Application is not yet supported. The command line should now show: [ - { + \{ "cloudName": "AzureCloud", "id": "0ef83f3a-d83e-2039-d930-309df93acd93d", "isDefault": true, "name": "N/A(tenant level account)", "state": "Enabled", "tenantId": "0ef83f3a-03cd-2039-d930-90fd39ecd048", - "user": { + "user": \{ "name": "email@mycompany.onmicrosoft.com", "type": "user" - } - } + \} + \} ] You now have a hidden azure directory where your token is stored in an @@ -121,5 +121,5 @@ Click on the *Save* button. ## Available metrics Go to - +\ to see the description of return metrics for this Azure service. diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md index 7c73633ebfef..662bb42ac3cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md @@ -32,7 +32,7 @@ The login and access token handling will be made by the plugin itself. ### Azure CLI 2.0 (for 'azcli' custom mode) The CLI needs at least Python version 2.7 -(). +(\). On CentOS/RedHat, install with following commands: @@ -47,7 +47,7 @@ The shell should prompt: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code CWT4WQZAD to authenticate. -Go to and enter the given code. +Go to \ and enter the given code. Log in with your account credentials. You should use a service account. Application is not yet supported. @@ -55,18 +55,18 @@ Application is not yet supported. The command line should now show: [ - { + \{ "cloudName": "AzureCloud", "id": "0ef83f3a-d83e-2039-d930-309df93acd93d", "isDefault": true, "name": "N/A(tenant level account)", "state": "Enabled", "tenantId": "0ef83f3a-03cd-2039-d930-90fd39ecd048", - "user": { + "user": \{ "name": "email@mycompany.onmicrosoft.com", "type": "user" - } - } + \} + \} ] You now have a hidden azure directory where your token is stored in an @@ -123,5 +123,5 @@ Click on the *Save* button. ## Available metrics Go to - +\ to see the description of return metrics for this Azure service. diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md index 45f22ef6cd52..cb93732d489a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md @@ -147,8 +147,8 @@ commande depuis votre collecteur Centreon en vous connectant avec l'utilisateur --resource='IPA001ABCD' \ --timeframe='900' \ --interval='PT5M' \ - --critical-provisioning-state='%{state} =~ /Failed/i' \ - --critical-ddos-status='%{status} =~ /DDOS Attack ongoing/i' + --critical-provisioning-state='%\{state\} =~ /Failed/i' \ + --critical-ddos-status='%\{status\} =~ /DDOS Attack ongoing/i' ``` La commande devrait retourner un message de sortie similaire à: diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md index 47618d5d0e6a..69dca2e4fc1f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md @@ -142,7 +142,7 @@ l'utilisateur **centreon-engine** (`su - centreon-engine`) : --proxyurl='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{peering_state} ne "Connected" || %{provisioning_state} ne "Succeeded"' \ + --critical-status='%\{peering_state\} ne "Connected" || %\{provisioning_state\} ne "Succeeded"' \ --use-new-perfdata ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md index a6c944e95b0b..c4d73ff3226d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md @@ -174,10 +174,10 @@ l'utilisateur **centreon-engine** (`su - centreon-engine`) : --client-id='' \ --client-secret='' \ --proxyurl='' \ - --ok-status='%{status} =~ /^Available$/' \ + --ok-status='%\{status\} =~ /^Available$/' \ --warning-status='' \ - --critical-status='%{status} =~ /^Unavailable$/' \ - --unknown-status='%{status} =~ /^Unknown$/' \ + --critical-status='%\{status\} =~ /^Unavailable$/' \ + --unknown-status='%\{status\} =~ /^Unknown$/' \ --api-version=2017-07-01\ ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md index 3358e1fb52f0..b67fd1914dc8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md @@ -169,7 +169,7 @@ Une fois le modèle appliqué, les macros ci-dessous indiquées comme requises ( | | RESOURCELOCATION | Set resource location (Optional) | | | | RESOURCETYPE | Set resource type (Optional) | | | | POLICYNAME | Set policy name (Optional) | | -| | CRITICALCOMPLIANCESTATE | | %{compliance_state} eq "NonCompliant" | +| | CRITICALCOMPLIANCESTATE | | %\{compliance_state\} eq "NonCompliant" | | | WARNINGCOMPLIANCESTATE | | | | | WARNINGNONCOMPLIANTPOLICIES | | | | | CRITICALNONCOMPLIANTPOLICIES | | | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-cadvisor-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-cadvisor-api.md index d389554955c1..e95a83c5606a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-cadvisor-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-cadvisor-api.md @@ -387,7 +387,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-kubernetes-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-kubernetes-api.md index b3839dee5b7d..29e4a3ab85eb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-kubernetes-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-kubernetes-api.md @@ -1039,8 +1039,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERTYPE | Filter event type (can be a regexp) | .* | | | FILTERNAMESPACE | Filter namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{type} =~ /warning/i') Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen} | %{type} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} =~ /error/i'). Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen} | %{type} =~ /error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{type\} =~ /warning/i') Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\} | %\{type\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} =~ /error/i'). Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\} | %\{type\} =~ /error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1050,8 +1050,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERCRONJOB | Filter CronJob name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter CronJob namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1061,8 +1061,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERDAEMONSET | Filter DaemonSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter DaemonSet namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{up_to_date\}\< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1072,8 +1072,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:-----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERDEPLOYMENT | Filter deployment name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter deployment namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}| %\{up_to_date\}\< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1081,8 +1081,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '(%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i)'). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name} | (%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i) | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '(%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i)'). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\} | (%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i) | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1109,8 +1109,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| | FILTERPERSISTENTVOLUME | Filter persistent volume name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter persistent volume name (can be a regexp). | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Bound\|Available\|Released/i'). You can use the following variables: %{name}, %{phase} | %{phase} !~ /Bound\|Available\|Released/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{phase} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Bound\|Available\|Released/i'). You can use the following variables: %\{name\}, %\{phase\} | %\{phase\} !~ /Bound\|Available\|Released/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{phase\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1123,10 +1123,10 @@ yum install centreon-plugin-Cloud-Kubernetes-Api | UNITS | Units of thresholds (default: '%') ('%', 'count') | % | | | WARNINGCONTAINERSREADY | Warning threshold | | | | CRITICALCONTAINERSREADY | Critical threshold | | | -| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i \|\| %{state} !~ /^ready$/'). You can use the following variables: %{status}, %{state}, %{name} | %{status} !~ /running/i \|\| %{state} !~ /^ready$/ | | -| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name} | | | -| CRITICALPODSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name}, %{namespace} | %{status} !~ /running/i | | -| WARNINGPODSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}, %{namespace} | | | +| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/'). You can use the following variables: %\{status\}, %\{state\}, %\{name\} | %\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/ | | +| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALPODSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\} | %\{status\} !~ /running/i | | +| WARNINGPODSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\} | | | | WARNINGRESTARTSCOUNT | Warning threshold | | | | CRITICALRESTARTSCOUNT | Critical threshold | | | | WARNINGTOTALRESTARTSCOUNT | Warning threshold | | | @@ -1140,8 +1140,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERREPLICATSET | Filter ReplicaSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter ReplicaSet namespace (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | %{ready} \< %{desired} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | %\{ready\} \< %\{desired\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1151,8 +1151,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERREPLICATIONCONTROLLER | Filter ReplicationController name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter ReplicationController namespace (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | %{ready} \< %{desired} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | %\{ready\} \< %\{desired\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1162,8 +1162,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERSTATEFULSET | Filter StatefulSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter StatefulSet namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready} | %{ready} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\} | %\{up_to_date\}\< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\} | %\{ready\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -1194,8 +1194,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --timeout='10' \ --filter-name='.*' \ --filter-namespace='.*' \ - --warning-status='%{up_to_date} < %{desired}' \ - --critical-status='%{ready} < %{desired}' \ + --warning-status='%\{up_to_date\} < %\{desired\}' \ + --critical-status='%\{ready\} < %\{desired\}' \ --verbose ``` @@ -1305,7 +1305,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1387,8 +1387,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --command-options | Command options (default: none). | | --filter-type | Filter event type (can be a regexp). | | --filter-namespace | Filter namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{type} =~ /warning/i') Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} =~ /error/i'). Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{type\} =~ /warning/i') Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} =~ /error/i'). Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\}. | @@ -1397,8 +1397,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter CronJob name (can be a regexp). | | --filter-namespace | Filter CronJob namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\}. | @@ -1407,8 +1407,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter DaemonSet name (can be a regexp). | | --filter-namespace | Filter DaemonSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\}. | @@ -1417,8 +1417,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter deployment name (can be a regexp). | | --filter-namespace | Filter deployment namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}. | @@ -1426,8 +1426,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter node name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '(%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i)'). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '(%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i)'). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\}. | @@ -1443,8 +1443,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter persistent volume name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{phase}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Bound\|Available\|Released/i'). You can use the following variables: %{name}, %{phase}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{phase\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Bound\|Available\|Released/i'). You can use the following variables: %\{name\}, %\{phase\}. | @@ -1454,10 +1454,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter pod name (can be a regexp). | | --filter-namespace | Filter pod namespace (can be a regexp). | | --extra-filter | Add an extra filter based on labels (can be defined multiple times) Example : --extra-filter='app=mynewapp' | -| --warning-pod-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}, %{namespace}. | -| --critical-pod-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name}, %{namespace}. | -| --warning-container-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}. | -| --critical-container-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i \|\| %{state} !~ /^ready$/'). You can use the following variables: %{status}, %{state}, %{name}. | +| --warning-pod-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\}. | +| --critical-pod-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\}. | +| --warning-container-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}. | +| --critical-container-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/'). You can use the following variables: %\{status\}, %\{state\}, %\{name\}. | | --warning-* | Warning threshold. Can be: 'containers-ready', 'total-restarts-count' (count), 'restarts-count' (count). | | --critical-* | Critical threshold. Can be: 'containers-ready', 'total-restarts-count' (count), 'restarts-count' (count). | | --units | Units of thresholds (default: '%') ('%', 'count'). | @@ -1469,8 +1469,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ReplicaSet name (can be a regexp). | | --filter-namespace | Filter ReplicaSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | @@ -1479,8 +1479,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ReplicationController name (can be a regexp). | | --filter-namespace | Filter ReplicationController namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | @@ -1489,8 +1489,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter StatefulSet name (can be a regexp). | | --filter-namespace | Filter StatefulSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md index ac322f1762fd..fe75347592a0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md @@ -242,8 +242,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Exchange-Api | CRITICALACTIVEMAILBOXES | Critical threshold | | | | WARNINGITEMS | Warning threshold | | | | CRITICALITEMS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | %{used} \> %{issue\_warning\_quota} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | %{used} \> %{prohibit\_send\_quota} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | %\{used\} \> %\{issue_warning_quota\}| | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | %\{used\} \> %\{prohibit_send_quota\}| | | WARNINGTOTALUSAGEACTIVE | Warning threshold | | | | CRITICALTOTALUSAGEACTIVE | Critical threshold | | | | WARNINGTOTALUSAGEINACTIVE | Warning threshold | | | @@ -343,7 +343,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -411,8 +411,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-mailbox | Filter mailboxes. | | --warning-* | Warning threshold. Can be: 'active-mailboxes', 'total-usage-active' (count), 'total-usage-inactive' (count). | | --critical-* | Critical threshold. Can be: 'active-mailboxes', 'total-usage-active' (count), 'total-usage-inactive' (count). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{used} \> %{issue\_warning\_quota}'). You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{used} \> %{prohibit\_send\_quota}'). You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{used\} \> %\{issue_warning_quota\}'). You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{used\} \> %\{prohibit_send_quota\}'). You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | | --filter-counters | Only display some counters (regexp can be used). Example to hide per user counters: --filter-counters='active\|total' (default: 'active\|total') | | --units | Unit of thresholds (default: '%') ('%', 'count'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md index 8288d8e2efd6..a1d2ac2b4864 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md @@ -280,12 +280,12 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | FILTERAPPNAME | Filter applications (can be a regexp) | | | | WARNINGKEYEXPIRES | Thresholds | | | | CRITICALKEYEXPIRES | Thresholds | | | -| CRITICALKEYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name} | %{status} =~ /expired/i | | -| WARNINGKEYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name} | | | +| CRITICALKEYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | %\{status\} =~ /expired/i | | +| WARNINGKEYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | | | | WARNINGPASSWORDEXPIRES | Thresholds | | | | CRITICALPASSWORDEXPIRES | Thresholds | | | -| CRITICALPASSWORDSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name} | %{status} =~ /expired/i | | -| WARNINGPASSWORDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name} | | | +| CRITICALPASSWORDSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | %\{status\} =~ /expired/i | | +| WARNINGPASSWORDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -294,8 +294,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERSERVICENAME | Filter services (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %{service\_name}, %{status}, %{classification} | %{status} !~ /serviceOperational\|serviceRestored/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{service\_name}, %{status}, %{classification} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | %\{status\} !~ /serviceOperational\|serviceRestored/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -304,8 +304,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERSKUPARTNUMBER | Filter subscriptions by SKU part number (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | %{capabilityStatus} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | %\{capabilityStatus\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | | | | WARNINGSUBSCRIPTIONUSAGE | Thresholds | | | | CRITICALSUBSCRIPTIONUSAGE | Thresholds | | | | WARNINGSUBSCRIPTIONUSAGEFREE | Thresholds | | | @@ -335,7 +335,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --client-id='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxx' \ --client-secret='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' \ --filter-sku-part-number='' \ - --warning-status='%{capabilityStatus} =~ /warning/i' \ + --warning-status='%\{capabilityStatus\} =~ /warning/i' \ --critical-status='' \ --warning-subscription-usage='' \ --critical-subscription-usage='' \ @@ -403,7 +403,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -458,10 +458,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-app-name | Filter applications (can be a regexp). | -| --warning-key-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --critical-key-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --warning-password-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --critical-password-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name}. | +| --warning-key-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --critical-key-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --warning-password-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --critical-password-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | | --unit | Select the time unit for the expiration thresholds. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is secondss. | | --warning-* --critical-* | Thresholds. Can be: 'key-expires', 'password-expires'. | @@ -471,8 +471,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-service-name | Filter services (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{service\_name}, %{status}, %{classification} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %{service\_name}, %{status}, %{classification} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | @@ -480,8 +480,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-sku-part-number | Filter subscriptions by SKU part number (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | | --warning-* --critical-* | Thresholds. Can be: 'subscription-usage', 'subscription-usage-free', 'subscription-usage-prct'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md index 2cb60b722558..872e941a284f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md @@ -325,7 +325,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md index 866d0abff3e7..02cc83d7fab0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md @@ -395,7 +395,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md index 92da21748b48..c2d6973c9bfe 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md @@ -345,7 +345,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md index 098d56762649..daece5d092b0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md @@ -355,7 +355,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-api.md index cc89e8f97b61..083d04e78484 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-api.md @@ -166,7 +166,7 @@ Une fois le Plugin installé, connectez-vous au Collecteur Centreon et utilisez --hostname=amzprometheus.int.centreon.com \ --url-path='/api/v1' --port='9090' --proto='http' \ --filter-label='job,coredns' \ - --warning-status='' --critical-status='%{health} !~ /up/' + --warning-status='' --critical-status='%\{health\} !~ /up/' ``` La commande devrait retourner un message de sortie similaire à : @@ -220,9 +220,9 @@ Voici un exemple pour illustrer comment le mode *Expression* fonctionne : --hostname=amzprometheus.int.centreon.com \ --url-path='/api/v1' --port='9090' --proto='http' \ --query='cpu_requests,sum by (node) (kube_pod_container_resource_requests_cpu_cores) / sum by (node) (kube_node_status_capacity_cpu_cores) * 100' \ - --output='%{instance} CPU Requests: %{cpu_requests}%' --multiple-output='Nodes CPU Requests within bounds' \ + --output='%\{instance\} CPU Requests: %\{cpu_requests\}%' --multiple-output='Nodes CPU Requests within bounds' \ --instance='node' \ - --warning-status='%{cpu_requests} > 60' --critical-status='%{cpu_requests} > 70' \ + --warning-status='%\{cpu_requests\} > 60' --critical-status='%\{cpu_requests\} > 70' \ --use-new-perfdata --verbose ``` @@ -288,25 +288,25 @@ Voici un résumé des macros à définir au niveau du Service: | INSTANCE | node | | OUTPUT | URL Path to reach API (Default: '/api/v1) | | MULTIPLEOUTPUT | Nodes CPU Requests within bounds | -| WARNINGSTATUS | %{cpu_requests} > 60 | -| CRITICALSTATUS | %{cpu_requests} > 70 | +| WARNINGSTATUS | %\{cpu_requests\} > 60 | +| CRITICALSTATUS | %\{cpu_requests\} > 70 | | EXTRAOPTIONS | --verbose --use-new-perfdata | ## Troubleshooting -### UNKNOWN: 500 Can't connect to amzprometheus.int.centreon.com:9090 () | Lorsque cette erreur est renvoyée, vérifier que les informations pour contacter le serveur Prometheus sont correctes (Port, Nom d'Hôte) et que la connexion est possible. -Le contenu de la balise donne des indications supplémentaires sur la +Le contenu de la balise \ donne des indications supplémentaires sur la cause du dysfonctionnement. ### UNKNOWN: 400 Bad Request | La requête PromQL contient probablement une erreur de syntaxe. Il est nécessaire -de valider son fonctionnement dans l'interface Prometheus. +de valider son fonctionnement dans l'interface Prometheus. ### Diagnostic des erreurs communes diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md index 17fc040e7991..9f0e75262b4a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md @@ -207,8 +207,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | POD | Filter on a specific pod (must be a PromQL filter, Default:'pod=~".*"') | pod=~".*" | | | WARNINGRESTARTSCOUNT | Warning threshold for container restarts count | | | | CRITICALRESTARTSCOUNT | Critical threshold for container restarts count | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/ \|\| %{state} !~ /ready/'). You can use the following variables: %{status}, %{state}, %{reason} | %{status} !~ /running/ \|\| %{state} !~ /ready/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{status}, %{state}, %{reason} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/ \|\| %\{state\} !~ /ready/'). You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | %\{status\} !~ /running/ \|\| %\{state\} !~ /ready/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -217,8 +217,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | DAEMONSET | Filter on a specific daemonset (must be a PromQL filter, Default: 'daemonset=~".*"') | daemonset=~".*" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{up_to_date\}\< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -227,8 +227,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | DEPLOYMENT | Filter on a specific deployment (must be a PromQL filter, Default: 'deployment=~".*"') | deployment=~".*" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}| %\{up_to_date\}\< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -238,8 +238,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | NAMESPACE | Filter on a specific namespace (must be a PromQL filter, Default: 'namespace=~".*"') | namespace=~".*" | | | PHASE | Filter on a specific phase (must be a PromQL filter, Default:'phase=~".*"') | phase=~".*" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Active/'). You can use the following variables: %{display}, %{phase} | %{phase} !~ /Active/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{phase} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Active/'). You can use the following variables: %\{display\}, %\{phase\} | %\{phase\} !~ /Active/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{phase\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -251,8 +251,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | UNITS | Units of thresholds (default: '') (can be '%') | | | | WARNINGALLOCATEDPODS | Warning threshold for pods allocation | | | | CRITICALALLOCATEDPODS | Critical threshold for pods allocation | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Ready/ \|\| %{schedulable} != /false/'). You can use the following variables: %{display}, %{status}, %{schedulable} | %{status} !~ /Ready/ \|\| %{schedulable} =~ /false/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{status}, %{schedulable} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Ready/ \|\| %\{schedulable\} != /false/'). You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | %\{status\} !~ /Ready/ \|\| %\{schedulable\} =~ /false/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -278,7 +278,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --proto='http' \ --node='node=~".*"' \ --warning-status='' \ - --critical-status='%{status} !~ /Ready/ || %{schedulable} =~ /false/' \ + --critical-status='%\{status\} !~ /Ready/ || %\{schedulable\} =~ /false/' \ --warning-allocated-pods='' \ --critical-allocated-pods='' \ --units='' \ @@ -348,7 +348,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -398,8 +398,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --container | Filter on a specific container (must be a PromQL filter, Default: 'container=~".*"') | | --pod | Filter on a specific pod (must be a PromQL filter, Default:'pod=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{status}, %{state}, %{reason} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/ \|\| %{state} !~ /ready/'). You can use the following variables: %{status}, %{state}, %{reason} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/ \|\| %\{state\} !~ /ready/'). You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | | --warning-restarts-count | Warning threshold for container restarts count. | | --critical-restarts-count | Critical threshold for container restarts count. | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | @@ -412,8 +412,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --daemonset | Filter on a specific daemonset (must be a PromQL filter, Default: 'daemonset=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - desired: ^kube\_daemonset\_status\_desired\_number\_scheduled$ - current: ^kube\_daemonset\_status\_current\_number\_scheduled$ - available: ^kube\_daemonset\_status\_number\_available$ - unavailable: ^kube\_daemonset\_status\_number\_unavailable$ - up\_to\_date: ^kube\_daemonset\_updated\_number\_scheduled$ - ready: ^kube\_daemonset\_status\_number\_ready$ - misscheduled: ^kube\_daemonset\_status\_number\_misscheduled$ | @@ -423,8 +423,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --deployment | Filter on a specific deployment (must be a PromQL filter, Default: 'deployment=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\}\< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - desired: ^kube\_deployment\_spec\_replicas$ - current: ^kube\_deployment\_status\_replicas$ - available: ^kube\_deployment\_status\_replicas\_available$ - unavailable: ^kube\_deployment\_status\_replicas\_unavailable$ - up\_to\_date: ^kube\_deployment\_status\_replicas\_updated$ | @@ -435,8 +435,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --namespace | Filter on a specific namespace (must be a PromQL filter, Default: 'namespace=~".*"') | | --phase | Filter on a specific phase (must be a PromQL filter, Default:'phase=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{phase}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Active/'). You can use the following variables: %{display}, %{phase} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{phase\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Active/'). You can use the following variables: %\{display\}, %\{phase\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - status: ^kube\_namespace\_status\_phase$ | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | @@ -447,8 +447,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --node | Filter on a specific node (must be a PromQL filter, Default:'node=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{status}, %{schedulable} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Ready/ \|\| %{schedulable} != /false/'). You can use the following variables: %{display}, %{status}, %{schedulable} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Ready/ \|\| %\{schedulable\} != /false/'). You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | | --warning-allocated-pods | Warning threshold for pods allocation. | | --critical-allocated-pods | Critical threshold for pods allocation. | | --units | Units of thresholds (default: '') (can be '%'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md index 8cf930dd72e5..df244a23c611 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md @@ -324,9 +324,9 @@ yum install centreon-plugin-Cloud-Vmware-Velocloud-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{edge\_state} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | %{edge\_state} =~ /NEVER\_ACTIVATED/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | %{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{edge_state\} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | %\{edge_state\} =~ /NEVER\_ACTIVATED/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | %\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -335,11 +335,11 @@ yum install centreon-plugin-Cloud-Vmware-Velocloud-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERLINKNAME | Filter links based on their name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{vpn\_state}, %{backup\_state} | | | -| WARNINGEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | -| CRITICALEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | -| CRITICALSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | %{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/ | | -| WARNINGSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{vpn_state\}, %\{backup_state\} | | | +| WARNINGEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | +| CRITICALEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | +| CRITICALSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | %\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/ | | +| WARNINGSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -487,7 +487,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -573,9 +573,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter edge by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{edge\_state} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{edge_state\} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | @@ -584,8 +584,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-edge-name | Filter edge by name (can be a regexp). | | --filter-link-name | Filter link by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{vpn\_state}, %{backup\_state}. | -| --warning-* --critical-* | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/'). | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{vpn_state\}, %\{backup_state\}. | +| --warning-* --critical-* | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-apc.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-apc.md index 9e4a9a04efad..eb04e6f7cd06 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-apc.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-apc.md @@ -213,8 +213,8 @@ yum install centreon-plugin-Hardware-Ats-Apc-Snmp | CRITICALLOADCAPACITY | Critical threshold | | | | WARNINGPOWER | Warning threshold | | | | CRITICALPOWER | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nearoverload/'). You can use the following variables: %{status}, %{display} | %{status} =~ /nearoverload/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(lowload\|overload)$/'). You can use the following variables: %{status}, %{display} | %{status} =~ /^(lowload\|overload)$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nearoverload/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /nearoverload/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(lowload\|overload)$/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /^(lowload\|overload)$/ | | | WARNINGVOLTAGE | Warning threshold | | | | CRITICALVOLTAGE | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -302,7 +302,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,8 +378,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^power$' | | --warning-* | Warning threshold. Can be: 'voltage', 'current', 'power', 'load', 'load-capacity'. | | --critical-* | Critical threshold. Can be: 'voltage', 'current', 'power', 'load', 'load-capacity'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nearoverload/'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(lowload\|overload)$/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nearoverload/'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(lowload\|overload)$/'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md index 646a69ce92cb..171438843be7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md @@ -221,7 +221,7 @@ yum install centreon-plugin-Hardware-Ats-Eaton-Snmp | UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: operation\_mode | | | | WARNINGHUMIDITY | Warning threshold | | | | CRITICALHUMIDITY | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{operation\_mode} !~ /source1\|source2/i'). You can use the following variables: %{operation\_mode} | %{operation\_mode} !~ /source1\|source2/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{operation_mode\} !~ /source1\|source2/i'). You can use the following variables: %\{operation_mode\} | %\{operation_mode\} !~ /source1\|source2/i | | | WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: operation\_mode | | | | WARNINGTEMPERATURE | Warning threshold | | | | CRITICALTEMPERATURE | Critical threshold | | | @@ -305,7 +305,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,7 +378,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: operation\_mode | | --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: operation\_mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{operation\_mode} !~ /source1\|source2/i'). You can use the following variables: %{operation\_mode} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{operation_mode\} !~ /source1\|source2/i'). You can use the following variables: %\{operation_mode\} | | --warning-* | Warning threshold. Can be: 'temperature', 'humidity'. | | --critical-* | Critical threshold. Can be: 'temperature', 'humidity'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md index 18c52ac9e74b..e4078113957c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md @@ -210,10 +210,10 @@ yum install centreon-plugin-Hardware-Devices-Gorgy-Ntpserver-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------|:-----------:| -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{sync\_status} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %{sync\_status} | %{sync\_status} =~ /Running with autonomy\|Free running/i | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %{sync\_status} | %{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i | | -| WARNINGTIMEBASESTATUS | Define the conditions to match for the status to be WARNING (Default: '%{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %{timebase\_status} | %{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i | | -| CRITICALTIMEBASESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{timebase\_status} =~ /^XO$/i'). You can use the following variables: %{timebase\_status} | %{timebase\_status} =~ /^XO$/i | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{sync_status\} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %\{sync_status\} | %\{sync_status\} =~ /Running with autonomy\|Free running/i | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %\{sync_status\} | %\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i | | +| WARNINGTIMEBASESTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %\{timebase_status\} | %\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i | | +| CRITICALTIMEBASESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{timebase_status\} =~ /^XO$/i'). You can use the following variables: %\{timebase_status\} | %\{timebase_status\} =~ /^XO$/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -226,7 +226,7 @@ yum install centreon-plugin-Hardware-Devices-Gorgy-Ntpserver-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -313,7 +313,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -380,10 +380,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^sync-status$' | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (Default: '%{sync\_status} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %{sync\_status} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (Default: '%{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %{sync\_status} | -| --warning-timebase-status | Define the conditions to match for the status to be WARNING (Default: '%{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %{timebase\_status} | -| --critical-timebase-status | Define the conditions to match for the status to be CRITICAL (Default: '%{timebase\_status} =~ /^XO$/i'). You can use the following variables: %{timebase\_status} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (Default: '%\{sync_status\} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %\{sync_status\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %\{sync_status\} | +| --warning-timebase-status | Define the conditions to match for the status to be WARNING (Default: '%\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %\{timebase_status\} | +| --critical-timebase-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{timebase_status\} =~ /^XO$/i'). You can use the following variables: %\{timebase_status\} | | --warning-* | Warning threshold. Can be: 'ntp-requests'. | | --critical-* | Critical threshold. Can be: 'ntp-requests'. | @@ -400,9 +400,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md index 1ffc91b497d6..b7501c777616 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md @@ -358,7 +358,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md index 13edba60dc7d..9fc4b7e2d8ce 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md @@ -269,8 +269,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -297,9 +297,9 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match to return a unknown status. The condition can be written using the following macros: %{storage\_state} | %{storage\_state} =~ /Unknown/i | | -| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{storage\_state} | %{storage_state} =~ /insufficientMediaCapacity/i \| \ | %{storage_state} =~ /insufficientMediaSpeed/i | | -| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %{storage\_state} | %{storage_state} =~ /mediaNotPresent/i \| \ | %{storage_state} =~ /error/i | | +| UNKNOWNSTATUS | Define the conditions to match to return a unknown status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /Unknown/i | | +| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /insufficientMediaCapacity/i \| \ | %\{storage_state\} =~ /insufficientMediaSpeed/i | | +| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /mediaNotPresent/i \| \ | %\{storage_state\} =~ /error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -307,8 +307,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %{status} | %{status} ne "ok" | | -| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{status} | | | +| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %\{status\} | %\{status\} ne "ok" | | +| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{status\} | | | | WARNINGTEMPERATURE | Warning threshold for temperature (Celsius). | | | | CRITICALTEMPERATURE | Critical threshold for temperature (Celsius). | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -399,7 +399,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -473,9 +473,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -509,17 +509,17 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match to return a unknown status (default: "%{storage\_state} =~ /Unknown/i"). The condition can be written using the following macros: %{storage\_state}. | -| --warning-status | Define the conditions to match to return a warning status (default: "%{storage\_state} =~ /insufficientMediaCapacity/i \|\| %{storage\_state} =~ /insufficientMediaSpeed/i"). The condition can be written using the following macros: %{storage\_state}. | -| --critical-status | Define the conditions to match to return a critical status (default: "%{storage\_state} =~ /mediaNotPresent/i \|\| %{storage\_state} =~ /error/i"). The condition can be written using the following macros: %{storage\_state}. | +| --unknown-status | Define the conditions to match to return a unknown status (default: "%\{storage_state\} =~ /Unknown/i"). The condition can be written using the following macros: %\{storage_state\}. | +| --warning-status | Define the conditions to match to return a warning status (default: "%\{storage_state\} =~ /insufficientMediaCapacity/i \|\| %\{storage_state\} =~ /insufficientMediaSpeed/i"). The condition can be written using the following macros: %\{storage_state\}. | +| --critical-status | Define the conditions to match to return a critical status (default: "%\{storage_state\} =~ /mediaNotPresent/i \|\| %\{storage_state\} =~ /error/i"). The condition can be written using the following macros: %\{storage_state\}. | | Option | Description | |:------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{status}. | -| --critical-status | Define the conditions to match to return a critical status (default: '%{status} ne "ok"'). The condition can be written using the following macros: %{status}. | +| --warning-status | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{status\}. | +| --critical-status | Define the conditions to match to return a critical status (default: '%\{status\} ne "ok"'). The condition can be written using the following macros: %\{status\}. | | --warning-temperature* | Warning threshold for temperature (Celsius). | | --critical-temperature* | Critical threshold for temperature (Celsius). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md index 1daacee06f73..29138d7e7675 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md @@ -237,8 +237,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | %{alarm} eq "enabled" | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | %\{alarm\} eq "enabled" | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -279,8 +279,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -311,8 +311,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | %{alarm} eq "enabled" | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | %\{alarm\} eq "enabled" | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | | | | WARNINGPROBETEMPERATURE | Thresholds | | | | CRITICALPROBETEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -407,7 +407,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -462,9 +462,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm} eq "enabled"'). You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm\} eq "enabled"'). You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | @@ -491,9 +491,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -528,9 +528,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm} eq "enabled"'). You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm\} eq "enabled"'). You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | | --warning-* --critical-* | Thresholds. Can be: 'probe-temperature'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md index 77bcbc2c170b..12cf52ad33ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md @@ -311,10 +311,10 @@ Les options spécifiques aux modes sont listées ci-dessus : | --filter-acked | Hide acknowledged alarms. | Mode | | --filter-active | Only show active alarms. | Mode | | --filter-severity | Only show alarms with a given severity level. Can be: 'critical', 'major', 'minor', 'warning', 'cleared'. Only one value can be set (no multiple values). | Mode | -| --warning-active-status | Set warning threshold for active status (Default: ''). Typical syntax: --warning-active-status='%{active} =~ "true"' | Mode | -| --critical-active-status | Set critical threshold for active status (Default: '%{active} =~ "true"'). Typical syntax: --critical-active-status='%{active} =~ "true"' | Mode | -| --warning-acked-status | Set warning threshold for acked status (Default: '%{acked} =~ "false"'). Typical syntax: --warning-acked-status='%{acked} =~ "false"' | Mode | -| --critical-acked-status | Set critical threshold for acked status (Default: ''). Typical syntax: --critical-acked-status='%{acked} =~ "false"' | Mode | +| --warning-active-status | Set warning threshold for active status (Default: ''). Typical syntax: --warning-active-status='%\{active\} =~ "true"' | Mode | +| --critical-active-status | Set critical threshold for active status (Default: '%\{active\} =~ "true"'). Typical syntax: --critical-active-status='%\{active\} =~ "true"' | Mode | +| --warning-acked-status | Set warning threshold for acked status (Default: '%\{acked\} =~ "false"'). Typical syntax: --warning-acked-status='%\{acked\} =~ "false"' | Mode | +| --critical-acked-status | Set critical threshold for acked status (Default: ''). Typical syntax: --critical-acked-status='%\{acked\} =~ "false"' | Mode | | --warning-* --critical-* | Thresholds. Can be: 'warning-alarms-total' (count) 'critical-alarms-total' (count), 'warning-alarm-duration' (s), 'critical-alarm-duration' (s), 'warning-alarm-severity' (level from 0 to 5), critical-alarm-severity (level from 0 to 5). | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md index ba39c7d3265d..7c70fa5cc20f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md @@ -119,8 +119,8 @@ Une fois le Plugin installé, vous pouvez tester celui-ci directement en ligne d --api-username='myapiusername' \ --api-password='myapipassword' \ --filter-name='mycall1.centreon.com' \ - --warning-status='%{level} =~ /warning|minor/i' \ - --critical-status='%{level} =~ /critical|major|error/i' \ + --warning-status='%\{level\} =~ /warning|minor/i' \ + --critical-status='%\{level\} =~ /critical|major|error/i' \ --verbose ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md index 70f0b0f86575..40356b43f70a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md @@ -165,8 +165,8 @@ depuis un collecteur Centreon en vous connectant avec l'utilisateur *centreon-en --hostname=10.0.0.1 \ --snmp-version='2c' --snmp-community='mysnmpcommunity' \ - --critical-cluster-status='%{cluster_status} =~ /outOfService/i' \ - --critical-license-status='%{license_status} =~ /notinstalled/i' \ + --critical-cluster-status='%\{cluster_status\} =~ /outOfService/i' \ + --critical-license-status='%\{license_status\} =~ /notinstalled/i' \ --warning-cluster-license-usage-prct='80' \ --critical-cluster-license-usage-prct='90' \ --verbose diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md index cc6e9d1bda17..385fb1a596d4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md @@ -186,9 +186,9 @@ yum install centreon-plugin-Hardware-Devices-Video-Appeartv-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| -| CRITICSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/ | | +| CRITICSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/ | | | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor\|warning/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor\|warning/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -212,8 +212,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --filter-msg='' \ - --warning-status='%{severity} =~ /minor|warning/i' \ - --critical-status='%{severity} =~ /critical|major/' + --warning-status='%\{severity\} =~ /minor|warning/i' \ + --critical-status='%\{severity\} =~ /critical|major/' ``` La commande devrait retourner un message de sortie similaire à : @@ -275,8 +275,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | | --dyn-mode | Specify a mode with the module's path (advanced). | @@ -312,7 +312,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md index bc7d8921158b..d4a946c269f7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md @@ -281,9 +281,9 @@ yum install centreon-plugin-Hardware-Kvm-Avocent-Acs-8000-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter by serial port name (can be a regexp) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICOUT | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -372,7 +372,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -490,9 +490,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-name | Filter by serial port name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md index f64b6e14a042..5a0bd21a0eff 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md @@ -296,7 +296,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -363,12 +363,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-bank-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | -| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low\|nearOverload/i'). You can use the following variables: %{type}, %{status}, %{display} | -| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^overload/'). You can use the following variables: %{type}, %{status}, %{display} | -| --unknown-phase-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low\|nearOverload/i'). You can use the following variables: %{status}, %{display} | -| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^overload/i'). You can use the following variables: %{status}, %{display} | +| --unknown-bank-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low\|nearOverload/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^overload/'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --unknown-phase-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low\|nearOverload/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^overload/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current', 'power'. | @@ -376,9 +376,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{phase}, %{bank}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /off/'). You can use the following variables: %{status}, %{phase}, %{bank}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{phase\}, %\{bank\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /off/'). You can use the following variables: %\{status\}, %\{phase\}, %\{bank\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md index ce533a113076..ed8b3840e3ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md @@ -269,7 +269,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md index 5b93323e6a9c..e38254c4f739 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md @@ -194,14 +194,14 @@ yum install centreon-plugin-Hardware-Pdu-Cyberpower-Snmp |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| | WARNINGBANKCURRENT | Thresholds | | | | CRITICALBANKCURRENT | Thresholds | | | -| WARNINGBANKSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /low\|nearOverload/i | | -| CRITICALBANKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/'). You can use the following variables: %{state}, %{display} | %{state} =~ /^overload/i | | +| WARNINGBANKSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /low\|nearOverload/i | | +| CRITICALBANKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /^overload/i | | | WARNINGPHASECURRENT | Thresholds | | | | CRITICALPHASECURRENT | Thresholds | | | | WARNINGPHASEPOWER | Thresholds | | | | CRITICALPHASEPOWER | Thresholds | | | -| WARNINGPHASESTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /low\|nearOverload/i | | -| CRITICALPHASESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /^overload/i | | +| WARNINGPHASESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /low\|nearOverload/i | | +| CRITICALPHASESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /^overload/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -211,8 +211,8 @@ yum install centreon-plugin-Hardware-Pdu-Cyberpower-Snmp |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /off/'). You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | %{state} =~ /off/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /off/'). You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | %\{state\} =~ /off/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -236,7 +236,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{state} =~ /off/i' \ + --critical-status='%\{state\} =~ /off/i' \ --warning-current='' \ --critical-current='' \ --verbose @@ -293,7 +293,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -347,12 +347,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-bank-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | -| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/'). You can use the following variables: %{state}, %{display} | -| --unknown-phase-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | -| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/i'). You can use the following variables: %{state}, %{display} | +| --unknown-bank-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | +| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/'). You can use the following variables: %\{state\}, %\{display\} | +| --unknown-phase-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | +| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'phase-current', 'phase-power', 'phase-voltage', 'bank-current'. | @@ -360,9 +360,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{state}, %{phase}, %{bank}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /off/'). You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%\{state\}, %\{phase\}, %\{bank\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /off/'). You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md index f9ad195d81ff..938f58181214 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md @@ -199,16 +199,16 @@ yum install centreon-plugin-Hardware-Pdu-Eaton-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| UNKNOWNHUMIDITYSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | -| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNHUMIDITYSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGHUMIDITY | Thresholds | | | | CRITICALHUMIDITY | Thresholds | | | -| CRITICALHUMIDITYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | %{status} eq "bad" | | -| WARNINGHUMIDITYSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALHUMIDITYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "bad" | | +| WARNINGHUMIDITYSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | -| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | %{status} eq "bad" | | -| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "bad" | | +| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -318,7 +318,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -372,12 +372,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | -| --unknown-humidity-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-humidity-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-humidity-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | +| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-humidity-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-humidity-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-humidity-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'humidity' (%), 'temperature' (C). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md index f46704a96e7e..9289f6960864 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md @@ -207,8 +207,8 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| | FILTERNAME | Filter PDU name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /normalWithAlarm\|abnormalOperation/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /normalWithWarning/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /normalWithWarning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /normalWithAlarm\|abnormalOperation/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /normalWithWarning/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /normalWithWarning/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -235,7 +235,7 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | FILTERNAME | Filter by name (can be a regexp) | | | -| UNKNOWNRCPSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | | | +| UNKNOWNRCPSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | | | | WARNINGCURRENTNEUTRAL | Thresholds | | | | CRITICALCURRENTNEUTRAL | Thresholds | | | | WARNINGLINE2NEUTRALAPPARENTPOWER | Thresholds | | | @@ -244,8 +244,8 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | CRITICALLINE2NEUTRALREALPOWER | Thresholds | | | | WARNINGPOTENTIALNEUTRAL | Thresholds | | | | CRITICALPOTENTIALNEUTRAL | Thresholds | | | -| WARNINGRCPSTATUS | Define the conditions to match for the status to be WARNING (default: '%{oper\_state} =~ /warning\|alarm/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | %{oper\_state} =~ /warning\|alarm/ | | -| CRITICALRCPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_state} =~ /abnormal/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | %{oper\_state} =~ /abnormal/ | | +| WARNINGRCPSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{oper_state\} =~ /warning\|alarm/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | %\{oper_state\} =~ /warning\|alarm/ | | +| CRITICALRCPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_state\} =~ /abnormal/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | %\{oper_state\} =~ /abnormal/ | | | WARNINGTOTALACCUMULATEDENERGY | Thresholds | | | | CRITICALTOTALACCUMULATEDENERGY | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,7 +336,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -391,8 +391,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter PDU name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /normalWithWarning/i'). You can use the following variables: %{status}, %{display}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /normalWithWarning/i'). You can use the following variables: %\{status\}, %\{display\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %\{status\}, %\{display\} | @@ -434,9 +434,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-rb | Filter receptable branch name (can be a regexp). | -| --unknown-rcp-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | -| --warning-rcp-status | Define the conditions to match for the status to be WARNING (default: '%{oper\_state} =~ /warning\|alarm/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | -| --critical-rcp-status | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_state} =~ /abnormal/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | +| --unknown-rcp-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | +| --warning-rcp-status | Define the conditions to match for the status to be WARNING (default: '%\{oper_state\} =~ /warning\|alarm/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | +| --critical-rcp-status | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_state\} =~ /abnormal/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-accumulated-energy', 'line2neutral-real-power', 'line2neutral-apparent-power'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md index ec68de8c364a..a0a4f2c70ac0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md @@ -225,7 +225,7 @@ yum install centreon-plugin-Hardware-Pdu-Gude-Epc-Snmp | CRITICALENERGY | Critical threshold | | | | WARNINGFREQUENCY | Warning threshold | | | | CRITICALFREQUENCY | Critical threshold | | | -| CRITICALOVPSTATUS | Critical threshold for OVP (OverVoltage Protection) status (default: '%{ovp\_status} !~ /ok/i') | %{ovp\_status} !~ /ok/i | | +| CRITICALOVPSTATUS | Critical threshold for OVP (OverVoltage Protection) status (default: '%\{ovp_status\} !~ /ok/i') | %\{ovp_status\} !~ /ok/i | | | WARNINGOVPSTATUS | Warning threshold for OVP (OverVoltage Protection) status | | | | WARNINGPHASEANGLE | Warning threshold | | | | CRITICALPHASEANGLE | Critical threshold | | | @@ -237,9 +237,9 @@ yum install centreon-plugin-Hardware-Pdu-Gude-Epc-Snmp | CRITICALPOWERFACTOR | Critical threshold | | | | WARNINGPOWERREACTIVE | Warning threshold | | | | CRITICALPOWERREACTIVE | Critical threshold | | | -| CRITICALPSSTATUS | Critical threshold for power supply status (default: '%{ps\_status} !~ /up/i') | %{ps\_status} !~ /up/i | | +| CRITICALPSSTATUS | Critical threshold for power supply status (default: '%\{ps_status\} !~ /up/i') | %\{ps_status\} !~ /up/i | | | WARNINGPSSTATUS | Warning threshold for power supply status | | | -| CRITICALSTATUS | Critical threshold for channel status (default: '%{status} !~ /valid/i') | %{status} !~ /valid/i | | +| CRITICALSTATUS | Critical threshold for channel status (default: '%\{status\} !~ /valid/i') | %\{status\} !~ /valid/i | | | WARNINGSTATUS | Warning threshold for channel status | | | | WARNINGVOLTAGE | Warning threshold | | | | CRITICALVOLTAGE | Critical threshold | | | @@ -377,7 +377,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -433,11 +433,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter power channel interfaces by name (can be a regexp). | | --warning-status | Warning threshold for channel status. | -| --critical-status | Critical threshold for channel status (default: '%{status} !~ /valid/i') | +| --critical-status | Critical threshold for channel status (default: '%\{status\} !~ /valid/i') | | --warning-ovp-status | Warning threshold for OVP (OverVoltage Protection) status. | -| --critical-ovp-status | Critical threshold for OVP (OverVoltage Protection) status (default: '%{ovp\_status} !~ /ok/i') | +| --critical-ovp-status | Critical threshold for OVP (OverVoltage Protection) status (default: '%\{ovp_status\} !~ /ok/i') | | --warning-ps-status | Warning threshold for power supply status. | -| --critical-ps-status | Critical threshold for power supply status (default: '%{ps\_status} !~ /up/i') | +| --critical-ps-status | Critical threshold for power supply status (default: '%\{ps_status\} !~ /up/i') | | --warning-* | Warning threshold. Can be: 'active-channels', 'current', 'energy', 'frequency', 'phase-angle', 'power-active', 'power-apparent', 'power-factor', 'power-reactive', 'voltage' | | --critical-* | Can be: 'active-channels', 'current', 'energy', 'frequency', 'phase-angle', 'power-active', 'power-apparent', 'power-factor', 'power-reactive', 'voltage' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md index 4bf6ac2c628a..0beede7dbf1f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md @@ -315,7 +315,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md index 3f5b8419c3ce..186334a0939c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md @@ -262,7 +262,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md index 0723604803e7..954e5344fc69 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md @@ -264,10 +264,10 @@ yum install centreon-plugin-Hardware-Printers-Generic-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /ok/'). You can use the following variables: %{status} | %{status} =~ /ok/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /.*/'). You can use the following variables: %{status} | %{status} =~ /.*/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| OKSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /ok/'). You can use the following variables: %\{status\} | %\{status\} =~ /ok/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /.*/'). You can use the following variables: %\{status\} | %\{status\} =~ /.*/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -297,9 +297,9 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --hostname=10.0.0.1 \ --snmp-community='my-snmp-community' \ --snmp-version='2c' \ - --ok-status='%{status} =~ /ok/' \ + --ok-status='%\{status\} =~ /ok/' \ --unknown-status='' \ - --warning-status='%{status} =~ /.*/' \ + --warning-status='%\{status\} =~ /.*/' \ --critical-status='' \ --verbose ``` @@ -359,7 +359,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -413,9 +413,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%%{status} =~ /other\|unknown/'). You can use the following variables: %{status}, %{description} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%%{status} =~ /coverOpen\|interlockOpen/'). You can use the following variables: %{status}, %{description} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{description} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%%\{status\} =~ /other\|unknown/'). You can use the following variables: %\{status\}, %\{description\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%%\{status\} =~ /coverOpen\|interlockOpen/'). You can use the following variables: %\{status\}, %\{description\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{description\} | @@ -461,10 +461,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| | --big-endian | Use that option if your printer provides big-endian bits ordering. | -| --ok-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /ok/'). You can use the following variables: %{status} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /.*/'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --ok-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /ok/'). You can use the following variables: %\{status\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /.*/'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md index a5aeff0c0525..cab0f5bf15db 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md @@ -262,7 +262,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md index 0c7ba033f82d..24c82eda9542 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md @@ -273,7 +273,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md index 6994aa33ee27..052b987f5f0f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md @@ -265,7 +265,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md index 870eb50c8bc0..b36f4650cdcd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md @@ -298,7 +298,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md index ec068f33ca8c..4d8fab91e34a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md @@ -263,7 +263,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md index 0a74fe006266..057f5cf431ec 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md @@ -47,7 +47,7 @@ Voici le tableau des services pour ce connecteur, détaillant les métriques rat | Métrique | Unité | |:---------------|:------| -| hardware.sensor.temperature. | C or F | +| hardware.sensor.temperature.\ | C or F | | hardware.sensor.humidity.percentage | % | | input.status | N/A | @@ -259,7 +259,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md index a72b8a5ad77c..a82dd6838a61 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md @@ -262,7 +262,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md index 4e9bebebfa09..d433cd80e029 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md @@ -217,8 +217,8 @@ yum install centreon-plugin-Hardware-Sensors-Rittal-Cmc-Snmp | FILTERINDEX | | | | | FILTERNAME | Filter device name (can be a regexp) | | | | FILTERALIAS | Filter devices alias (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %{status} | %{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /notAvail\|lost\|error/i'). You can use the following variables: %{status} | %{status} =~ /notAvail\|lost\|error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %\{status\} | %\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /notAvail\|lost\|error/i'). You can use the following variables: %\{status\} | %\{status\} =~ /notAvail\|lost\|error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -239,9 +239,9 @@ yum install centreon-plugin-Hardware-Sensors-Rittal-Cmc-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------|:------------| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{overall\_device\_status} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{overall\_device\_status} =~ /detected\|lost\|changed\|update/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{unit\_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{unit_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{overall_device_status\}=~ /detected\|lost\|changed\|update/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{overall_device_status\}=~ /detected\|lost\|changed\|update/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\}=~ /warning/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\}=~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\}=~ /alarm/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\}=~ /alarm/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -338,7 +338,7 @@ Les options génériques aux modes sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -395,9 +395,9 @@ Les options spécifiques aux modes sont listées ci-dessous : | --filter-name | Filter device name (can be a regexp). | Mode | | --filter-alias | Filter devices alias (can be a regexp). | Mode | | --index | Filter device index (exact match). | Mode | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %{status} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /notAvail\|lost\|error/i'). You can use the following variables: %{status} | Mode | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %\{status\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /notAvail\|lost\|error/i'). You can use the following variables: %\{status\} | Mode | @@ -411,9 +411,9 @@ Les options spécifiques aux modes sont listées ci-dessous : | Option | Description | Type | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{overall\_device\_status} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{unit\_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{overall_device_status\}=~ /detected\|lost\|changed\|update/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\}=~ /warning/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\}=~ /alarm/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md index 5c80f6b8e7af..5b595846b33c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md @@ -329,7 +329,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md index 1a45571909bd..7045a52e9360 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md @@ -353,7 +353,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md index 9151ff60080d..a27d22677015 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md @@ -256,7 +256,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md index fd150745223d..93516e86b96b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md @@ -246,8 +246,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALAUDITMINOR | Critical threshold | | | | WARNINGAUDITTOTAL | Warning threshold | | | | CRITICALAUDITTOTAL | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -279,8 +279,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALFAULTSMINOR | Critical threshold | | | | WARNINGFAULTSTOTAL | Warning threshold | | | | CRITICALFAULTSTOTAL | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -288,9 +288,9 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown"') You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | %{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down"'). You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | %{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown"') You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | %\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down"'). You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | %\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -304,8 +304,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALOFFLINE | Thresholds | | | | WARNINGONLINE | Thresholds | | | | CRITICALONLINE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "offline"'). You can use the following variables: %{dn}, %{status} | %{status} eq "offline" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "offline"'). You can use the following variables: %\{dn\}, %\{status\} | %\{status\} eq "offline" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -337,7 +337,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-offline='' \ --critical-offline='' \ --warning-status='' \ - --critical-status='%{status} eq "offline"' \ + --critical-status='%\{status\} eq "offline"' \ --verbose ``` @@ -395,7 +395,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -461,8 +461,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | | --memory | Only check new audit. | | --filter-message | Filter on event message. (default: none) | | --retention | Event older (current time - retention time) is not checked (in seconds). | @@ -495,8 +495,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | | --memory | Only check new fault. | | --filter-message | Filter on event message. (default: none) | | --retention | Event older (current time - retention time) is not checked (in seconds). | @@ -506,9 +506,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown"') You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down"'). You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown"') You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down"'). You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -516,8 +516,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "offline"'). You can use the following variables: %{dn}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "offline"'). You can use the following variables: %\{dn\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'online', 'offline'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md index 66c898a98ec4..397a4e6922e1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md @@ -274,7 +274,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -328,12 +328,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nonCritical\|other/'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical\|nonRecoverable/'). You can use the following variables: %{status} | -| --unknown-storage-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /unknown/'). You can use the following variables: %{status} | -| --warning-storage-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nonCritical\|other/'). You can use the following variables: %{status} | -| --critical-storage-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical\|nonRecoverable/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nonCritical\|other/'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical\|nonRecoverable/'). You can use the following variables: %\{status\} | +| --unknown-storage-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\} | +| --warning-storage-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nonCritical\|other/'). You can use the following variables: %\{status\} | +| --critical-storage-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical\|nonRecoverable/'). You can use the following variables: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md index f0bfb172e27d..7dd31f257c92 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md @@ -241,7 +241,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md index 89e1ba694d1f..2a64379e2448 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md @@ -185,9 +185,9 @@ yum install centreon-plugin-Hardware-Servers-Hp-Oneview-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter pool name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -199,7 +199,7 @@ yum install centreon-plugin-Hardware-Servers-Hp-Oneview-Restapi -3. [Déployez la configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). Le service apparaît dans la liste des services supervisés, et dans la page **Statut des ressources**. La commande envoyée par le connecteur est indiquée dans le panneau de détails du service : celle-ci montre les valeurs des macros. +1. [Déployez la configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). Le service apparaît dans la liste des services supervisés, et dans la page **Statut des ressources**. La commande envoyée par le connecteur est indiquée dans le panneau de détails du service : celle-ci montre les valeurs des macros. ## Comment puis-je tester le plugin et que signifient les options des commandes ? @@ -284,7 +284,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -351,9 +351,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter pool name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md index 49abc2f1caed..73597ff5e9ff 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md @@ -411,7 +411,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md index 8f8d4112fc73..b86da9619183 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md @@ -277,7 +277,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md index 2b4e4a7ddd9a..f12c0de12c85 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md @@ -236,8 +236,8 @@ yum install centreon-plugin-Hardware-Storage-Avid-Isis-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{state} !~ /Online/i'). Can use special variables like: %{state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{state\} !~ /Online/i'). Can use special variables like: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -333,7 +333,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -409,8 +409,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{state} !~ /Online/i'). Can use special variables like: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{state\} !~ /Online/i'). Can use special variables like: %\{state\} | | --warning-redistributing-count | Warning threshold for number of workspaces redistributing. | | --critical-redistributing-count | Critical threshold for number of workspaces redistributing. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md index 1b936caae500..10a60ce4cf25 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md @@ -263,7 +263,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md index ca0905bd9299..ad8acb4ac5dd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md @@ -220,8 +220,8 @@ yum install centreon-plugin-Hardware-Storage-DataCore-Sansymphony-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:--------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERCAPTION | Define which element should be monitored based on the extended caption. This option will be treated as a regular expression. By default all elements will be checked | | | -| WARNINGSTATE | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | -| CRITICALSTATE | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | +| WARNINGSTATE | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | +| CRITICALSTATE | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -321,7 +321,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -385,7 +385,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-caption | Define which element should be monitored based on the extended caption. This option will be treated as a regular expression. By default all elements will be checked. | -| --warning-state --critical-state | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical. | +| --warning-state --critical-state | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md index c2e631a2f5db..ea0a2514f4f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md @@ -332,7 +332,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md index e01348da5de1..d9c1a47bf534 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md @@ -261,7 +261,7 @@ yum install centreon-plugin-Hardware-Storage-Dell-Compellent-Snmp | WARNINGIN | Warning thresholds | 80 | | | CRITICALOUT | Critical thresholds | 90 | | | WARNINGOUT | Warning thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -353,7 +353,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -440,9 +440,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md index 020a06061253..14721382c650 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md index c79ce56d6424..e07cfd179874 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md @@ -390,7 +390,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md index 461800f0087f..8a9e4b1de1ad 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md @@ -332,7 +332,7 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| -| TRULYALERT | Expression to define an actual alert (default: '%{severity} =~ /emergency\|alert\|warning\|critical/i') | %{severity} =~ /emergency\|alert\|warning\|critical/i | | +| TRULYALERT | Expression to define an actual alert (default: '%\{severity\} =~ /emergency\|alert\|warning\|critical/i') | %\{severity\} =~ /emergency\|alert\|warning\|critical/i | | | WARNINGALERTSCURRENT | Threshold | | | | CRITICALALERTSCURRENT | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -416,8 +416,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -426,8 +426,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:----------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERMTREENAME | Check MTress by name | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -435,14 +435,14 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCIFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{cifsStatus} | | | -| CRITICALCIFSSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{cifsStatus} =~ /enabledNotRunning/'). You can use the following variables: %{cifsStatus} | | | -| WARNINGDDBOOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ddboostStatus} | | | -| CRITICALDDBOOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ddboostStatus} | | | -| WARNINGNFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{nfsStatus} | | | -| CRITICALNFSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{nfsStatus} | | | -| WARNINGVTLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | | | -| CRITICALVTLSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{vtlAdminState} =~ /failed/'). You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | | | +| WARNINGCIFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{cifsStatus\} | | | +| CRITICALCIFSSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{cifsStatus\} =~ /enabledNotRunning/'). You can use the following variables: %\{cifsStatus\} | | | +| WARNINGDDBOOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ddboostStatus\} | | | +| CRITICALDDBOOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ddboostStatus\} | | | +| WARNINGNFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{nfsStatus\} | | | +| CRITICALNFSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{nfsStatus\} | | | +| WARNINGVTLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | | | +| CRITICALVTLSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{vtlAdminState\} =~ /failed/'). You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -451,8 +451,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------|:-----------:| | CUSTOMINSTANCESNAME | Customize the name composition rule for the instances the metrics will be attached to (default: '%(type) %(source) %(destination)'). You can use the following variables: %(type) %(source) %(destination) | %(type) %(source) %(destination) | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /initializing\|recovering/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | %{state} =~ /disabledNeedsResync\|uninitialized/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | %{state} =~ /initializing\|recovering/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /initializing\|recovering/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | %\{state\} =~ /disabledNeedsResync\|uninitialized/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | %\{state\} =~ /initializing\|recovering/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -566,7 +566,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -601,7 +601,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --display-alerts | Display alerts in verbose output. | -| --truly-alert | Expression to define a truly alert (default: '%{severity} =~ /emergency\|alert\|warning\|critical/i'). | +| --truly-alert | Expression to define a truly alert (default: '%\{severity\} =~ /emergency\|alert\|warning\|critical/i'). | | --warning-* --critical-* | Thresholds. Can be: 'alerts-current'. | @@ -711,9 +711,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -754,9 +754,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-mtree-name | Check MTress by name. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'mtrees-detected', 'space-precompression-usage'. | @@ -765,18 +765,18 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --unknown-cifs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{cifsStatus} | -| --warning-cifs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{cifsStatus} | -| --critical-cifs-status | Define the conditions to match for the status to be CRITICAL (default: '%{cifsStatus} =~ /enabledNotRunning/'). You can use the following variables: %{cifsStatus} | -| --unknown-ddboost-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ddboostStatus} | -| --warning-ddboost-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ddboostStatus} | -| --critical-ddboost-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ddboostStatus} | -| --unknown-nfs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{nfsStatus} | -| --warning-nfs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{nfsStatus} | -| --critical-nfs-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{nfsStatus} | -| --unknown-vtl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | -| --warning-vtl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | -| --critical-vtl-status | Define the conditions to match for the status to be CRITICAL (default: '%{vtlAdminState} =~ /failed/'). You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | +| --unknown-cifs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{cifsStatus\} | +| --warning-cifs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{cifsStatus\} | +| --critical-cifs-status | Define the conditions to match for the status to be CRITICAL (default: '%\{cifsStatus\} =~ /enabledNotRunning/'). You can use the following variables: %\{cifsStatus\} | +| --unknown-ddboost-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ddboostStatus\} | +| --warning-ddboost-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ddboostStatus\} | +| --critical-ddboost-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ddboostStatus\} | +| --unknown-nfs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{nfsStatus\} | +| --warning-nfs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{nfsStatus\} | +| --critical-nfs-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{nfsStatus\} | +| --unknown-vtl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | +| --warning-vtl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | +| --critical-vtl-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vtlAdminState\} =~ /failed/'). You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | @@ -789,9 +789,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-repl-destination | Check replications by destination. | | --custom-perfdata-instances | Customize the name composition rule for the instances the metrics will be attached to (default: '%(type) %(source) %(destination)'). You can use the following variables: %(type) %(source) %(destination) | | --unit | Select the time unit for thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks (default: 'd'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /initializing\|recovering/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /initializing\|recovering/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'repl-detected', 'precompression-data-remaining', 'last-insync-time'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md index 7d41038d77e4..07e2654af1ae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md @@ -23,8 +23,8 @@ Generate key for centreon-engine user with command: # su - centreon-engine # ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa # ssh-keygen -e -f .ssh/identity.pub > identity.pub.ietf - # telnet - CLI> import ssh-public-key -server -port maintenance -user -filename identity.pub.ietf -account-name centreon + # telnet \ + CLI> import ssh-public-key -server \ -port maintenance -user \ -filename identity.pub.ietf -account-name centreon Password: importing ./identity.pub.ietf from ... CLI> exit @@ -32,7 +32,7 @@ Generate key for centreon-engine user with command: You can now try to connect you without password # su - centreon-engine - # ssh -l centreon + # ssh -l centreon \ ## Centreon Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md index 9613b8e14cd4..40171a3bcc3e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md @@ -241,10 +241,10 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:------------| -| UNKNOWNSTATUS | Set unknown threshold for status (Default: '%{state} =~ /unknown/'). You can use the following variables: %{state}, %{display} | %{state} =~ /unknown/ | | +| UNKNOWNSTATUS | Set unknown threshold for status (Default: '%\{state\} =~ /unknown/'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /unknown/ | | | FILTERNAME | Filter node name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /offline/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: -). You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /offline/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: -). You can use the following variables: %\{state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Tous les options sont listées [ici](#options-disponibles) | --verbose | | @@ -275,8 +275,8 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Tous les options sont listées [ici](#options-disponibles) | --verbose | | @@ -309,8 +309,8 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:------------| | FILTERNAME | Filter volume name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: -). You can use the following variables: %{status}, %{display} | %{status} =~ /needsChecking/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: '%{status} =~ /needsChecking/i'). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: -). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /needsChecking/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: '%\{status\} =~ /needsChecking/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Tous les options sont listées [ici](#options-disponibles) | --verbose | | @@ -512,7 +512,7 @@ Les options génériques aux modes sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Change storage free perfdata in used: --change-perfdata=free,used,invert() Change storage free perfdata in used: --change-perfdata=used,free,invert() Scale traffic values automaticaly: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Extend perfdata from multiple perfdatas (methods in target are: min, max, average, sum) Syntax: --extend-perfdata-group=searchlabel,newlabel,target\[,\[newuom\],\[m in\],\[max\]\] Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -567,9 +567,9 @@ Les options spécifiques aux modes sont listées ci-dessus : | Option | Description | Type | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------|:-----| | --filter-name | Filter node name (can be a regexp). | Mode | -| --unknown-status | Set unknown threshold for status (Default: '%{state} =~ /unknown/'). You can use the following variables: %{state}, %{display} | Mode | -| --warning-status | Set warning threshold for status (Default: -). You can use the following variables: %{state}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{display} | Mode | +| --unknown-status | Set unknown threshold for status (Default: '%\{state\} =~ /unknown/'). You can use the following variables: %\{state\}, %\{display\} | Mode | +| --warning-status | Set warning threshold for status (Default: -). You can use the following variables: %\{state\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{display\} | Mode | @@ -608,9 +608,9 @@ Les options spécifiques aux modes sont listées ci-dessus : | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'counter'). | Mode | @@ -649,8 +649,8 @@ Les options spécifiques aux modes sont listées ci-dessus : |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:-----| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | Mode | | --filter-name | Filter volume name (can be a regexp). | Mode | -| --warning-status | Set warning threshold for status (Default: '%{status} =~ /needsChecking/i'). You can use the following variables: %{status}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: -). You can use the following variables: %{status}, %{display} | Mode | +| --warning-status | Set warning threshold for status (Default: '%\{status\} =~ /needsChecking/i'). You can use the following variables: %\{status\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: -). You can use the following variables: %\{status\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'usage'. | Mode | | --units | Units of thresholds (Default: '%') ('%', 'B'). | Mode | | --free | Thresholds are on free space left. | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md index 283f805479be..1e56b436f61a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md @@ -304,7 +304,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md index 18f0e2890127..9a0fbe7fca00 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md @@ -301,8 +301,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | CRITICALFLASHCACHEUSAGEPRCT | Define the CRITICAL threshold for the following component: 'flashcache-usage-prct' | | | | WARNINGFLASHCACHEVOLUMEREADHITS | Define the WARNING threshold for the following component: 'flashcache-volume-readhits' | | | | CRITICALFLASHCACHEVOLUMEREADHITS | Define the CRITICAL threshold for the following component: 'flashcache-volume-readhits' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id} | %{status} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\} | %\{status\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -311,30 +311,30 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| | FILTERCAGEID | Filter cages by ID (can be a regexp) | | | -| CRITICALBOARDFIRMWARESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | %{status} !~ /Current/i | | -| WARNINGBOARDFIRMWARESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | | | -| CRITICALBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALBOARDFIRMWARESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | %\{status\} !~ /Current/i | | +| WARNINGBOARDFIRMWARESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | | +| CRITICALBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be WARNING | | | -| CRITICALBOARDSELFSTATUS | Define the conditions on self to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALBOARDSELFSTATUS | Define the conditions on self to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGBOARDSELFSTATUS | Define the conditions on self to match for the status to be WARNING | | | -| CRITICALDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be WARNING | | | -| CRITICALDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be WARNING | | | -| WARNINGDRIVESTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | | | -| CRITICALDRIVESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | | | +| WARNINGDRIVESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | | +| CRITICALDRIVESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | | | WARNINGDRIVETEMPERATURE | Define WARNING threshold for the temperature of the drives | | | | CRITICALDRIVETEMPERATURE | Define CRITICAL threshold for the temperature of the drives | | | -| CRITICALPSUACSTATUS | Define the conditions on psu ac to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUACSTATUS | Define the conditions on psu ac to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUACSTATUS | Define the conditions on psu ac to match for the status to be WARNING | | | -| CRITICALPSUDCSTATUS | Define the conditions on psu dc to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUDCSTATUS | Define the conditions on psu dc to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUDCSTATUS | Define the conditions on psu dc to match for the status to be WARNING | | | -| CRITICALPSUFANSTATUS | Define the conditions on psu fan to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUFANSTATUS | Define the conditions on psu fan to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUFANSTATUS | Define the conditions on psu fan to match for the status to be WARNING | | | -| CRITICALPSUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id} | %{status} !~ /Normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id} | | | +| CRITICALPSUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\} | %\{status\} !~ /Normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -379,8 +379,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter disk name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Warning threshold | | | | WARNINGUSAGEFREE | Warning threshold | | | @@ -397,8 +397,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | FILTERNODEID | Filter nodes by ID (can be a regexp) | | | | WARNINGCPUUTILIZATION | Warning threshold | | | | CRITICALCPUUTILIZATION | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -408,20 +408,20 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh |:-------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | FILTERNODEID | Filter nodes by ID (can be a regexp) | | | | FILTERPSUID | Filter power supplies by ID (can be a regexp) | | | -| CRITICALACSTATUS | Set critical threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGACSTATUS | Set warning threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALBATTERYSTATUS | Set critical threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGBATTERYSTATUS | Set warning threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | +| CRITICALACSTATUS | Set critical threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGACSTATUS | Set warning threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALBATTERYSTATUS | Set critical threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGBATTERYSTATUS | Set warning threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | | WARNINGCHARGEREMAINING | Warning threshold | | | | CRITICALCHARGEREMAINING | Critical threshold | | | | WARNINGCHARGEREMAININGMINUTES | Warning threshold | | | | CRITICALCHARGEREMAININGMINUTES | Critical threshold | | | -| CRITICALDCSTATUS | Set critical threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGDCSTATUS | Set warning threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALFANSTATUS | Set critical threshold for fan status . You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGFANSTATUS | Set warning threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | +| CRITICALDCSTATUS | Set critical threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGDCSTATUS | Set warning threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALFANSTATUS | Set critical threshold for fan status . You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGFANSTATUS | Set warning threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -557,7 +557,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -607,7 +607,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-volume-name | Filter volumes by name (can be a regexp). | | --unknown-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-status | Define the conditions to match for the status to be WARNING. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{node\_id} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{node_id\} | | --warning-* | Define the WARNING thresholds for the following components: 'flashcache-usage', 'flashcache-usage-free', 'flashcache-usage-prct', 'flashcache-node-readhits', 'flashcache-volume-readhits'. | | --critical-* | Define the CRITICAL thresholds for the following components: 'flashcache-usage', 'flashcache-usage-free', 'flashcache-usage-prct', 'flashcache-node-readhits', 'flashcache-volume-readhits'. | @@ -619,25 +619,25 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-cage-id | Filter cages by ID (can be a regexp). | | --unknown-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-status | Define the conditions to match for the status to be WARNING. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Normal/i') You can use the following variables: %{status}, %{cage\_id} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Normal/i') You can use the following variables: %\{status\}, %\{cage_id\} | | --unknown-board-firmware-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-board-firmware-status | Define the conditions to match for the status to be WARNING. | -| --critical-board-firmware-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Current/i') You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | +| --critical-board-firmware-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Current/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | --unknown-board-\[self\|partner\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-board-\[self\|partner\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-board-\[self\|partner\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | +| --critical-board-\[self\|partner\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-psu-status | Define the conditions to match for the status to be WARNING. | -| --critical-psu-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | +| --critical-psu-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | --unknown-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | +| --critical-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | --unknown-drive-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-drive-status | Define the conditions to match for the status to be WARNING. | -| --critical-drive-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | +| --critical-drive-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | --unknown-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | +| --critical-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | --warning-drive-temperature | Define WARNING threshold for the temperature of the drives. | | --critical-drive-temperature | Define CRITICAL threshold for the temperature of the drives. | @@ -669,8 +669,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter disk name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Warning threshold. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | @@ -679,9 +679,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-node-id | Filter nodes by ID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{node\_id} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{node_id\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization'. | @@ -691,21 +691,21 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-node-id | Filter nodes by ID (can be a regexp). | | --filter-psu-id | Filter power supplies by ID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-ac-status | Set unknown threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-ac-status | Set warning threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-ac-status | Set critical threshold for AC status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-dc-status | Set unknown threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-dc-status | Set warning threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-dc-status | Set critical threshold for DC status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-fan-status | Set unknown threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-fan-status | Set warning threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-fan-status | Set critical threshold for fan status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-battery-status | Set unknown threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-battery-status | Set warning threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-battery-status | Set critical threshold for battery status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-ac-status | Set unknown threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-ac-status | Set warning threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-ac-status | Set critical threshold for AC status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-dc-status | Set unknown threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-dc-status | Set warning threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-dc-status | Set critical threshold for DC status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-fan-status | Set unknown threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-fan-status | Set warning threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-fan-status | Set critical threshold for fan status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-battery-status | Set unknown threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-battery-status | Set warning threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-battery-status | Set critical threshold for battery status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining', 'charge-remaining-minutes. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md index 5e7ee7e371a1..3a2e7f2342fd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-Lefthand-Snmp | CRITICALREADIOPS | Critical threshold | | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /normal/i | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /normal/i | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Critical threshold | | | | WARNINGWRITE | Warning threshold | | | @@ -264,7 +264,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-write-latency='' \ --critical-write-latency='' \ --warning-replication-status='' \ - --critical-replication-status='%{status} !~ /normal/i' \ + --critical-replication-status='%\{status\} !~ /normal/i' \ --verbose ``` @@ -321,7 +321,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -401,8 +401,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^read\|write$' | | --filter-name | Filter volume name (can be a regexp). | -| --warning-replication-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i'). You can use the following variables: %{status}, %{display} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'read' (b/s), 'write' (b/s), 'read-iops', 'write-iops', 'read-latency', 'write-latency', 'usage'. | | --critical-* | Critical threshold. Can be: 'read' (b/s), 'write' (b/s), 'read-iops', 'write-iops', 'read-latency', 'write-latency', 'usage'. | | --units | Units of thresholds (default: '%') ('%', 'B'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md index 4c4e4dc35aa5..c54c70b5e07e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md @@ -248,7 +248,7 @@ yum install centreon-plugin-Hardware-Storage-Hp-Msa2000-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -335,7 +335,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -420,9 +420,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md index e65993ced633..4c882151a2c0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md @@ -320,8 +320,8 @@ yum install centreon-plugin-Hardware-Storage-Hpe-Primera-Restapi | CRITICALDISKSTOTAL | Thresholds. | | | | WARNINGDISKSUNKNOWN | Thresholds. | | | | CRITICALDISKSUNKNOWN | Thresholds. | | | -| WARNINGSTATUS | Define the condition to match for the returned status to be WARNING. Default: '%{status} =~ /^(new\|degraded\|unknown)$/' | %{status} =~ /^(new\|degraded\|unknown)$/ | | -| CRITICALSTATUS | Define the condition to match for the returned status to be CRITICAL. Default: '%{status} =~ /failed/' | %{status} =~ /failed/ | | +| WARNINGSTATUS | Define the condition to match for the returned status to be WARNING. Default: '%\{status\} =~ /^(new\|degraded\|unknown)$/' | %\{status\} =~ /^(new\|degraded\|unknown)$/ | | +| CRITICALSTATUS | Define the condition to match for the returned status to be CRITICAL. Default: '%\{status\} =~ /failed/' | %\{status\} =~ /failed/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -368,8 +368,8 @@ yum install centreon-plugin-Hardware-Storage-Hpe-Primera-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERNODEID | Define which nodes (filtered by regular expression) should be monitored. Example: --filter-node='^(0\|1)$' | | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the %{status} variables. | %{status} ne "online" | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the %{status} variables. | | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the %\{status\} variables. | %\{status\} ne "online" | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the %\{status\} variables. | | | | WARNINGOFFLINE | Thresholds for the number of offline nodes | 0:0 | | | CRITICALOFFLINE | Thresholds for the number of offline nodes | | | | WARNINGONLINE | Thresholds for the number of online nodes | | | @@ -485,7 +485,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -552,9 +552,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-model | Define which volumes should be monitored based on the disk model. This option will be treated as a regular expression. | | --filter-serial | Define which volumes should be monitored based on the disk serial number. This option will be treated as a regular expression. | | --filter-position | Define which volumes should be monitored based on the disk position. The position is composed of 3 integers, separated by colons: - Cage number where the physical disk is in. - Magazine number where the physical disk is in. - For DC4 cages, disk position within the magazine. For non-DC4 cages, 0. Example: 7:5:0 This option will be treated as a regular expression. | -| --warning-status | Define the condition to match for the returned status to be WARNING. Default: '%{status} =~ /^(new\|degraded\|unknown)$/' | -| --critical-status | Define the condition to match for the returned status to be CRITICAL. Default: '%{status} =~ /failed/' | -| --unknown-status | Define the condition to match for the returned status to be UNKNOWN. Default: '%{status} =~ /NOT\_DOCUMENTED$/' | +| --warning-status | Define the condition to match for the returned status to be WARNING. Default: '%\{status\} =~ /^(new\|degraded\|unknown)$/' | +| --critical-status | Define the condition to match for the returned status to be CRITICAL. Default: '%\{status\} =~ /failed/' | +| --unknown-status | Define the condition to match for the returned status to be UNKNOWN. Default: '%\{status\} =~ /NOT\_DOCUMENTED$/' | | --warning-* --critical-* | Thresholds. '*' may stand for 'disks-total', 'disks-normal', 'disks-degraded', 'disks-new', 'disks-failed', 'disks-unknown'. | @@ -584,8 +584,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------| | --filter-node | Define which nodes (filtered by regular expression) should be monitored. Example: --filter-node='^(0\|1)$' | -| --warning-node-status | Define the conditions to match for the status to be WARNING. (default: '%{status} ne "online"'). You can use the %{status} variables. | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL You can use the %{status} variables. | +| --warning-node-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} ne "online"'). You can use the %\{status\} variables. | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL You can use the %\{status\} variables. | | --warning-total | Thresholds for the total number of nodes. | | --critical-total | Thresholds for the total number of nodes. | | --warning-online | Thresholds for the number of online nodes. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md index c3af896e51d8..d64d0fc3d05d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md index f990d1ae0790..fc6f2b677986 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md index d2a24d146744..c7916384549b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md index 52a7f786982c..9a316cd80876 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md @@ -235,8 +235,8 @@ yum install centreon-plugin-Hardware-Storage-Ibm-Storwize-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERNAME | Filter pool name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /degraded/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /degraded/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /offline/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /degraded/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /degraded/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /offline/i | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -247,8 +247,8 @@ yum install centreon-plugin-Hardware-Storage-Ibm-Storwize-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:-------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERCONSISTENCYGROUPNAME | Filter group name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /idling/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /idling/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -334,7 +334,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -407,8 +407,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter pool name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /degraded/i'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /degraded/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage'. | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md index 87b540fcddb4..6ab7cbc94f99 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md @@ -253,7 +253,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md index 56ce289d2fa0..4931806844cf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md @@ -253,7 +253,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md index c112af8622e4..1b15b06baead 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md @@ -220,7 +220,7 @@ yum install centreon-plugin-Hardware-Storage-Lenovo-Sseries-Snmp | CRITICALIN | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -307,7 +307,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -392,9 +392,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md index cfe1a9e195f2..06f8e9287873 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md @@ -294,8 +294,8 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | CRITICALREADIOPS | Thresholds | | | | WARNINGREADLATENCY | Thresholds | | | | CRITICALREADLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALIOPS | Thresholds | | | @@ -321,9 +321,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| -| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{link\_status}, %{display} | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "online"'). You can use the following variables: %{state}, %{link\_status}, %{display} | %{state} ne "online" | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{link\_status}, %{display} | | | +| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "online"'). You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | %\{state\} ne "online" | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADIOPS | Thresholds | | | @@ -352,9 +352,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERNAME | Filter LUN name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{container\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{container\_state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{container\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -380,9 +380,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------|:-----------:| | FILTERNAME | Filter snapmirror name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{healthy} ne "true" or %{state} eq "broken\_off"'). You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | %{healthy} ne "true" or %{state} eq "broken\_off" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{healthy\} ne "true" or %\{state\} eq "broken\_off"'). You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | %\{healthy\} ne "true" or %\{state\} eq "broken\_off" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -391,15 +391,15 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERNAME | Filter volumes by volume name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADIOPS | Thresholds | | | | CRITICALREADIOPS | Thresholds | | | | WARNINGREADLATENCY | Thresholds | | | | CRITICALREADLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -439,7 +439,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-name='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{state} !~ /online/i' \ + --critical-status='%\{state\} !~ /online/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -524,7 +524,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -568,9 +568,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter aggregates by aggregate name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'read' (B/s), 'read-iops', 'write' (B/s), 'write-iops', 'read-latency' (ms), 'write-latency' (ms), 'total-latency' (ms), 'other-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | @@ -591,9 +591,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='node-status' | -| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{link\_status}, %{display} | -| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{link\_status}, %{display} | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "online"'). You can use the following variables: %{state}, %{link\_status}, %{display} | +| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | +| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "online"'). You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization' (%), 'read' (B/s), 'write' (B/s), 'read-iops', 'write-iops', 'read-latency' (ms), 'write-lantency' (ms), 'other-latency' (ms), 'total-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | @@ -612,9 +612,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter LUN name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{container\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{container\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{container\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | @@ -633,9 +633,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter snapmirror name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{healthy} ne "true" or %{state} eq "broken\_off"'). You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{healthy\} ne "true" or %\{state\} eq "broken\_off"'). You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | @@ -645,9 +645,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter volumes by volume name (can be a regexp). | | --filter-vserver-name | Filter volumes by vserver name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'read' (B/s), 'read-iops', 'write' (B/s), 'write-iops', 'read-latency' (ms), 'write-latency' (ms), 'total-latency' (ms), 'other-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md index 71ffbf257c27..467b705c33b5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md @@ -153,8 +153,8 @@ Centreon avec l'utilisateur *centreon-engine*: --api-password='xxxx' \ --mode=storage-volumes \ --verbose \ - --warning-volume-status='%{status} =~ /degraded/i' \ - --critical-volume-status='%{status} =~ /failed/i' + --warning-volume-status='%\{status\} =~ /degraded/i' \ + --critical-volume-status='%\{status\} =~ /failed/i' ``` La commande doit retourner un résultat de la forme: diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md index d0ed83941142..48c9d7ee3b67 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md @@ -228,8 +228,8 @@ yum install centreon-plugin-Hardware-Storage-Purestorage-Flasharray-V2-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERCATEGORY | Filter by category name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} ne "closed" and %{severity} =~ /warning/i') You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | %{state} ne "closed" and %{severity} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "closed" and %{severity} =~ /critical/i'). You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | %{state} ne "closed" and %{severity} =~ /critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} ne "closed" and %\{severity\} =~ /warning/i') You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | %\{state\} ne "closed" and %\{severity\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "closed" and %\{severity\} =~ /critical/i'). You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | %\{state\} ne "closed" and %\{severity\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -370,7 +370,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -425,8 +425,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-category | Filter by category name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} ne "closed" and %{severity} =~ /warning/i') You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "closed" and %{severity} =~ /critical/i'). You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} ne "closed" and %\{severity\} =~ /warning/i') You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "closed" and %\{severity\} =~ /critical/i'). You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | | --memory | Only check new alarms. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md index c2203f54ba62..5d5130be640e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md @@ -287,7 +287,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md index 93a8960e656f..821d3fa3001c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md @@ -326,8 +326,8 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERNAME | Filter pools by name (can be a regexp) | | | -| WARNINGPOOLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /degraded\|warning/i | | -| CRITICALPOOLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /error\|critical/i | | +| WARNINGPOOLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /degraded\|warning/i | | +| CRITICALPOOLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /error\|critical/i | | | WARNINGSPACEUSAGE | Threshold | | | | CRITICALSPACEUSAGE | Threshold | | | | WARNINGSPACEUSAGEFREE | Threshold | | | @@ -370,7 +370,7 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | WARNINGIN | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -385,8 +385,8 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | CRITICALSPACEUSAGEFREE | Threshold | | | | WARNINGSPACEUSAGEPRCT | Threshold | | | | CRITICALSPACEUSAGEPRCT | Threshold | | | -| WARNINGVOLUMESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /degraded\|warning/i | | -| CRITICALVOLUMESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /critical/i | | +| WARNINGVOLUMESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /degraded\|warning/i | | +| CRITICALVOLUMESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -509,7 +509,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -619,9 +619,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter pools by name (can be a regexp). | -| --unknown-pool-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-pool-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded\|warning/i'). You can use the following variables: %{status}, %{name} | -| --critical-pool-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /error\|critical/i'). You can use the following variables: %{status}, %{name} | +| --unknown-pool-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-pool-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded\|warning/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-pool-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /error\|critical/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage-prct', 'space-usage', 'space-usage-free'. | @@ -650,9 +650,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -682,9 +682,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter volumes by name (can be a regexp). | | --force-counters-legacy | Force to use legacy counters. Should be used when EX/QTS counters are buggy. | -| --unknown-volume-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-volume-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded\|warning/i'). You can use the following variables: %{status}, %{name} | -| --critical-volume-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{name} | +| --unknown-volume-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-volume-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded\|warning/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-volume-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage-prct', 'space-usage', 'space-usage-free'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md index 36d8637fc2e1..f3bc5542f9fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md @@ -270,7 +270,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md index ec1ee28ecf6f..4933c7ff0545 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md @@ -353,7 +353,7 @@ yum install centreon-plugin-Hardware-Storage-Synology-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -459,7 +459,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -622,9 +622,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md index 8926578fe1ed..1b78e9e38b09 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md @@ -218,8 +218,8 @@ yum install centreon-plugin-Hardware-Storage-Wd-Nas-Snmp |:--------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | WARNINGDRIVETEMPERATURE | Warning threshold for 'drive-temperature' | | | | CRITICALDRIVETEMPERATURE | Critical threshold for 'drive-temperature' | | | -| WARNINGFANSTATUS | Define the conditions to match for the status to be WARNING (default : '%{status} ne "running"'). You can use the following variables: %{status} | | | -| CRITICALFANSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGFANSTATUS | Define the conditions to match for the status to be WARNING (default : '%\{status\} ne "running"'). You can use the following variables: %\{status\} | | | +| CRITICALFANSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSYSTEMTEMPERATURE | Warning threshold for 'system-temperature' | | | | CRITICALSYSTEMTEMPERATURE | Critical threshold for 'system-temperature' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -320,7 +320,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -374,8 +374,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-fan-status | Define the conditions to match for the status to be WARNING (default : '%{status} ne "running"'). You can use the following variables: %{status} | -| --critical-fan-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --warning-fan-status | Define the conditions to match for the status to be WARNING (default : '%\{status\} ne "running"'). You can use the following variables: %\{status\} | +| --critical-fan-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'system-temperature', 'drive-temperature'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-telephony-alcatel-oxe-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-telephony-alcatel-oxe-snmp.md index 9eda05f95821..84e138916de8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-telephony-alcatel-oxe-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-telephony-alcatel-oxe-snmp.md @@ -120,7 +120,7 @@ Statut sous forme de chaîne. |:------------------------------------------|:-------| | *trunk*#trunk.channels.outofservice.count | count | | *trunk*#trunk.channels.current.count | count | -| %{trunkstatus} | string | +| %\{trunkstatus\} | string | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md index 799ba7095e0a..d311518aef28 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md @@ -196,13 +196,13 @@ yum install centreon-plugin-Hardware-Ups-Alpha-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Warning threshold | | | | CRITICALCURRENT | Critical threshold | | | | WARNINGLOAD | Warning threshold | | | | CRITICALLOAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status} | %{status} =~ /batteryLow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /batteryDepleted/i'). You can use the following variables: %{status} | %{status} =~ /batteryDepleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryLow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /batteryDepleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDepleted/i | | | WARNINGTEMPERATURE | Warning threshold | | | | CRITICALTEMPERATURE | Critical threshold | | | | WARNINGVOLTAGE | Warning threshold | | | @@ -229,9 +229,9 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --hostname=10.0.0.1 \ --snmp-version='2c' \ --snmp-community='my-snmp-community' \ - --unknown-status='%{status} =~ /unknown/i' \ - --warning-status='%{status} =~ /batteryLow/i' \ - --critical-status='%{status} =~ /batteryDepleted/i' \ + --unknown-status='%\{status\} =~ /unknown/i' \ + --warning-status='%\{status\} =~ /batteryLow/i' \ + --critical-status='%\{status\} =~ /batteryDepleted/i' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -293,7 +293,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -357,9 +357,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /batteryDepleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /batteryDepleted/i'). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'load', 'voltage', 'current', 'temperature'. | | --critical-* | Critical threshold. Can be: 'load', 'voltage', 'current', 'temperature'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md index e5ee4987ed43..cfb59838ee6c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md @@ -236,14 +236,14 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{replace} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{status\} =~ /unknown/i | | | REPLACELASTTIMEFORMAT | Define the date format (default: '%m/%d/%Y') | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status}, %{replace} | %{status} =~ /batteryLow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{replace} =~ /yes/i'). You can use the following variables: %{status}, %{replace} | %{replace} =~ /yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{status\} =~ /batteryLow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{replace\} =~ /yes/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{replace\} =~ /yes/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGTIME | Thresholds | | | @@ -267,8 +267,8 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | CRITICALLINEPHASEPOWER | Thresholds | | | | WARNINGLINEPHASEVOLTAGE | Thresholds | | | | CRITICALLINEPHASEVOLTAGE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_cause} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_cause} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_cause\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_cause\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -278,15 +278,15 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | | WARNINGLOAD | Thresholds | 90 | | | CRITICALLOAD | Thresholds | 95 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /onLine\|rebooting/i'). You can use the following variables: %{status} | %{status} !~ /onLine\|rebooting/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /onLine\|rebooting/i'). You can use the following variables: %\{status\} | %\{status\} !~ /onLine\|rebooting/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -397,7 +397,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -453,15 +453,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | | --replace-lasttime-format | Define the date format (default: '%m/%d/%Y'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{replace} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status}, %{replace} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{replace} =~ /yes/i'). You can use the following variables: %{status}, %{replace} | -| --unknown-battery-pack-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-battery-pack-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-battery-pack-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "OK"'). You can use the following variables: %{status} | -| --unknown-cartridge-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-cartridge-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-cartridge-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "OK"'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{replace\} =~ /yes/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --unknown-battery-pack-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-battery-pack-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-battery-pack-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "OK"'). You can use the following variables: %\{status\} | +| --unknown-cartridge-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-cartridge-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-cartridge-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "OK"'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'temperature', 'time', 'replace-lasttime', 'timeon'. | @@ -470,8 +470,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^frequence\|voltage$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_cause} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_cause} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_cause\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_cause\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence', 'line-frequence', 'line-phase-voltage', 'line-phase-current', 'line-phase-power'. | @@ -480,9 +480,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /onLine\|rebooting/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /onLine\|rebooting/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'frequence'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md index 1dc3493ed9cf..8a242617864a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md @@ -202,11 +202,11 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | %{status} =~ /unknown\|notPresent/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown\|notPresent/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -218,11 +218,11 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -232,7 +232,7 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -241,8 +241,8 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -269,7 +269,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /normal/' \ + --critical-status='%\{status\} !~ /normal/' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -335,7 +335,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -389,9 +389,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'voltage' (V), 'temperature' (C). | @@ -399,9 +399,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence'. | @@ -409,9 +409,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power', 'frequence'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md index db2091ad712f..2c48aa5d39cb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md @@ -223,9 +223,9 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------|:-----------:| -| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{battery\_mode} | %{battery\_mode} =~ /unknown/i | | -| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be WARNING. You can use the following variables: %{battery\_mode} | %{battery_mode} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|ManualBoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostCharging\|MasterBateryTesting/i | | -| CRITICALBATTERYMODE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{battery\_mode} | %{battery\_mode} =~ /ACFailTesting\|ACFail/i | | +| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /unknown/i | | +| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|ManualBoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostCharging\|MasterBateryTesting/i | | +| CRITICALBATTERYMODE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /ACFailTesting\|ACFail/i | | | WARNINGCAPACITY | Thresholds | | | | CRITICALCAPACITY | Thresholds | | | | WARNINGCURRENT | Thresholds | | | @@ -258,8 +258,8 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | CRITICALCOMMUNICATING | Thresholds | | | | WARNINGINSTALLED | Thresholds | | | | CRITICALINSTALLED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | %{installed} != %{communicating} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | %\{installed\} != %\{communicating\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | | | | WARNINGUSEDCAPACITY | Thresholds | | | | CRITICALUSEDCAPACITY | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -269,11 +269,11 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /unknown\|unma\_status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /unknown\|unma\_status} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /warning\|minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /major\|critical/i \|\| %{communication\_status} =~ /interrupt/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /warning\|minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /major\|critical/i \|\| %\{communication_status\} =~ /interrupt/i | | | WARNINGUSEDCAPACITY | Thresholds | | | | CRITICALUSEDCAPACITY | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -285,9 +285,9 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNALARMSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /fail/i | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /low/i | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /high/i | | +| UNKNOWNALARMSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /fail/i | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /low/i | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /high/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -378,7 +378,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -433,9 +433,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Thresholds: voltage (V), current (A), capacity (%), nominal-capacity (Ah) | -| --unknown-battery-mode | Define the conditions to match for the status to be UNKNOWN (default: '%{battery\_mode} =~ /unknown/i'). You can use the following variables: %{battery\_mode} | -| --warning-battery-mode | Define the conditions to match for the status to be WARNING (default: '%{battery\_mode} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|Manual BoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostC harging\|MasterBateryTesting/i'). You can use the following variables: %{battery\_mode} | -| --critical-battery-mode | Define the conditions to match for the status to be CRITICAL (default: '%{battery\_mode} =~ /ACFailTesting\|ACFail/i'). You can use the following variables: %{battery\_mode} | +| --unknown-battery-mode | Define the conditions to match for the status to be UNKNOWN (default: '%\{battery_mode\} =~ /unknown/i'). You can use the following variables: %\{battery_mode\} | +| --warning-battery-mode | Define the conditions to match for the status to be WARNING (default: '%\{battery_mode\} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|Manual BoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostC harging\|MasterBateryTesting/i'). You can use the following variables: %\{battery_mode\} | +| --critical-battery-mode | Define the conditions to match for the status to be CRITICAL (default: '%\{battery_mode\} =~ /ACFailTesting\|ACFail/i'). You can use the following variables: %\{battery_mode\} | @@ -449,9 +449,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{installed} != %{communicating}'). You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{installed\} != %\{communicating\}'). You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | | --warning-* --critical-* | Thresholds. Can be: 'used-capacity', 'installed', 'communicating' | @@ -459,9 +459,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{system\_status} =~ /unknown\|unmanaged\|restricted\|testing\|disabled/i \|\| %{communication\_status} =~ /unknown/i'). You can use the following variables: %{system\_status}, %{communication\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{system\_status} =~ /warning\|minor/i'). You can use the following variables: %{system\_status}, %{communication\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{system\_status} =~ /major\|critical/i \|\| %{communication\_status} =~ /interrupt/i'). You can use the following variables: %{system\_status}, %{communication\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{system_status\} =~ /unknown\|unmanaged\|restricted\|testing\|disabled/i \|\| %\{communication_status\} =~ /unknown/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{system_status\} =~ /warning\|minor/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{system_status\} =~ /major\|critical/i \|\| %\{communication_status\} =~ /interrupt/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | | --warning-* --critical-* | Thresholds: voltage (V), current (A), used-capacity (%) | @@ -469,9 +469,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN (default: '%{alarm\_status} =~ /fail/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING (default: '%{alarm\_status} =~ /low/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm\_status} =~ /high/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{alarm_status\} =~ /fail/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING (default: '%\{alarm_status\} =~ /low/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm_status\} =~ /high/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | | --warning-temperature --critical-temperature | Thresholds: temperature (C) | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md index 39f5f800a668..876dcd7a7b0e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md @@ -259,16 +259,16 @@ yum install centreon-plugin-Hardware-Ups-Himoinsa-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGALARMSTATUS | Warning threshold for alarm (default: '%{status} =~ /^alarm/'). Can use special variables like: %{status} | %{status} =~ /^alarm/ | | -| CRITICALALARMSTATUS | Critical threshold for alarm. Can use special variables like: %{status} | | | -| WARNINGCLOSEDCOMMUTATOR | Warning threshold for commutator currently closed. Can use special variables like: %{status} | | | -| CRITICALCLOSEDCOMMUTATOR | Critical threshold for commutator currently closed. Can use special variables like: %{status} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%{status} =~ /mains/i' | | | -| WARNINGMODESTATUS | Warning threshold for commutator mode status. Can use special variables like: %{status} | | | -| CRITICALMODESTATUS | Critical threshold for commutator mode status. Can use special variables like: %{status} | | | -| WARNINGMOTORSTATUS | Warning threshold for motor status. Can use special variables like: %{status} | | | -| CRITICALMOTORSTATUS | Critical threshold for motor status. Can use special variables like: %{status} | | | -| WARNINGTRANSFERPUMPSTATUS | Warning threshold for transfer pump status. Can use special variables like: %{status} | | | -| CRITICALTRANSFERPUMPSTATUS | Critical threshold for transfer pump status. Can use special variables like: %{status} | | | +| WARNINGALARMSTATUS | Warning threshold for alarm (default: '%\{status\} =~ /^alarm/'). Can use special variables like: %\{status\} | %\{status\} =~ /^alarm/ | | +| CRITICALALARMSTATUS | Critical threshold for alarm. Can use special variables like: %\{status\} | | | +| WARNINGCLOSEDCOMMUTATOR | Warning threshold for commutator currently closed. Can use special variables like: %\{status\} | | | +| CRITICALCLOSEDCOMMUTATOR | Critical threshold for commutator currently closed. Can use special variables like: %\{status\} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%\{status\} =~ /mains/i' | | | +| WARNINGMODESTATUS | Warning threshold for commutator mode status. Can use special variables like: %\{status\} | | | +| CRITICALMODESTATUS | Critical threshold for commutator mode status. Can use special variables like: %\{status\} | | | +| WARNINGMOTORSTATUS | Warning threshold for motor status. Can use special variables like: %\{status\} | | | +| CRITICALMOTORSTATUS | Critical threshold for motor status. Can use special variables like: %\{status\} | | | +| WARNINGTRANSFERPUMPSTATUS | Warning threshold for transfer pump status. Can use special variables like: %\{status\} | | | +| CRITICALTRANSFERPUMPSTATUS | Critical threshold for transfer pump status. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -403,7 +403,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,16 +479,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-alarm-status | Warning threshold for alarm (default: '%{status} =~ /^alarm/'). Can use special variables like: %{status} | -| --critical-alarm-status | Critical threshold for alarm. Can use special variables like: %{status} | -| --warning-motor-status | Warning threshold for motor status. Can use special variables like: %{status} | -| --critical-motor-status | Critical threshold for motor status. Can use special variables like: %{status} | -| --warning-mode-status | Warning threshold for commutator mode status. Can use special variables like: %{status} | -| --critical-mode-status | Critical threshold for commutator mode status. Can use special variables like: %{status} | -| --warning-closed-commutator | Warning threshold for commutator currently closed. Can use special variables like: %{status} | -| --critical-closed-commutator | Critical threshold for commutator currently closed. Can use special variables like: %{status} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%{status} =~ /mains/i' | -| --warning-transfer-pump-status | Warning threshold for transfer pump status. Can use special variables like: %{status} | -| --critical-transfer-pump-status | Critical threshold for transfer pump status. Can use special variables like: %{status} | +| --warning-alarm-status | Warning threshold for alarm (default: '%\{status\} =~ /^alarm/'). Can use special variables like: %\{status\} | +| --critical-alarm-status | Critical threshold for alarm. Can use special variables like: %\{status\} | +| --warning-motor-status | Warning threshold for motor status. Can use special variables like: %\{status\} | +| --critical-motor-status | Critical threshold for motor status. Can use special variables like: %\{status\} | +| --warning-mode-status | Warning threshold for commutator mode status. Can use special variables like: %\{status\} | +| --critical-mode-status | Critical threshold for commutator mode status. Can use special variables like: %\{status\} | +| --warning-closed-commutator | Warning threshold for commutator currently closed. Can use special variables like: %\{status\} | +| --critical-closed-commutator | Critical threshold for commutator currently closed. Can use special variables like: %\{status\} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%\{status\} =~ /mains/i' | +| --warning-transfer-pump-status | Warning threshold for transfer pump status. Can use special variables like: %\{status\} | +| --critical-transfer-pump-status | Critical threshold for transfer pump status. Can use special variables like: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md index 57cf1f249a4b..e443e464b1ec 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md @@ -213,15 +213,15 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | %{status} =~ /batteryDischarging/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDischarging/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -261,7 +261,7 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| UNKNOWNSOURCE | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{source} | | | +| UNKNOWNSOURCE | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{source\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -270,8 +270,8 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSOURCE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{source} | %{source} !~ /normal/i | | -| WARNINGSOURCE | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{source} | | | +| CRITICALSOURCE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{source\} | %\{source\} !~ /normal/i | | +| WARNINGSOURCE | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{source\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -362,7 +362,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -417,9 +417,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V). | @@ -441,9 +441,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{source}. | -| --warning-source | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{source}. | -| --critical-source | Define the conditions to match for the status to be CRITICAL (default: '%{source} !~ /normal/i'). You can use the following variables: %{source}. | +| --unknown-source | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{source\}. | +| --warning-source | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{source\}. | +| --critical-source | Define the conditions to match for the status to be CRITICAL (default: '%\{source\} !~ /normal/i'). You can use the following variables: %\{source\}. | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md index 637fbbbe9351..26e78d91e6d4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md @@ -234,8 +234,8 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| | WARNINGALARMSCURRENT | Thresholds | | | | CRITICALALARMSCURRENT | Thresholds | | | -| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneWarning\|aborted/ | | -| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneError/ | | +| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneWarning\|aborted/ | | +| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneError/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -243,13 +243,13 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNING | Thresholds | | | | CRITICAL | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -306,9 +306,9 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /other/') You can use the following variables: %{status} | %{status} =~ /other/ | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | %{status} =~ /bypass\|battery\|booster\|reducer/ | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /none/') You can use the following variables: %{status} | %{status} =~ /none/ | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | %\{status\} =~ /other/ | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | %\{status\} =~ /bypass\|battery\|booster\|reducer/ | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | %\{status\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -394,7 +394,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -449,9 +449,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --display-alarms | Display alarms in verbose output. | -| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{detail} | -| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | -| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | +| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{detail\} | +| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | +| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | | --warning-* --critical-* | Thresholds. Can be: 'alarms-current'. | @@ -459,9 +459,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -496,9 +496,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /other/') You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /none/') You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md index 90653e7fe3c4..66a8bdf97e90 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md @@ -359,7 +359,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -432,8 +432,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* | Warning threshold. Can be: 'frequence', 'voltage', 'current'. | | --critical-* | Critical threshold. Can be: 'frequence', 'voltage', 'current'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{badstatus}, %{failcause} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{badstatus} =~ /yes/'). You can use the following variables: %{badstatus}, %{failcause} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{badstatus\}, %\{failcause\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{badstatus\} =~ /yes/'). You can use the following variables: %\{badstatus\}, %\{failcause\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md index 5d705ac66797..236ef3eaee11 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md @@ -202,11 +202,11 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | %{status} =~ /unknown\|notPresent/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown\|notPresent/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -218,11 +218,11 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -232,7 +232,7 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -241,8 +241,8 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -269,7 +269,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /normal/' \ + --critical-status='%\{status\} !~ /normal/' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -335,7 +335,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -389,9 +389,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'voltage' (V), 'temperature' (C). | @@ -399,9 +399,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence'. | @@ -409,9 +409,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power', 'frequence'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md index 0b7f0384de37..e13b2d05c950 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md @@ -202,8 +202,8 @@ yum install centreon-plugin-Hardware-Ups-Phoenixtec-Snmp | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -228,8 +228,8 @@ yum install centreon-plugin-Hardware-Ups-Phoenixtec-Snmp | CRITICALFREQUENCE | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBypass/i'). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /onBattery/i'). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBypass/i'). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /onBattery/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | @@ -311,7 +311,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -366,9 +366,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'temperature' (C), 'voltage' (V). | @@ -383,9 +383,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBypass/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /onBattery/i'). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBypass/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /onBattery/i'). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md index f5650371675c..6a450f650952 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md @@ -252,15 +252,15 @@ yum install centreon-plugin-Hardware-Ups-Powerware-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCHARGEREMAINING | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | WARNINGCURRENT | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCURRENT | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryDischarging/i'). You can use the following variables: %{status} | %{status} =~ /batteryDischarging/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryDischarging/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDischarging/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALVOLTAGE | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -406,7 +406,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -482,9 +482,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryDischarging/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryDischarging/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md index d4c18622b310..926427f2c139 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md @@ -209,15 +209,15 @@ yum install centreon-plugin-Hardware-Ups-Riello-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -246,8 +246,8 @@ yum install centreon-plugin-Hardware-Ups-Riello-Snmp | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -328,7 +328,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -389,9 +389,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -407,9 +407,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------| | --ignore-zero-counters | Ignore counters equals to 0. | -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md index c8f30f4b3374..8e104ea48b21 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md @@ -212,15 +212,15 @@ yum install centreon-plugin-Hardware-Ups-Socomec-Netvision-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted\|failure/i'). You can use the following variables: %{status} | %{status} =~ /depleted\|failure/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted\|failure/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted\|failure/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -245,13 +245,13 @@ yum install centreon-plugin-Hardware-Ups-Socomec-Netvision-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -343,7 +343,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -404,9 +404,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted\|failure/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted\|failure/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -422,9 +422,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| | --ignore-zero-counters | Ignore counters equals to 0. | -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md index d792184459f5..923806954556 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md @@ -214,8 +214,8 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| | WARNINGALARMSCURRENT | Thresholds | | | | CRITICALALARMSCURRENT | Thresholds | | | -| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneWarning\|aborted/ | | -| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneError/ | | +| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneWarning\|aborted/ | | +| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneError/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -223,13 +223,13 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNING | Thresholds | | | | CRITICAL | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -275,9 +275,9 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /other/') You can use the following variables: %{status} | %{status} =~ /other/ | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | %{status} =~ /bypass\|battery\|booster\|reducer/ | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /none/') You can use the following variables: %{status} | %{status} =~ /none/ | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | %\{status\} =~ /other/ | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | %\{status\} =~ /bypass\|battery\|booster\|reducer/ | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | %\{status\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -356,7 +356,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -411,9 +411,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --display-alarms | Display alarms in verbose output. | -| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{detail} | -| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | -| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | +| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{detail\} | +| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | +| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | | --warning-* --critical-* | Thresholds. Can be: 'alarms-current'. | @@ -421,9 +421,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -449,9 +449,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /other/') You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /none/') You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md index e727e57638c1..e303b1ca2fed 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md @@ -295,7 +295,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md index f0ba6dbb1ea0..b581be13dbea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md @@ -302,7 +302,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-3com-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-3com-snmp.md index 50c195ae8cae..71526c2d2167 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-3com-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-3com-snmp.md @@ -285,7 +285,7 @@ yum install centreon-plugin-Network-3com-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -374,7 +374,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -476,9 +476,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-acmepacket-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-acmepacket-snmp.md index 3a044548f971..96ad9ead7473 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-acmepacket-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-acmepacket-snmp.md @@ -347,8 +347,8 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -460,7 +460,7 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| | FILTERNAME | Filter by SIP name (can be a regexp) | | | -| STATUS | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %{status} | | | +| STATUS | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %\{status\} | | | | WARNINGASR | Warning threshold | | | | CRITICALASR | Critical threshold | | | | WARNINGINSESSIONSRATE | Warning threshold | | | @@ -469,7 +469,7 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALLATENCY | Critical threshold | | | | WARNINGOUTSESSIONSRATE | Warning threshold | | | | CRITICALOUTSESSIONSRATE | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -489,8 +489,8 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALLICENSEUSAGE | Critical threshold | | | | WARNINGMEMORYUSAGE | Warning threshold | | | | CRITICALMEMORYUSAGE | Critical threshold | | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{replication\_state} | %{replication\_state} =~ /outOfService/i | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{replication\_state} | | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{replication_state\} | %\{replication_state\} =~ /outOfService/i | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{replication_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -515,7 +515,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} =~ /outOfService|constraintsViolation|inServiceTimedOut/i' \ + --critical-status='%\{status\} =~ /outOfService|constraintsViolation|inServiceTimedOut/i' \ --warning-in-sessions-rate='' \ --critical-in-sessions-rate='' \ --warning-out-sessions-rate='' \ @@ -589,7 +589,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -684,9 +684,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -787,8 +787,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i'). You can use the following variables: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i'). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'in-sessions-rate', 'out-sessions-rate', 'latency', 'asr'. | | --critical-* | Critical threshold. Can be: 'in-sessions-rate', 'out-sessions-rate', 'latency', 'asr'. | | --filter-name | Filter by SIP name (can be a regexp). | @@ -799,8 +799,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | -| --warning-replication-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{replication\_state} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%{replication\_state} =~ /outOfService/i'). You can use the following variables: %{replication\_state} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{replication_state\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%\{replication_state\} =~ /outOfService/i'). You can use the following variables: %\{replication_state\} | | --warning-* | Warning threshold. Can be: 'license-usage' (%), 'memory-usage' (%), 'cpu-load' (%), 'health-score' (%), 'current-sessions', 'current-calls'. | | --critical-* | Critical threshold. Can be: 'license-usage' (%), 'memory-usage' (%), 'cpu-load' (%), 'health-score' (%), 'current-sessions', 'current-calls'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md index 4ffa2fbaf581..ab1a83be6822 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Network-Adva-Fsp150-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: {description}, %{object}, %{severity}, %{type}, %{label}, %{since} | %{severity} eq "serviceAffecting" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{label}, %{since} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} eq "serviceAffecting" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -247,8 +247,8 @@ yum install centreon-plugin-Network-Adva-Fsp150-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --use-new-perfdata --verbose --no-skipped-counters | | @@ -284,7 +284,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{severity} eq "serviceAffecting"' \ + --critical-status='%\{severity\} eq "serviceAffecting"' \ --verbose ``` @@ -344,7 +344,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -410,8 +410,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{label}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} eq "serviceAffecting"'). You can use the following variables: {description}, %{object}, %{severity}, %{type}, %{label}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} eq "serviceAffecting"'). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | @@ -450,9 +450,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md index cd59a617dd5c..599e7d4c87bc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md @@ -235,8 +235,8 @@ yum install centreon-plugin-Network-Adva-Fsp3000-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning\|minor/i') You can use the following variables: %{severity}, %{type}, %{label}, %{since} | %{severity} =~ /warning\|minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{type}, %{label}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning\|minor/i') You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} =~ /warning\|minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -259,8 +259,8 @@ yum install centreon-plugin-Network-Adva-Fsp3000-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALOPERDOWN | Thresholds | | | @@ -335,7 +335,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-optical \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-traffic-in='' \ --critical-traffic-in='' \ --warning-traffic-out='' \ @@ -420,7 +420,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -486,8 +486,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning\|minor/i') You can use the following variables: %{severity}, %{type}, %{label}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{type}, %{label}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning\|minor/i') You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | @@ -511,9 +511,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-status | Check interface status. | | --add-traffic | Check interface traffic. | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'laser-temp', 'input-power', 'output-power', 'traffic-in', 'traffic-out'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --interface | Set the interface (number expected) example: 1,2,... (empty means 'check all interfaces'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aerohive-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aerohive-snmp.md index 3a77906156ac..d2e6ed4e732a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aerohive-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aerohive-snmp.md @@ -225,7 +225,7 @@ yum install centreon-plugin-Network-Aerohive-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -310,7 +310,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -394,9 +394,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-allied-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-allied-snmp.md index 4c493afabc43..117d1d801b55 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-allied-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-allied-snmp.md @@ -266,8 +266,8 @@ yum install centreon-plugin-Network-Allied-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -357,7 +357,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -450,9 +450,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md index 5f11ef854ad1..24729859dfcb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md @@ -245,8 +245,8 @@ yum install centreon-plugin-Network-Alvarion-Breezeaccess-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -362,7 +362,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -436,9 +436,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md index 8d51428800db..60702776bf36 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md @@ -289,8 +289,8 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose --no-skipped-counters | | @@ -310,14 +310,14 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| | WARNINGCPUUTILIZATION | Thresholds | | | | CRITICALCPUUTILIZATION | Thresholds | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i'). You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | %{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i'). You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | | | | WARNINGMEMBERSTOTAL | Thresholds | | | | CRITICALMEMBERSTOTAL | Thresholds | | | | WARNINGMEMORYUSAGEPRCT | Thresholds | | | | CRITICALMEMORYUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /no\_split/i'). You can use the following variables: %{status} | %{status} !~ /no\_split/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /no\_split/i'). You can use the following variables: %\{status\} | %\{status\} !~ /no\_split/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -325,20 +325,20 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------|:-----------:| -| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{config\_sync} | | | -| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{config\_sync} | | | +| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{config_sync\} | | | +| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{config_sync\} | | | | WARNINGISLPACKETSIN | Thresholds | | | | CRITICALISLPACKETSIN | Thresholds | | | | WARNINGISLPACKETSOUT | Thresholds | | | | CRITICALISLPACKETSOUT | Thresholds | | | -| CRITICALISLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{isl\_status} =~ /outSync/'). You can use the following variables: %{isl\_status} | %{isl\_status} =~ /outSync/ | | -| WARNINGISLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{isl\_status} | | | +| CRITICALISLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{isl_status\} =~ /outSync/'). You can use the following variables: %\{isl_status\} | %\{isl_status\} =~ /outSync/ | | +| WARNINGISLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{isl_status\} | | | | WARNINGKEEPALIVEPACKETSIN | Thresholds | | | | CRITICALKEEPALIVEPACKETSIN | Thresholds | | | | WARNINGKEEPALIVEPACKETSOUT | Thresholds | | | | CRITICALKEEPALIVEPACKETSOUT | Thresholds | | | -| CRITICALKEEPALIVESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{keepalive\_status} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %{keepalive\_status} | %{keepalive\_status} =~ /outofSyncEstablished\|failed/ | | -| WARNINGKEEPALIVESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{keepalive\_status} | | | +| CRITICALKEEPALIVESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{keepalive_status\} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %\{keepalive_status\} | %\{keepalive_status\} =~ /outofSyncEstablished\|failed/ | | +| WARNINGKEEPALIVESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{keepalive_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -438,7 +438,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -532,9 +532,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -580,12 +580,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /no\_split/i'). You can use the following variables: %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i'). You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /no\_split/i'). You can use the following variables: %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i'). You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total', 'memory-usage-prct', 'cpu-utilization'. | @@ -605,15 +605,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{config\_sync} | -| --warning-device-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{config\_sync} | -| --critical-device-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{config\_sync} | -| --unknown-isl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{isl\_status} | -| --warning-isl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{isl\_status} | -| --critical-isl-status | Define the conditions to match for the status to be CRITICAL (Default: '%{isl\_status} =~ /outSync/'). You can use the following variables: %{isl\_status} | -| --unknown-keepalive-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{keepalive\_status} | -| --warning-keepalive-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{keepalive\_status} | -| --critical-keepalive-status | Define the conditions to match for the status to be CRITICAL (Default: '%{keepalive\_status} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %{keepalive\_status} | +| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{config_sync\} | +| --warning-device-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{config_sync\} | +| --critical-device-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{config_sync\} | +| --unknown-isl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{isl_status\} | +| --warning-isl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{isl_status\} | +| --critical-isl-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{isl_status\} =~ /outSync/'). You can use the following variables: %\{isl_status\} | +| --unknown-keepalive-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{keepalive_status\} | +| --warning-keepalive-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{keepalive_status\} | +| --critical-keepalive-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{keepalive_status\} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %\{keepalive_status\} | | --warning-* --critical-* | Thresholds. Can be: 'isl-packets-in', 'isl-packets-out', 'keepalive-packets-in', 'keepalive-packets-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md index 58e7478ce400..43159282981c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md @@ -308,8 +308,8 @@ yum install centreon-plugin-Network-Aruba-Cppm-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -469,7 +469,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -562,9 +562,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md index bd2dee8aa96a..5ca1d702cdee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md @@ -203,8 +203,8 @@ yum install centreon-plugin-Network-Aruba-Instant-Snmp | CRITICALMEMUSAGEFREE | Thresholds | | | | WARNINGMEMUSAGEPRCT | Thresholds | | | | CRITICALMEMUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -213,8 +213,8 @@ yum install centreon-plugin-Network-Aruba-Instant-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter SSID name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /enable/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /enable/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /enable/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /enable/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -239,7 +239,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /up/i' \ + --critical-status='%\{status\} !~ /up/i' \ --warning-cpu='' \ --critical-cpu='' \ --warning-clients='' \ @@ -304,7 +304,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -360,8 +360,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^cpu$' | | --filter-name | Filter access point name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-ap', 'cpu', 'clients', 'mem-usage' (B), 'mem-usage-free' (B), 'mem-usage-prct' (%). | @@ -370,8 +370,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter SSID name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /enable/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /enable/i'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md index 84cc68e9a621..139b351dd592 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md @@ -193,8 +193,8 @@ yum install centreon-plugin-Network-Aruba-Orchestrator-Restapi | CRITICALSEVERITYMAJOR | Thresholds | | | | WARNINGSEVERITYMINOR | Thresholds | | | | CRITICALSEVERITYMINOR | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | %{severity} =~ /minor\|warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | %{severity} =~ /major\|critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /minor\|warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /major\|critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -202,13 +202,13 @@ yum install centreon-plugin-Network-Aruba-Orchestrator-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{hostname} | %{state} =~ /unknown\|unreachable/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{hostname\} | %\{state\} =~ /unknown\|unreachable/i | | | FILTERHOSTNAME | Filter appliances by hostname | | | | FILTERGROUP | Filter appliances by group | | | | WARNINGAPPLIANCESDETECTED | Thresholds | | | | CRITICALAPPLIANCESDETECTED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{hostname} | %{state} =~ /unsupportedVersion\|outOfSynchronization/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{hostname} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{hostname\} | %\{state\} =~ /unsupportedVersion\|outOfSynchronization/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{hostname\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -234,8 +234,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --access-token='XXXX' \ --filter-hostname='' \ --filter-group='' \ - --unknown-status='%{state} =~ /unknown|unreachable/i' \ - --warning-status='%{state} =~ /unsupportedVersion|outOfSynchronization/i' \ + --unknown-status='%\{state\} =~ /unknown|unreachable/i' \ + --warning-status='%\{state\} =~ /unsupportedVersion|outOfSynchronization/i' \ --critical-status='' \ --warning-appliances-detected='' \ --critical-appliances-detected='' \ @@ -299,7 +299,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -342,8 +342,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-hostname | Filter alarms by hostname (can be a regexp). | | --timezone | Set timezone for creation time (default is 'UTC'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/i'). You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/i'). You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | | --warning-* --critical-* | Thresholds. Can be: 'severity-minor', 'severity-warning', 'severity-major', 'severity-critical'. | @@ -354,9 +354,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-hostname | Filter appliances by hostname. | | --filter-group | Filter appliances by group. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{state} =~ /unknown\|unreachable/i'). You can use the following variables: %{state}, %{hostname} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /unsupportedVersion\|outOfSynchronization/i'). You can use the following variables: %{state}, %{hostname} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{hostname} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{state\} =~ /unknown\|unreachable/i'). You can use the following variables: %\{state\}, %\{hostname\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /unsupportedVersion\|outOfSynchronization/i'). You can use the following variables: %\{state\}, %\{hostname\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{hostname\} | | --warning-* --critical-* | Thresholds. Can be: 'appliances-detected'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md index e19fb76d485b..e04cc6269228 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md @@ -335,12 +335,12 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp |:------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTERNAME | Filter interfaces by name (can be a regexp) | | | | FILTEROWNER | Filter interfaces by owner (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{owner} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{owner} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | -| CRITICALTRANSPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | %{transport\_status} =~ /down/i | | -| WARNINGTRANSPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | | | +| CRITICALTRANSPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | %\{transport_status\} =~ /down/i | | +| WARNINGTRANSPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -351,8 +351,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | FILTERNAME | Filter interfaces by name (can be a regexp) | | | | FILTERLOCALADDRESS | Filter interfaces by local address (can be a regexp) | | | | FILTERPEERADDRESS | Filter interfaces by peer address (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -365,8 +365,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | FILTESOURCEADDRESS | Filter interfaces by source address (can be a regexp) | | | | FILTERDESTINATIONADDRESS | Filter interfaces by destination address (can be a regexp) | | | | FILTERTYPE | Filter interfaces by type (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -397,8 +397,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | CRITICALREQUESTSUECONTEXTRELEASETOTAL | Thresholds | | | | WARNINGSESSIONSACTIVE | Thresholds | | | | CRITICALSESSIONSACTIVE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | %{sctp\_status} =~ /down/i \|\| %{s1ap\_status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | %\{sctp_status\} =~ /down/i \|\| %\{s1ap_status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -437,8 +437,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | CRITICALLICENSEUSIMUSAGE | Thresholds | | | | WARNINGLICENSEUSIMUSAGEPRCT | Thresholds | | | | CRITICALLICENSEUSIMUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -568,7 +568,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -666,12 +666,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='transport' | | --filter-name | Filter interfaces by name (can be a regexp). | | --filter-owner | Filter interfaces by owner (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{owner} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{owner} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{name}, %{owner} | -| --unknown-transport-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | -| --warning-transport-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | -| --critical-transport-status | Define the conditions to match for the status to be CRITICAL (default: '%{transport\_status} =~ /down/i'). You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --unknown-transport-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | +| --warning-transport-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | +| --critical-transport-status | Define the conditions to match for the status to be CRITICAL (default: '%\{transport_status\} =~ /down/i'). You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -682,9 +682,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter interfaces by name (can be a regexp). | | --filter-local-address | Filter interfaces by local address (can be a regexp). | | --filter-peer-address | Filter interfaces by peer address (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -695,9 +695,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-source-address | Filter interfaces by source address (can be a regexp). | | --filter-destination-address | Filter interfaces by destination address (can be a regexp). | | --filter-type | Filter interfaces by type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -719,9 +719,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='users' | | --filter-name | Filter interfaces by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{sctp\_status} =~ /down/i \|\| %{s1ap\_status} =~ /down/i'). You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{sctp_status\} =~ /down/i \|\| %\{s1ap_status\} =~ /down/i'). You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'users-connected', 'users-idle', 'sessions-active', 'traffic-in', 'traffic-out', 'requests-ue-context-release-total', 'requests-ue-context-release-radio-lost', 'requests-attach-success', 'requests-attach-success-prct', 'requests-pdn-context-activation', 'requests-pdn-context-activation-prct', 'requests-pdn-context-rej-insufres', 'requests-pdn-context-rej-noapn', 'requests-pdn-context-rej-nosub'. | @@ -730,8 +730,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='users' | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{status\} | | --unit | Select the time unit for the expiration threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | | --warning-* --critical-* | Thresholds. Can be: 'expires', 'license-users-usage', 'license-users-free', 'license-users-usage-prct', 'license-sessions-usage', 'license-sessions-free', 'license-sessions-usage-prct', 'license-usim-usage', 'license-usim-free', 'license-usim-usage-prct'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md index d2e401da9b21..11f4ada9b53a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md @@ -196,8 +196,8 @@ yum install centreon-plugin-Network-Atto-Fibrebridge-Snmp | CRITICALINVALIDCRC | Thresholds | | | | WARNINGSIGNALLOSS | Thresholds | | | | CRITICALSIGNALLOSS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin}, %{status}, %{display} | %{admin} =~ /enabled/ and %{status} !~ /online/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | %\{admin\} =~ /enabled/ and %\{status\} !~ /online/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -291,7 +291,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -360,8 +360,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'invalid-crc', 'signal-loss'. | | --filter-name | Filter name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{admin}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin} =~ /enabled/ and %{status} !~ /online/'). You can use the following variables: %{admin}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin\} =~ /enabled/ and %\{status\} !~ /online/'). You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-audiocodes-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-audiocodes-snmp.md index 465200b7d00e..482dddd532ed 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-audiocodes-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-audiocodes-snmp.md @@ -308,8 +308,8 @@ yum install centreon-plugin-Network-Audiocodes-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -370,8 +370,8 @@ yum install centreon-plugin-Network-Audiocodes-Snmp | CRITICALCOUNTCALLS | Thresholds | | | | WARNINGMAXCALLS | Thresholds | | | | CRITICALMAXCALLS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | %{state} =~ /activated/ and %{alarm} !~ /greenActive/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | %\{state\} =~ /activated/ and %\{alarm\} !~ /greenActive/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -453,7 +453,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -546,9 +546,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -616,8 +616,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-name | Filter by name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /activated/ and %{alarm} !~ /greenActive/i'). You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /activated/ and %\{alarm\} !~ /greenActive/i'). You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | | --warning-* --critical-* | Thresholds. Can be: 'avg-calls', 'max-calls', 'count-calls'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-backbox-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-backbox-restapi.md index d3265917792b..94e4fd37b1d1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-backbox-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-backbox-restapi.md @@ -323,7 +323,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md index 7df6a12790cc..04ce608239f0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md @@ -318,7 +318,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md index fd4f4d1892d5..b7e605b845df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md @@ -321,8 +321,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | IFLTERNAME | Filter by service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /^started$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^started$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -411,8 +411,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -465,8 +465,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | IFLTERNAME | Filter by service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /^started$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^started$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -498,8 +498,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter by VPN name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /^down$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /^down$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -597,7 +597,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -651,8 +651,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^started$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^started$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by service name (can be a regexp). | @@ -723,9 +723,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -773,8 +773,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^started$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^started$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by service name (can be a regexp). | @@ -845,8 +845,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^down$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^down$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by VPN name (can be a regexp). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-beeware-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-beeware-snmp.md index 7311db83c955..c06533dd4d64 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-beeware-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-beeware-snmp.md @@ -199,8 +199,8 @@ yum install centreon-plugin-Network-Beeware-Snmp | CRITICALMEMORY | Critical threshold | | | | WARNINGNBCHILDS | Warning threshold | | | | CRITICALNBCHILDS | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status} | %{status} !~ /running/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\} | %\{status\} !~ /running/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -225,7 +225,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /running/i' \ + --critical-status='%\{status\} !~ /running/i' \ --warning-memory='' \ --critical-memory='' \ --warning-cpu='' \ @@ -288,7 +288,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -334,8 +334,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --snmp-tls-trust-cert | A trusted CA certificate used to verify a remote host's certificate. If you use this option, you must also define --snmp-tls-their-hostname. | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^cpu\|memory$' | | --filter-name | Filter reverse proxy (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{display}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{display\}, %\{status\} | | --warning-* | Warning threshold. Can be: 'cpu', 'memory' (B), 'nbchilds'. | | --critical-* | Critical threshold. Can be: 'cpu', 'memory' (B), 'nbchilds'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md index 99dba4d031b2..f3d3d46cf60b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md @@ -259,8 +259,8 @@ yum install centreon-plugin-Network-Cambium-cnPilot-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Tous les options sont listées [ici](#options-disponibles) | | | @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Cambium-cnPilot-Snmp | CRITICALCLIENTS | | | | | WARNINGINTERFERENCE | Thresholds | | | | CRITICALINTERFERENCE | Thresholds | | | -| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %{status}, %{name} | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{status} eq "expired"'). Can used special variables like: %{status}, %{name} | | | +| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{status\} eq "expired"'). Can used special variables like: %\{status\}, %\{name\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -316,7 +316,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -385,7 +385,7 @@ Les options génériques aux modes sont listées ci-dessous : | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Change storage free perfdata in used: --change-perfdata=free,used,invert() Change storage free perfdata in used: --change-perfdata=used,free,invert() Scale traffic values automaticaly: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Extend perfdata from multiple perfdatas (methods in target are: min, max, average, sum) Syntax: --extend-perfdata-group=searchlabel,newlabel,target\[,\[newuom\],\[m in\],\[max\]\] Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -439,8 +439,8 @@ Les options spécifiques aux modes sont listées ci-dessus : | Option | Description | Type | |:-----------------------------|:------------------------------------------------------------------------------------------|:-----| | --filter-ap | Filter on one or several AP. | Mode | -| --warning-connection-status | Set warning threshold for status. Can used special variables like: %{status}, %{name} | Mode | -| --critical-connection-status | Set critical threshold for status. Can used special variables like: %{status}, %{name} | Mode | +| --warning-connection-status | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | +| --critical-connection-status | Set critical threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | @@ -476,9 +476,9 @@ Les options spécifiques aux modes sont listées ci-dessus : | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Set warning threshold for status. Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Set warning threshold for status. Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'counter'). | Mode | @@ -528,8 +528,8 @@ Les options spécifiques aux modes sont listées ci-dessus : | --statefile-cipher | Cipher to encrypt cache (Default: 'AES'). | Retention | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | Mode | | --filter-name | Filter interface by MACAdress | Mode | -| --warning-status | Set warning threshold for status. Can used special variables like: %{status}, %{name} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{status} eq "expired"'). Can used special variables like: %{status}, %{name} | Mode | +| --warning-status | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{status\} eq "expired"'). Can used special variables like: %\{status\}, %\{name\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'clients-connected', 'noise-floor', 'interference', 'traffic-in', 'traffic-out'. | Mode | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md index 6e4bbe877436..2393832a6ac4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md @@ -261,8 +261,8 @@ yum install centreon-plugin-Network-Cambium-Epmp-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -270,9 +270,9 @@ yum install centreon-plugin-Network-Cambium-Epmp-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /validation fail\|not provided/i'). You can use the following variables: %{status} | %{status} =~ /validation fail\|not provided/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /not valid/i'). You can use the following variables: %{status} | %{status} =~ /not valid/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /validation fail\|not provided/i'). You can use the following variables: %\{status\} | %\{status\} =~ /validation fail\|not provided/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /not valid/i'). You can use the following variables: %\{status\} | %\{status\} =~ /not valid/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -310,7 +310,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -383,7 +383,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -473,9 +473,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -501,9 +501,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /validation fail\|not provided/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /not valid/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /validation fail\|not provided/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /not valid/i'). You can use the following variables: %\{status\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md index 1b041875be74..65cc4b5627b5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md @@ -219,8 +219,8 @@ yum install centreon-plugin-Network-Chapsvision-Crossing-Snmp | CRITICALDATABASELASTUPDATE | Thresholds | | | | WARNINGLICENSEEXPIRES | Thresholds | | | | CRITICALLICENSEEXPIRES | Thresholds | | | -| WARNINGVERSION | Define the conditions the version must match for the returned status to be WARNING. You can use the following variables: %{version}, %{name} | | | -| CRITICALVERSION | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %{version}, %{name} | | | +| WARNINGVERSION | Define the conditions the version must match for the returned status to be WARNING. You can use the following variables: %\{version\}, %\{name\} | | | +| CRITICALVERSION | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %\{version\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -264,8 +264,8 @@ yum install centreon-plugin-Network-Chapsvision-Crossing-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -355,7 +355,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -412,9 +412,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='version' | | --antivirus1-date-format | Define the date format for the first antivirus (default: '%Y/%m/%d'). | | --antivirus2-date-format | Define the date format for the second antivirus (default: '%Y/%m/%d'). | -| --unknown-version | Define the conditions the version must match for the status to be UNKNOWN. You can use the following variables: %{version}, %{name} | -| --warning-version | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %{version}, %{name} | -| --critical-version | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %{version}, %{name} | +| --unknown-version | Define the conditions the version must match for the status to be UNKNOWN. You can use the following variables: %\{version\}, %\{name\} | +| --warning-version | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %\{version\}, %\{name\} | +| --critical-version | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %\{version\}, %\{name\} | | --unit | Select the unit for the expired license threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'license-expires', 'database-last-update'. | @@ -443,9 +443,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md index 7066a439b16b..e636f0816945 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md @@ -180,8 +180,8 @@ yum install centreon-plugin-Network-Cisco-Apic-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHEALTH | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | | | -| CRITICALHEALTH | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | | | +| WARNINGHEALTH | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | | | +| CRITICALHEALTH | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -203,8 +203,8 @@ yum install centreon-plugin-Network-Cisco-Apic-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHEALTH | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | | | -| CRITICALHEALTH | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | | | +| WARNINGHEALTH | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | | | +| CRITICALHEALTH | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -291,7 +291,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -342,8 +342,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-health | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | -| --critical-health | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | +| --warning-health | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | +| --critical-health | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | @@ -360,8 +360,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-tenant | Regexp filter on the tenant name | -| --warning-health | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | -| --critical-health | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | +| --warning-health | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | +| --critical-health | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md index e282a9d459fb..4d3eac67646d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md @@ -234,8 +234,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | CRITICALPHONESREJECTED | Thresholds | | | | WARNINGPHONESUNREGISTERED | Thresholds | | | | CRITICALPHONESUNREGISTERED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/'). You can use the following variables: %{status}, %{display} | %{status} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -243,8 +243,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALPARTIALLYREGISTERED | Warning threshold | | | | CRITICALTOTALPARTIALLYREGISTERED | Critical threshold | | | | WARNINGTOTALREGISTERED | Warning threshold | | | @@ -262,8 +262,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALPARTIALLYREGISTERED | Warning threshold | | | | CRITICALTOTALPARTIALLYREGISTERED | Critical threshold | | | | WARNINGTOTALREGISTERED | Warning threshold | | | @@ -281,8 +281,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{name}, %{description} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{description} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{name\}, %\{description\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{description\} | | | | WARNINGTOTALPARTIALLYREGISTERED | Thresholds | | | | CRITICALTOTALPARTIALLYREGISTERED | Thresholds | | | | WARNINGTOTALREGISTERED | Thresholds | | | @@ -316,7 +316,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{status} !~ /^registered/' \ + --critical-status='%\{status\} !~ /^registered/' \ --warning-total-registered='' \ --critical-total-registered='' \ --warning-total-unregistered='' \ @@ -384,7 +384,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -439,8 +439,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='phone' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'phones-registered', 'phones-unregistered', 'phones-rejected', 'gateways-registered', 'gateways-unregistered', 'gateways-rejected', 'mediadevices-registered', 'mediadevices-unregistered', 'mediadevices-rejected'. | @@ -449,8 +449,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. | | --critical-* | Critical threshold. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | @@ -460,8 +460,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. | | --critical-* | Critical threshold. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | @@ -473,8 +473,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter phone by name (can be a regexp). | | --filter-description | Filter phone by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{description} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{name}, %{description} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{description\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{name\}, %\{description\} | | --warning-* --critical-* | Thresholds. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md index f7327e2256c8..5635cddd68e8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md @@ -279,7 +279,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md index 6763d3a87df4..ebf708862f97 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md @@ -278,7 +278,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md index a1c0f9010388..34b533dd6667 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md @@ -176,7 +176,7 @@ yum install centreon-plugin-Network-Cisco-Esa-Xmlapi | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| -| UNKNOWNHTTPSTATUS | Threshold unknown for http response code (default: '%{http_code} < 200 or %{http_code} >= 300') | | | +| UNKNOWNHTTPSTATUS | Threshold unknown for http response code (default: '%\{http_code\} < 200 or %\{http_code\} >= 300') | | | | WARNINGCONNECTIONSIN | Warning threshold for 'connections-in' | | | | CRITICALCONNECTIONSIN | Critical threshold for 'connections-in' | | | | WARNINGCONNECTIONSOUT | Warning threshold for 'connections-out' | | | @@ -203,8 +203,8 @@ yum install centreon-plugin-Network-Cisco-Esa-Xmlapi | CRITICALQUEUEDISK | Critical threshold for 'queuedisk' (%) | | | | WARNINGRESOURCECONSERVATION | Warning threshold for 'resource-conservation' | | | | CRITICALRESOURCECONSERVATION | Critical threshold for 'resource-conservation' | | | -| CRITICALSYSTEMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system_status} | %{system\_status} !~ /online/i | | -| WARNINGSYSTEMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{system_status} | | | +| CRITICALSYSTEMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\} | %\{system_status\} !~ /online/i | | +| WARNINGSYSTEMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{system_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -233,7 +233,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-http-status='' \ --critical-http-status='' \ --warning-system-status='' \ - --critical-system-status='%{system_status} !~ /online/i' \ + --critical-system-status='%\{system_status\} !~ /online/i' \ --warning-memory='' \ --critical-memory='' \ --warning-cpu-total='' \ @@ -313,7 +313,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -358,11 +358,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --username | Specify the username for authentication | | --password | Specify the password for authentication | | --timeout | Threshold for HTTP timeout | -| --unknown-http-status | Threshold unknown for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-http-status | Threshold unknown for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-http-status | Warning threshold for http response code | | --critical-http-status | Critical threshold for http response code | -| --warning-system-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{system\_status} | -| --critical-system-status | Define the conditions to match for the status to be CRITICAL (default: '%{system\_status} !~ /online/i'). You can use the following variables: %{system\_status} | +| --warning-system-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{system_status\} | +| --critical-system-status | Define the conditions to match for the status to be CRITICAL (default: '%\{system_status\} !~ /online/i'). You can use the following variables: %\{system_status\} | | --warning-* --critical-* | Warning threshold. Can be: 'memory' (%), 'cpu-total' (%), 'diskio' (%), 'log' (%), 'resource-conservation', 'connections-in', 'connections-out', 'queue-active-recipients', 'messages-quarantine', 'messages-workqueue', 'queuedisk' (%), 'messages-received'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md index 02e9240d2b2a..8f9dbd55d0de 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md @@ -170,7 +170,7 @@ yum install centreon-plugin-Network-Cisco-Firepower-Fmc-Restapi |:----------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | FILTERDOMAINNAME | Filter devices by domain name (can be a regexp) | | | | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| UNKNOWNDEVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNDEVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGDEVICESSTATUSBLACK | Warning thresholds for 'devices-status-black' | | | | CRITICALDEVICESSTATUSBLACK | Critical thresholds for 'devices-status-black' | | | | WARNINGDEVICESSTATUSBLUE | Warning thresholds for 'devices-status-blue' | | | @@ -181,8 +181,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Fmc-Restapi | CRITICALDEVICESSTATUSRED | Critical thresholds for 'devices-status-red' | | | | WARNINGDEVICESSTATUSYELLOW | Warning thresholds for 'devices-status-yellow' | | | | CRITICALDEVICESSTATUSYELLOW | Critical thresholds for 'devices-status-yellow' | | | -| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/i | | -| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /red\|black/i | | +| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/i | | +| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red\|black/i | | | WARNINGDEVICESTOTAL | Warning thresholds for 'devices-total' | | | | CRITICALDEVICESTOTAL | Critical thresholds for 'devices-total' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -224,8 +224,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-devices-status-yellow='' \ --critical-devices-status-yellow='' \ --unknown-device-status='' \ - --warning-device-status='%{status} =~ /yellow/i' \ - --critical-device-status='%{status} =~ /red|black/i' \ + --warning-device-status='%\{status\} =~ /yellow/i' \ + --critical-device-status='%\{status\} =~ /red|black/i' \ --verbose ``` @@ -290,7 +290,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -336,9 +336,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-domain-name | Filter devices by domain name (can be a regexp). | | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-device-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i'). You can use the following variables: %{status}, %{name} | -| --critical-device-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red\|black/i'). You can use the following variables: %{status}, %{name} | +| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red\|black/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'devices-total', 'devices-status-green', 'devices-status-black', 'devices-status-blue', 'devices-status-red', 'devices-status-yellow'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md index f65f6e1db8ed..01f2bb64473d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md @@ -286,8 +286,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Snmp | CRITICALFAULTSMINOR | Critical threshold for 'faults-info' | | | | WARNINGFAULTSTOTAL | Warning threshold for 'faults-total' | | | | CRITICALFAULTSTOTAL | Critical threshold for 'faults-total' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{acknowledged}, %{since} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{since} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{acknowledged\}, %\{since\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{since\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -318,8 +318,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Snmp | CRITICALOUTERROR | Critical threshold for 'out-error' | | | | WARNINGOUTTRAFFIC | Warning threshold for 'out-traffic' | | | | CRITICALOUTTRAFFIC | Critical threshold for 'out-traffic' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -421,7 +421,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -495,8 +495,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/). You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{acknowledged}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{acknowledged\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | | --warning-* --critical-* | Thresholds. Can be: 'faults-total', 'faults-critical', 'faults-major', 'faults-warning', 'faults-minor', 'faults-info'. | @@ -538,9 +538,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md index 174fdc260e10..9d048fae323d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md @@ -275,7 +275,7 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | | WARNINGDNSREQUESTSOUTSTANDING | Warning threshold | | | | CRITICALDNSREQUESTSOUTSTANDING | Warning threshold | | | | WARNINGDNSREQUESTSPENDING | Warning threshold | | | @@ -284,8 +284,8 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | CRITICALFDOPENED | Warning threshold | | | | WARNINGMESSAGESWORKQUEUE | Warning threshold | | | | CRITICALMESSAGESWORKQUEUE | Warning threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{resource\_conservation} =~ /memoryShortage\|queueSpaceShortage/i \|\| %{queue\_status} =~ /queueSpaceShortage/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{resource\_conservation} =~ /queueFull/i \|\| %{queue\_status} =~ /queueFull/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{resource_conservation\} =~ /memoryShortage\|queueSpaceShortage/i \|\| %\{queue_status\} =~ /queueSpaceShortage/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{resource_conservation\} =~ /queueFull/i \|\| %\{queue_status\} =~ /queueFull/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | | WARNINGTHREADSMAIL | Warning threshold | | | | CRITICALTHREADSMAIL | Warning threshold | | | | WARNINGTIMEEXPIRATION | Warning threshold | | | @@ -362,7 +362,7 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -453,7 +453,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -539,9 +539,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{queue\_status}, %{resource\_conservation} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{resource\_conservation} =~ /memoryShortage\|queueSpaceShortage/i \|\| %{queue\_status} =~ /queueSpaceShortage/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{resource\_conservation} =~ /queueFull/i \|\| %{queue\_status} =~ /queueFull/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{resource_conservation\} =~ /memoryShortage\|queueSpaceShortage/i \|\| %\{queue_status\} =~ /queueSpaceShortage/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{resource_conservation\} =~ /queueFull/i \|\| %\{queue_status\} =~ /queueFull/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | --warning-* --critical-* | Warning threshold. Can be: 'messages-workqueue', 'dns-requests-outstanding', 'dns-requests-pending', 'fd-opened', 'threads-mail', 'update-failures', 'time-expiration'. | @@ -597,9 +597,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md index 325961875431..4e175038abf0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md @@ -407,18 +407,18 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | CRITICALLINKLATENCY | Thresholds | | | | WARNINGLINKLOSS | Thresholds | | | | CRITICALLINKLOSS | Thresholds | | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | | WARNINGPORTTRAFFICIN | Thresholds | | | | CRITICALPORTTRAFFICIN | Thresholds | | | | WARNINGPORTTRAFFICOUT | Thresholds | | | | CRITICALPORTTRAFFICOUT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALALERTING | Thresholds | | | | CRITICALTOTALALERTING | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -462,18 +462,18 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | CRITICALLINKLOSS | Thresholds | | | | WARNINGLINKSINEFFECTIVE | Thresholds | | | | CRITICALLINKSINEFFECTIVE | Thresholds | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{link\_status}, %{display} | %{link\_status} =~ /failed/i | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} =~ /failed/i | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | | WARNINGPORTTRAFFICIN | Thresholds | | | | CRITICALPORTTRAFFICIN | Thresholds | | | | WARNINGPORTTRAFFICOUT | Thresholds | | | | CRITICALPORTTRAFFICOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /alerting/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /alerting/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALALERTING | Thresholds | | | | CRITICALTOTALALERTING | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -544,8 +544,8 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | FILTERORGANIZATIONID | Filter VPN tunnels by organization ID (can be a regexp) | | | | FILTERORGANIZATIONNAME | Filter VPN tunnels by organization name (can be a regexp) | | | | FILTERDEVICESERIAL | Filter VPN tunnels by device serial (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | %{status} =~ /offline/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | %\{status\} =~ /offline/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | | | | WARNINGTOTALDORMANT | Thresholds | | | | CRITICALTOTALDORMANT | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -575,8 +575,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --api-token='12345abcd6789efgh0123abcd4567efgh8901abcd' \ --proxyurl='http://proxy.mycompany:8080' \ --filter-device-name='centreon-par-training-ap' \ - --critical-status='%{status} =~ /alerting/i' \ - --critical-link-status='%{link_status} =~ /failed/i' \ + --critical-status='%\{status\} =~ /alerting/i' \ + --critical-link-status='%\{link_status\} =~ /failed/i' \ --verbose ``` @@ -651,7 +651,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -734,15 +734,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --skip-performance | Don't monitor appliance performance score. | | --skip-connections | Don't monitor connection stats. | | --skip-traffic-disconnect-port | Skip port traffic counters if port status is disconnected. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-online-prct', 'total-offline', 'total-offline-prct', 'total-alerting', 'traffic-in', 'traffic-out', 'connections-success', 'connections-auth', 'connections-assoc', 'connections-dhcp', 'connections-dns', 'load', 'links-ineffective', 'link-latency' (ms), ''link-loss' (%), 'port-traffic-in', 'port-traffic-out'. | @@ -762,15 +762,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --skip-performance | Don't monitor appliance performance score. | | --skip-connections | Don't monitor connection stats. | | --skip-traffic-disconnect-port | Skip port traffic counters if port status is disconnected. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-online-prct', 'total-offline', 'total-offline-prct', 'total-alerting', 'traffic-in', 'traffic-out', 'connections-success', 'connections-auth', 'connections-assoc', 'connections-dhcp', 'connections-dns', 'load', 'links-ineffective', 'link-latency' (ms), ''link-loss' (%), 'port-traffic-in', 'port-traffic-out'. | @@ -802,9 +802,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-organization-id | Filter VPN tunnels by organization ID (can be a regexp). | | --filter-organization-name | Filter VPN tunnels by organization name (can be a regexp). | | --filter-device-serial | Filter VPN tunnels by device serial (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{deviceSerial}, %{mode} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-offline', 'total-dormant'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md index b4bcd7387627..da0c19c4a842 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md @@ -296,7 +296,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -361,8 +361,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --speed-in | Set interface speed for incoming traffic (in Mb). | | --speed-out | Set interface speed for outgoing traffic (in Mb). | | --units-traffic | Units of thresholds for the traffic (default: '%') ('%', 'b/s'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /offline/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /offline/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'total-devices', 'clients', 'in', 'out'. | | --critical-* | Critical threshold. Can be: 'total-devices', 'clients', 'in', 'out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md index fb827c1babff..e2c5c9dba03f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md @@ -169,8 +169,8 @@ yum install centreon-plugin-Network-Cisco-Prime-Restapi | CRITICALAPCLIENTS | Critical threshold | | | | WARNINGAPLWAPPUPTIME | Warning threshold | | | | CRITICALAPLWAPPUPTIME | Critical threshold | | | -| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | %{admin\_status} =~ /enable/i && %{status} =~ /minor\|warning/i | | -| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | %{admin\_status} =~ /enable/i && %{status} =~ /major\|critical/i | | +| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | %\{admin_status\} =~ /enable/i && %\{status\} =~ /minor\|warning/i | | +| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | %\{admin_status\} =~ /enable/i && %\{status\} =~ /major\|critical/i | | | WARNINGAPUPTIME | Warning threshold | | | | CRITICALAPUPTIME | Critical threshold | | | | WARNINGCTRLAPCOUNT | Warning threshold | | | @@ -199,8 +199,8 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --password='' \ --filter-ap='.*' \ --filter-controller='.*' \ - --warning-ap-status='%{admin_status} =~ /enable/i && %{status} =~ /minor|warning/i' \ - --critical-ap-status='%{admin_status} =~ /enable/i && %{status} =~ /major|critical/i' \ + --warning-ap-status='%\{admin_status\} =~ /enable/i && %\{status\} =~ /minor|warning/i' \ + --critical-ap-status='%\{admin_status\} =~ /enable/i && %\{status\} =~ /major|critical/i' \ --warning-ap-clients='' \ --critical-ap-clients='' \ --warning-ap-uptime='' \ @@ -268,7 +268,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -318,8 +318,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^total-error$' | | --warning-* | Warning threshold. Can be: 'ap-clients', 'ap-uptime', 'ap-lwappuptime', 'ctrl-ap-count'. | | --critical-* | Critical threshold. Can be: 'ap-clients', 'ap-uptime', 'ap-lwappuptime', 'ctrl-ap-count'. | -| --warning-ap-status | Define the conditions to match for the status to be WARNING (default: '%{admin\_status} =~ /enable/i && %{status} =~ /minor\|warning/i') You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | -| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} =~ /enable/i && %{status} =~ /major\|critical/i'). You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | +| --warning-ap-status | Define the conditions to match for the status to be WARNING (default: '%\{admin_status\} =~ /enable/i && %\{status\} =~ /minor\|warning/i') You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | +| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} =~ /enable/i && %\{status\} =~ /major\|critical/i'). You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | | --reload-cache-time | Time in minutes before reloading cache file (default: 5). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md index bedbaf012fc4..5132c1c8e5c1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md @@ -431,8 +431,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALAUTHROUNDTRIPTIME | Thresholds | | | | WARNINGAUTHTRANSACTIONSSUCEEDED | Thresholds | | | | CRITICALAUTHTRANSACTIONSSUCEEDED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /dead/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /dead/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -447,7 +447,7 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | WARNINGINUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -474,8 +474,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALPEERSDETECTED | Thresholds | | | | WARNINGPEERUPDATELAST | Thresholds | | | | CRITICALPEERUPDATELAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | %{adminStatus} =~ /start/ && %{state} !~ /established/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | %\{adminStatus\} =~ /start/ && %\{state\} !~ /established/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -483,8 +483,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | %{running\_last\_changed} \> %{running\_last\_saved} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\}| %\{running_last_changed\}\> %\{running_last_saved\}| | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -585,8 +585,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -623,8 +623,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter partition name (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -660,8 +660,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -687,10 +687,10 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALREMOVED | Set thresholds for members count for each states. | | | | WARNINGSDMMISMATCH | Set thresholds for members count for each states. | | | | CRITICALSDMMISMATCH | Set thresholds for members count for each states. | | | -| CRITICALSTACKSTATUS | Set critical threshold for stack status. You can use the following variables: %{stack\_status} | %{stack\_status} =~ /notredundant/ | | -| WARNINGSTACKSTATUS | Set warning threshold for stack status. You can use the following variables: %{stack\_status} | | | -| CRITICALSTATUS | Set critical threshold for member status. You can use the following variables: %{name}, %{role}, %{state} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed' | %{state} !~ /ready/ && %{state} !~ /provisioned/ | | -| WARNINGSTATUS | Set warning threshold for members status. You can use the following variables: %{name}, %{role}, %{state} | | | +| CRITICALSTACKSTATUS | Set critical threshold for stack status. You can use the following variables: %\{stack_status\} | %\{stack_status\} =~ /notredundant/ | | +| WARNINGSTACKSTATUS | Set warning threshold for stack status. You can use the following variables: %\{stack_status\} | | | +| CRITICALSTATUS | Set critical threshold for member status. You can use the following variables: %\{name\}, %\{role\}, %\{state\} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed' | %\{state\} !~ /ready/ && %\{state\} !~ /provisioned/ | | +| WARNINGSTATUS | Set warning threshold for members status. You can use the following variables: %\{name\}, %\{role\}, %\{state\} | | | | WARNINGVERSIONMISMATCH | Set thresholds for members count for each states. | | | | CRITICALVERSIONMISMATCH | Set thresholds for members count for each states. | | | | WARNINGWAITING | Set thresholds for members count for each states. | | | @@ -815,7 +815,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -883,9 +883,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='auth' | | --filter-name | Filter AAA server by name (Example: 10.199.126.100:1812:1813. Format: \[address\]:\[authPort\]:\[accPort\]). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /dead/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /dead/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'auth-requests', 'auth-requests-timeout', 'auth-transactions-suceeded', 'auth-roundtrip-time', 'acc-requests', 'acc-requests-timeout', 'acc-transactions-suceeded', 'acc-roundtrip-time'. | @@ -916,9 +916,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-qos-limit | Check QoS traffic limit rate. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-traffic-limit', 'out-traffic-limit', 'in-crc', 'in-fcserror', 'out-fc-wait', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -965,9 +965,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-remote-as | Filter based on remote AS number (regexp allowed) | | --filter-remote-addr | Filter based on IP of peers (regexp allowed) | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminStatus} =~ /start/ && %{state} !~ /established/'). You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminStatus\} =~ /start/ && %\{state\} !~ /established/'). You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | | --warning-* --critical-* | Thresholds. Can be: 'peers-detected', 'peer-update-last', 'peer-prefixes-accepted', 'peer-prefixes-denied'. | @@ -975,8 +975,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{running\_last\_changed} \> %{running\_last\_saved}'). You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{running_last_changed\}\> %\{running_last_saved\}'). You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | @@ -1038,9 +1038,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-qos-limit | Check QoS traffic limit rate. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-traffic-limit', 'out-traffic-limit', 'in-crc', 'in-fcserror', 'out-fc-wait', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -1096,9 +1096,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /readOnly/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /readOnly/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | | --filter-name | Filter partition name (can be a regexp). | @@ -1133,8 +1133,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -1142,10 +1142,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Set thresholds on members count for each states. (Can be: 'waiting', 'progressing', 'added', 'ready', 'sdm-mismatch', 'version-mismatch', 'feature-mismatch', 'new-master-init', 'provisioned', 'invalid', 'removed') | -| --warning-stack-status | Set warning threshold for stack status (default: ''). You can use the following variables: %{stack\_status} | -| --critical-stack-status | Set critical threshold for stack status (default: '%{stack\_status} =~ /notredundant/'). You can use the following variables: %{stack\_status} | -| --warning-status | Set warning threshold for members status (default: ''). You can use the following variables: %{name}, %{role}, %{state} | -| --critical-status | Set critical threshold for member status (default: '%{state} !~ /ready/ && %{state} !~ /provisioned/'). You can use the following variables: %{name}, %{role}, %{state} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed'. | +| --warning-stack-status | Set warning threshold for stack status (default: ''). You can use the following variables: %\{stack_status\} | +| --critical-stack-status | Set critical threshold for stack status (default: '%\{stack_status\} =~ /notredundant/'). You can use the following variables: %\{stack_status\} | +| --warning-status | Set warning threshold for members status (default: ''). You can use the following variables: %\{name\}, %\{role\}, %\{state\} | +| --critical-status | Set critical threshold for member status (default: '%\{state\} !~ /ready/ && %\{state\} !~ /provisioned/'). You can use the following variables: %\{name\}, %\{role\}, %\{state\} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md index 13e5beb22edb..58276d83d9ab 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md @@ -204,9 +204,9 @@ yum install centreon-plugin-Network-Cisco-Standard-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERNAME | Filter name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | %{admin} eq "up" and %{oper} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | %\{admin\} eq "up" and %\{oper\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALOPERATIONALUP | Thresholds | | | @@ -297,7 +297,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -352,9 +352,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin} eq "up" and %{oper} eq "down"'). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin\} eq "up" and %\{oper\} eq "down"'). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-operational-up'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md index a781c43c852f..d02a78bc6bd4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md @@ -258,8 +258,8 @@ yum install centreon-plugin-Network-Cisco-Umbrella-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /yellow/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /red/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /yellow/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -267,14 +267,14 @@ yum install centreon-plugin-Network-Cisco-Umbrella-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGADSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALADSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGCLOUDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALCLOUDSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGLOCALDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALLOCALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | +| WARNINGADSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALADSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGCLOUDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALCLOUDSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGLOCALDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALLOCALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -424,7 +424,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,16 +478,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /yellow/') You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /red/'). You can use the following variables: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /yellow/') You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\} | | Option | Description | |:-------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /yellow/'). Can be: 'dns-status', 'localdns-status', 'cloud-status', 'ad-status'. Can use special variables like: %{status}, %{display} | -| --critical-* | Define the conditions to match for the status to be CRITICAL. (default: %{status} =~ /red/). Can be: 'dns-connectivity', 'localdns-connectivity', 'cloud-connectivity', 'ad-connectivity'. Can use special variables like: %{status}, %{display} | +| --warning-* | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /yellow/'). Can be: 'dns-status', 'localdns-status', 'cloud-status', 'ad-status'. Can use special variables like: %\{status\}, %\{display\} | +| --critical-* | Define the conditions to match for the status to be CRITICAL. (default: %\{status\} =~ /red/). Can be: 'dns-connectivity', 'localdns-connectivity', 'cloud-connectivity', 'ad-connectivity'. Can use special variables like: %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md index 773c883c8e2c..339b4e38d0ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md @@ -276,8 +276,8 @@ yum install centreon-plugin-Network-Cisco-Vcs-Restapi | CRITICALRESPONSES4XX | Threshold | | | | WARNINGRESPONSES5XX | Threshold | | | | CRITICALRESPONSES5XX | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status} | %{status} ne "Active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\} | %\{status\} ne "Active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -295,8 +295,8 @@ yum install centreon-plugin-Network-Cisco-Vcs-Restapi | CRITICALSEARCHESMAXTARGETSEXCEEDED | Thresholds | | | | WARNINGSEARCHESTOTAL | Thresholds | | | | CRITICALSEARCHESTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status}, %{type}, %{name} | %{status} ne "Active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status}, %{type}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\}, %\{type\}, %\{name\} | %\{status\} ne "Active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\}, %\{type\}, %\{name\} | | | | WARNINGZONECALLSCURRENT | Thresholds | | | | CRITICALZONECALLSCURRENT | Thresholds | | | | WARNINGZONESCOUNT | Thresholds | | | @@ -328,7 +328,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-counters='' \ --filter-zone-name='' \ --warning-status='' \ - --critical-status='%{status} ne "Active"' \ + --critical-status='%\{status\} ne "Active"' \ --warning-zone-calls-current='' \ --critical-zone-calls-current='' \ --warning-searches-total='' \ @@ -400,7 +400,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -484,8 +484,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). (example: --filter-counters='responses') | | --warning-* --critical-* | Threshold. Can be: 'connections-client', 'connections-server', 'requests-completed', 'requests-get', 'requests-post', 'responses-1xx', 'responses-2xx', 'responses-3xx', 'responses-4xx', 'responses-5xx'. | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "Active"'). Can use special variables like: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "Active"'). Can use special variables like: %\{status\}. | @@ -506,8 +506,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-zone-name | Filter zones by name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'zones-count', 'zone-calls-current', 'searches-total', 'searches-dropped', 'searches-maxsub-exceeded', 'searches-maxtargets-exceeded'. | -| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{status}, %{type}, %{name}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} ne "Active"'). Can use special variables like: %{status}, %{type}, %{name}. | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{status\}, %\{type\}, %\{name\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} ne "Active"'). Can use special variables like: %\{status\}, %\{type\}, %\{name\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md index a3c27fec273d..524b500e7ce9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md @@ -267,7 +267,7 @@ yum install centreon-plugin-Network-Cisco-Voice-Gateway-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -369,7 +369,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -465,9 +465,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md index 6b487f592ad6..d1713968a37c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md @@ -280,8 +280,8 @@ yum install centreon-plugin-Network-Cisco-Wap-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -308,9 +308,9 @@ yum install centreon-plugin-Network-Cisco-Wap-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------|:-----------:| | FILTERAPDESCRIPTION | Filter virtual access points by description (can be a regexp) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} eq "up" and %{operational\_status} eq "down"'). You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | %{admin\_status} eq "up" and %{operational\_status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} eq "up" and %\{operational_status\} eq "down"'). You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | %\{admin_status\} eq "up" and %\{operational_status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -395,7 +395,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -486,9 +486,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -548,9 +548,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-description | Filter virtual access points by description (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} eq "up" and %{operational\_status} eq "down"'). You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} eq "up" and %\{operational_status\} eq "down"'). You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md index 561c30a7555d..59cb25d90a6d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md @@ -381,8 +381,8 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -394,10 +394,10 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | FILTERGROUP | Filter access point group (can be a regexp) | | | | WARNINGRADIOINTERFACECHANNELSUTILIZATION | Threshold | | | | CRITICALRADIOINTERFACECHANNELSUTILIZATION | Threshold | | | -| CRITICALRADIOSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} eq "down" | | -| WARNINGRADIOSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALRADIOSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} eq "down" | | +| WARNINGRADIOSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | WARNINGTOTALASSOCIATED | Threshold | | | @@ -484,8 +484,8 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -613,7 +613,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -672,10 +672,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter access point name (can be a regexp). | | --filter-group | Filter access point group (can be a regexp). | | --add-radio-interfaces | Monitor radio interfaces channels utilization. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-associated', 'total-disassociating', 'total-downloading', 'total-enabled', 'total-disabled', 'radio-interface-channels-utilization' (%). | @@ -687,10 +687,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter access point name (can be a regexp). | | --filter-group | Filter access point group (can be a regexp). | | --add-radio-interfaces | Monitor radio interfaces channels utilization. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-associated', 'total-disassociating', 'total-downloading', 'total-enabled', 'total-disabled', 'radio-interface-channels-utilization' (%). | @@ -763,9 +763,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md index 277490bc0b38..96345de2d038 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md @@ -327,7 +327,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md index 1cd5d3709fc6..97b74dea5f82 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md @@ -234,8 +234,8 @@ yum install centreon-plugin-Network-Citrix-Sdx-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter storage repository name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /good/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /good/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,7 +336,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -426,8 +426,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^read\|write$' | | --filter-name | Filter storage repository name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /good/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /good/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'usage'. | | --critical-* | Critical threshold. Can be: 'usage'. | | --units | Units of thresholds (default: '%') ('%', 'B'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-colubris-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-colubris-snmp.md index 805d9920a3e2..1172b1196fa3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-colubris-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-colubris-snmp.md @@ -250,8 +250,8 @@ yum install centreon-plugin-Network-Colubris-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | FILTERNAME | Filter AP name with regexp | | | -| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | %{state} eq "disconnected" | | -| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | %\{state\} eq "disconnected" | | +| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGAPUSERS | Warning threshold | | | | CRITICALAPUSERS | Critical threshold | | | | WARNINGTOTALAP | Warning threshold | | | @@ -295,8 +295,8 @@ yum install centreon-plugin-Network-Colubris-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -414,7 +414,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -484,8 +484,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --check-device-without-ctrl | Check device even if it doesn't belongs to an controller team. | | --warning-* | Warning threshold. Can be: 'total-ap', 'total-users', 'ap-users'. | | --critical-* | Critical threshold. Can be: 'total-ap', 'total-users', 'ap-users'. | -| --warning-ap-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "disconnected"'). You can use the following variables: %{state}, %{display} | +| --warning-ap-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "disconnected"'). You can use the following variables: %\{state\}, %\{display\} | @@ -521,9 +521,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cyberoam-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cyberoam-snmp.md index 80f997141102..33b36cbca2a4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cyberoam-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-cyberoam-snmp.md @@ -319,7 +319,7 @@ yum install centreon-plugin-Network-Cyberoam-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -435,7 +435,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -537,9 +537,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-6200-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-6200-snmp.md index b48d0db2238f..b10c54ebe3c3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-6200-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-6200-snmp.md @@ -387,7 +387,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -496,9 +496,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md index 8d2cc4fad454..606e2f47ab3f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md @@ -291,8 +291,8 @@ yum install centreon-plugin-Network-Dell-Nseries-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -419,7 +419,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -483,9 +483,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-os10-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-os10-snmp.md index 3ffaf6bf4a1e..7bd57429c561 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-os10-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-os10-snmp.md @@ -356,8 +356,8 @@ yum install centreon-plugin-Network-Dell-Os10-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -430,7 +430,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -507,7 +507,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -648,9 +648,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md index 898a66f93e06..c1650890e709 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md @@ -288,7 +288,7 @@ yum install centreon-plugin-Network-Dell-Sseries-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -377,7 +377,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -480,9 +480,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-denyall-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-denyall-snmp.md index 5e632ae5da40..880e9e2082eb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-denyall-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-denyall-snmp.md @@ -311,8 +311,8 @@ yum install centreon-plugin-Network-Denyall-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -361,8 +361,8 @@ yum install centreon-plugin-Network-Denyall-Snmp | CRITICALMEMORYUSAGE | Threshold | | | | WARNINGREQUESTS | Threshold | | | | CRITICALREQUESTS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{uid} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{uid} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{uid\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{uid\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -515,7 +515,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -581,9 +581,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -634,9 +634,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-uid | Filter reverse proxy by UID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{uid} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{uid} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{uid} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{uid\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{uid\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{uid\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'memory-usage', 'requests'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md index cfebf5ed31ac..6991ed43c384 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md @@ -230,7 +230,7 @@ yum install centreon-plugin-Network-Digi-AnywhereUSB-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -321,7 +321,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -411,9 +411,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md index a36370d1f160..3d4184f8e64c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md @@ -230,7 +230,7 @@ yum install centreon-plugin-Network-Digi-Portserverts-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -320,7 +320,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -410,9 +410,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md index 76ee79b882bc..c6a6c2292c72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md @@ -256,10 +256,10 @@ yum install centreon-plugin-Network-Digi-Sarian-Snmp |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------|:-----------:| | WARNINGSIGNAL | Warning threshold for signal strength | | | | CRITICALSIGNAL | Critical threshold for signal strength | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{registered}, %{attachement} | %{attachement} eq "attached" and %{registered} !~ /registeredHostNetwork\|registeredRoaming/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{registered}, %{attachement} | | | -| CRITICALTECHNOLOGY | Set critical threshold for technology. Use special variables %{technology} | %{technology} !~ /2G\|3G\|4G/ | | -| WARNINGTECHNOLOGY | Set warning threshold for technology. Use special variables %{technology} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{registered\}, %\{attachement\} | %\{attachement\} eq "attached" and %\{registered\} !~ /registeredHostNetwork\|registeredRoaming/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{registered\}, %\{attachement\} | | | +| CRITICALTECHNOLOGY | Set critical threshold for technology. Use special variables %\{technology\} | %\{technology\} !~ /2G\|3G\|4G/ | | +| WARNINGTECHNOLOGY | Set warning threshold for technology. Use special variables %\{technology\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -294,7 +294,7 @@ yum install centreon-plugin-Network-Digi-Sarian-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -409,7 +409,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -451,10 +451,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='signal\|technology' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{registered}, %{attachement} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{attachement} eq "attached" and %{registered} !~ /registeredHostNetwork\|registeredRoaming/' You can use the following variables: %{registered}, %{attachement} | -| --warning-technology | Set warning threshold for technology. Use special variables %{technology}. | -| --critical-technology | Set critical threshold for technology (default: '%{technology} !~ /2G\|3G\|4G/' Use special variables %{technology}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{registered\}, %\{attachement\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{attachement\} eq "attached" and %\{registered\} !~ /registeredHostNetwork\|registeredRoaming/' You can use the following variables: %\{registered\}, %\{attachement\} | +| --warning-technology | Set warning threshold for technology. Use special variables %\{technology\}. | +| --critical-technology | Set critical threshold for technology (default: '%\{technology\} !~ /2G\|3G\|4G/' Use special variables %\{technology\}. | | --warning-signal | Warning threshold for signal strength. | | --critical-signal | Critical threshold for signal strength. | @@ -501,9 +501,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md index a9abb9f94609..8b0a4b2b2f39 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md @@ -238,7 +238,7 @@ yum install centreon-plugin-Network-Dlink-Dgs3100-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -327,7 +327,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -420,9 +420,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md index ef3eb32c0c19..14ed205298eb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Dlink-Standard-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --use-new-perfdata --verbose --no-skipped-counters | | @@ -304,12 +304,12 @@ yum install centreon-plugin-Network-Dlink-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{status} =~ /unknown/i | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{status}, %{display} | %{status} eq "down" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /codeUpdate/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{status} =~ /codeUpdate/i | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{status\} =~ /unknown/i | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "down" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /codeUpdate/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{status\} =~ /codeUpdate/i | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i | | | WARNINGMEMBERSTOTAL | Thresholds | | | | CRITICALMEMBERSTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -398,7 +398,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -493,9 +493,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -538,12 +538,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /codeUpdate/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /codeUpdate/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-efficientip-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-efficientip-snmp.md index 245cae94530d..892ab5fc1d50 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-efficientip-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-efficientip-snmp.md @@ -613,8 +613,8 @@ yum install centreon-plugin-Network-Efficientip-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------|:-----------:| -| WARGNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /upgrading\|split-brain/') Can be used with special variables like: %{status}, %{role} | %{status} =~ /upgrading\|split-brain/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %{status}, %{role} | %{status} =~ /invalid credentials\|replication stopped\|timeout/ | | +| WARGNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /upgrading\|split-brain/') Can be used with special variables like: %\{status\}, %\{role\} | %\{status\} =~ /upgrading\|split-brain/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %\{status\}, %\{role\} | %\{status\} =~ /invalid credentials\|replication stopped\|timeout/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -708,7 +708,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -888,8 +888,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /upgrading\|split-brain/') Can be used with special variables like: %{status}, %{role} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %{status}, %{role} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /upgrading\|split-brain/') Can be used with special variables like: %\{status\}, %\{role\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %\{status\}, %\{role\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-enterasys-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-enterasys-snmp.md index 0ffa9c5ecb39..f2bffa2dcb79 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-enterasys-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-enterasys-snmp.md @@ -285,8 +285,8 @@ yum install centreon-plugin-Network-Enterasys-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -439,7 +439,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -489,9 +489,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md index 756746d56eed..62daa596ed2a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md @@ -327,7 +327,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -354,7 +354,7 @@ Les options génériques sont listées ci-dessous : | --filter | Exclude some parts (comma separated list) You can also exclude items from specific instances: --filter=psu,1 | | --absent-problem | Return an error if a component is not 'present' (default is skipping). It can be set globally or for a specific instance: --absent-problem='component\_name' or --absent-problem='component\_name,instance\_value'. | | --no-component | Define the expected status if no components are found (default: critical). | -| --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='psu,OK,notAvailable' package network::evertz::FC7800::snmp::mode::components::psu; use strict; use warnings; my %map\_psu\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_psu = { powerSupply1Status =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.3', map =\> \%map\_psu\_status }, powerSupply2Status =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.4', map =\> \%map\_psu\_status }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, $mapping\_psu-\>{powerSupply1Status}-\>{oid} . '.0', $mapping\_psu-\>{powerSupply2Status}-\>{oid} . '.0'; } sub check\_psu { my ($self, %options) = @\_; return if (!defined($options{status})); return if ($self-\>check\_filter(section =\> 'psu', instance =\> $options{instance})); $self-\>{components}-\>{psu}-\>{total}++; $self-\>{output}-\>output\_add(long\_msg =\> sprintf("power supply '%s' status is '%s' \[instance = %s\]", $options{instance}, $options{status}, $options{instance})); my $exit = $self-\>get\_severity(section =\> 'psu', value =\> $options{status}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Power supply '%s' status is '%s'", $options{instance}, $options{status})); } } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking poer supplies"); $self-\>{components}-\>{psu} = {name =\> 'psus', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'psu')); my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping\_psu, results =\> $self-\>{results}, instance =\> '0'); check\_psu($self, status =\> $result-\>{powerSupply1Status}, instance =\> 1); check\_psu($self, status =\> $result-\>{powerSupply2Status}, instance =\> 2); } 1; package network::evertz::FC7800::snmp::mode::components::frameline; use strict; use warnings; my %map\_frameline\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_frameline = { frameStatusLine =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.2', map =\> \%map\_frameline\_status }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, $mapping\_frameline-\>{frameStatusLine}-\>{oid} . '.0'; } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking frame line"); $self-\>{components}-\>{frameline} = {name =\> 'frameline', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'frameline')); my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping\_frameline, results =\> $self-\>{results}, instance =\> '0'); return if (!defined($result-\>{frameStatusLine})); $self-\>{components}-\>{frameline}-\>{total}++; $self-\>{output}-\>output\_add(long\_msg =\> sprintf("frame line status is '%s' \[instance = %s\]", $result-\>{frameStatusLine}, '0')); my $exit = $self-\>get\_severity(section =\> 'frameline', value =\> $result-\>{frameStatusLine}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Frame line status is '%s'", $result-\>{frameStatusLine})); } } 1; | +| --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='psu,OK,notAvailable' package network::evertz::FC7800::snmp::mode::components::psu; use strict; use warnings; my %map\_psu\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_psu = \{ powerSupply1Status =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.3', map =\> \%map\_psu\_status \}, powerSupply2Status =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.4', map =\> \%map\_psu\_status \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}}, $mapping\_psu-\>\{powerSupply1Status\}-\>\{oid\} . '.0', $mapping\_psu-\>\{powerSupply2Status\}-\>\{oid\} . '.0'; \} sub check\_psu \{ my ($self, %options) = @\_; return if (!defined($options\{status\})); return if ($self-\>check\_filter(section =\> 'psu', instance =\> $options\{instance\})); $self-\>\{components\}-\>\{psu\}-\>\{total\}++; $self-\>\{output\}-\>output\_add(long\_msg =\> sprintf("power supply '%s' status is '%s' \[instance = %s\]", $options\{instance\}, $options\{status\}, $options\{instance\})); my $exit = $self-\>get\_severity(section =\> 'psu', value =\> $options\{status\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Power supply '%s' status is '%s'", $options\{instance\}, $options\{status\})); \} \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking poer supplies"); $self-\>\{components\}-\>\{psu\} = \{name =\> 'psus', total =\> 0, skip =\> 0\}; return if ($self-\>check\_filter(section =\> 'psu')); my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping\_psu, results =\> $self-\>\{results\}, instance =\> '0'); check\_psu($self, status =\> $result-\>\{powerSupply1Status\}, instance =\> 1); check\_psu($self, status =\> $result-\>\{powerSupply2Status\}, instance =\> 2); \} 1; package network::evertz::FC7800::snmp::mode::components::frameline; use strict; use warnings; my %map\_frameline\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_frameline = \{ frameStatusLine =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.2', map =\> \%map\_frameline\_status \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}}, $mapping\_frameline-\>\{frameStatusLine\}-\>\{oid\} . '.0'; \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking frame line"); $self-\>\{components\}-\>\{frameline\} = \{name =\> 'frameline', total =\> 0, skip =\> 0\}; return if ($self-\>check\_filter(section =\> 'frameline')); my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping\_frameline, results =\> $self-\>\{results\}, instance =\> '0'); return if (!defined($result-\>\{frameStatusLine\})); $self-\>\{components\}-\>\{frameline\}-\>\{total\}++; $self-\>\{output\}-\>output\_add(long\_msg =\> sprintf("frame line status is '%s' \[instance = %s\]", $result-\>\{frameStatusLine\}, '0')); my $exit = $self-\>get\_severity(section =\> 'frameline', value =\> $result-\>\{frameStatusLine\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Frame line status is '%s'", $result-\>\{frameStatusLine\})); \} \} 1; | | --warning | Define the warning threshold for temperatures (syntax: type,instance,threshold) Example: --warning='temperature,.*,30' | | --critical | Define the critical threshold for temperatures (syntax: type,instance,threshold) Example: --critical='temperature,.*,40' | | --warning-count-* | Define the warning threshold for the number of components of one type (replace '*' with the component type). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-extreme-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-extreme-snmp.md index 8a7ca40c432f..ef4458767a2d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-extreme-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-extreme-snmp.md @@ -273,12 +273,12 @@ yum install centreon-plugin-Network-Extreme-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{role}, %{roleLast} | | | -| UNKNOWNPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} eq "mismatch"'). You can use the following variables: %{role}, %{roleLast} | %{status} eq "mismatch" | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} eq "down"'). You can use the following variables: %{role}, %{roleLast} | %{role} ne %{roleLast} \|\| %{status} eq "down" | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} ne "up"'). You can use the following variables: %{link\_status}, %{display} | %{link\_status} ne "up" | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{role\}, %\{roleLast\} | | | +| UNKNOWNPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "mismatch"'). You can use the following variables: %\{role\}, %\{roleLast\} | %\{status\} eq "mismatch" | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down"'). You can use the following variables: %\{role\}, %\{roleLast\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down" | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} ne "up"'). You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} ne "up" | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -315,7 +315,7 @@ yum install centreon-plugin-Network-Extreme-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -405,7 +405,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Only keep perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -501,12 +501,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-member-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{role}, %{roleLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{status} eq "mismatch"'). You can use the following variables: %{role}, %{roleLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} eq "down"'). You can use the following variables: %{role}, %{roleLast} | -| --unknown-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} ne "up"'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{role\}, %\{roleLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "mismatch"'). You can use the following variables: %\{role\}, %\{roleLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down"'). You can use the following variables: %\{role\}, %\{roleLast\} | +| --unknown-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} ne "up"'). You can use the following variables: %\{link_status\}, %\{display\} | @@ -533,9 +533,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-congdropped', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fiberstore-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fiberstore-snmp.md index 5734eb0f18e4..429ba3ad44b1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fiberstore-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fiberstore-snmp.md @@ -261,8 +261,8 @@ yum install centreon-plugin-Network-Fiberstore-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -304,7 +304,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -377,7 +377,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -470,9 +470,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md index 198d62556741..5f540ad6631c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md @@ -323,7 +323,7 @@ yum install centreon-plugin-Network-Firewalls-Arkoon-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -369,7 +369,7 @@ yum install centreon-plugin-Network-Firewalls-Arkoon-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -463,7 +463,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -557,9 +557,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -654,9 +654,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md index 1b3228647781..883e29f3a907 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md @@ -317,8 +317,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | NOHASTATUS | Status to return when HA not running or not installed (default: 'UNKNOWN') | UNKNOWN | | -| WARNINGSTATUS | Trigger warning on %{role} or %{hastate} values. Example: --warning-status '%{role} !~ /master/' will warn when failover occurs | %{hastate} !~ /(UP\|working)/ | | -| CRITICALSTATUS | Trigger critical on %{role} or %{hastate} values (default: '%{hastate} !~ /(UP\|working)/') | | | +| WARNINGSTATUS | Trigger warning on %\{role\} or %\{hastate\} values. Example: --warning-status '%\{role\} !~ /master/' will warn when failover occurs | %\{hastate\} !~ /(UP\|working)/ | | +| CRITICALSTATUS | Trigger critical on %\{role\} or %\{hastate\} values (default: '%\{hastate\} !~ /(UP\|working)/') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -364,7 +364,7 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -372,8 +372,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "permanent" and %{status} =~ /down/i'). You can use the following variables: %{type}, %{status}, %{display} | %{type} eq "permanent" and %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "permanent" and %\{status\} =~ /down/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | %\{type\} eq "permanent" and %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -381,8 +381,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "up" and %{operState} ne %{operStateLast}'). You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | %{adminState} eq "up" and %{operState} ne %{operStateLast} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\}'). You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | %\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -480,7 +480,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -561,8 +561,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Trigger warning on %{role} or %{hastate} values. Example: --warning-status '%{role} !~ /master/' will warn when failover occurs. | -| --critical-status | Trigger critical on %{role} or %{hastate} values (default: '%{hastate} !~ /(UP\|working)/'). | +| --warning-status | Trigger warning on %\{role\} or %\{hastate\} values. Example: --warning-status '%\{role\} !~ /master/' will warn when failover occurs. | +| --critical-status | Trigger critical on %\{role\} or %\{hastate\} values (default: '%\{hastate\} !~ /(UP\|working)/'). | | --no-ha-status | Status to return when HA not running or not installed (default: 'UNKNOWN'). | @@ -622,9 +622,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -651,8 +651,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter vpn name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "permanent" and %{status} =~ /down/i'). You can use the following variables: %{type}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "permanent" and %\{status\} =~ /down/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | | --buggy-snmp | Checkpoint snmp can be buggy. Test that option if no response. | | --warning-* --critical-* | Thresholds. Can be: 'tunnels-total'. | @@ -673,8 +673,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "up" and %{operState} ne %{operStateLast}'). You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\}'). You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md index 4ae231c2c5ee..01bd48770cfe 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md @@ -326,8 +326,8 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | WARNINGACTIVEUNITS | Warning threshold | | | | CRITICALACTIVEUNITS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -407,7 +407,7 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -464,7 +464,7 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -556,7 +556,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -631,8 +631,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | --warning-* | Warning threshold. Can be: 'active-units'. | | --critical-* | Critical threshold. Can be: 'active-units'. | @@ -694,9 +694,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -775,9 +775,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md index 7c3ee037ed96..033ab94bd468 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md @@ -364,8 +364,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALCPUUTILIZATION | Set thresholds | | | | WARNINGMEMORYUSAGE | Set thresholds | | | | CRITICALMEMORYUSAGE | Set thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/'). You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | %{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/'). You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | %\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | | | | WARNINGSYNCHRONIZED | Set thresholds | | | | CRITICALSYNCHRONIZED | Set thresholds | | | | WARNINGTOTALCHECKSUMS | Set thresholds | | | @@ -444,8 +444,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALJITTER | Thresholds | | | | WARNINGLATENCY | Thresholds | | | | CRITICALLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | | | | WARNINGTRAFFICBI | Thresholds | | | | CRITICALTRAFFICBI | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -481,7 +481,7 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -547,8 +547,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALSESSIONSACTIVE | Thresholds | | | | WARNINGSESSIONSRATE Thresholds | | | | CRITICALSESSIONSRATE Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -669,7 +669,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -735,8 +735,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/'). You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/'). You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | | --warning-* --critical-* | Set thresholds. Can be: 'total-nodes', 'synchronized', 'unsynchronized', 'total-checksums', 'cpu-utilization', 'memory-usage'. | @@ -817,9 +817,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-id | Define which SD-WAN links should be monitored based on their IDs. This option will be treated as a regular expression. | | --filter-name | Define which SD-WAN links should be monitored based on their names. This option will be treated as a regular expression. | | --filter-vdom | Define which virtual domains should be monitored based on their names. This option will be treated as a regular expression. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'traffic-bi', 'latency', 'jitter', 'packetloss'. | @@ -854,9 +854,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -900,9 +900,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -946,9 +946,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -987,8 +987,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-* | Filter name with regexp. Can be ('vdomain', 'vpn') | | --warning-* | Warning on counters. Can be ('users', 'sessions', 'tunnels', 'traffic-in', 'traffic-out') | | --critical-* | Warning on counters. Can be ('users', 'sessions', 'tunnels', 'traffic-in', 'traffic-out') | -| --warning-status | Define the conditions to match for the status to be WARNING. Use "%{state}" as a special variable. Useful to be notified when tunnel is up "%{state} eq 'up'" | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Use "%{state}" as a special variable. Useful to be notified when tunnel is up "%{state} eq 'up'" | +| --warning-status | Define the conditions to match for the status to be WARNING. Use "%\{state\}" as a special variable. Useful to be notified when tunnel is up "%\{state\} eq 'up'" | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Use "%\{state\}" as a special variable. Useful to be notified when tunnel is up "%\{state\} eq 'up'" | @@ -1011,8 +1011,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-traffic | Add traffic usage by virtual domain. | | --add-policy | Add number of policies by virtual domain. | | --policy-cache-time | Time in minutes before reloading cache file (default: 60). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'sessions-active', 'session-rate', 'memory-usage-prct', 'license-usage', 'license-free', 'license-usage-prct', 'traffic-in', 'traffic-out', 'policies-active'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md index b97483c29edf..094d22ad41b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md @@ -363,7 +363,7 @@ yum install centreon-plugin-Network-Juniper-Mag-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -409,7 +409,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -475,7 +475,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -600,9 +600,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -648,9 +648,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md index 0f9f07cb557e..e4c3190bf600 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md @@ -382,7 +382,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Sa-Snmp | WARNINGIN | Thresholds | | | | CRITICALOUT | Thresholds | | | | WARNINGOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -494,7 +494,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -631,9 +631,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -680,9 +680,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md index 7444a1cc74db..dcd5f1d23e43 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md @@ -425,7 +425,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Srx-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -539,7 +539,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -711,9 +711,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds (will superseed --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md index 94b8499713d5..5b3668d5175b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md @@ -323,7 +323,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Ssg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -332,8 +332,8 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Ssg-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------|:-----------:| | FILTERNAME | Check only VPNs whose name match the given regular expression. | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{p1state} eq "inactive" \|\| %{p2state} eq "inactive"'). You can use the following variables: %{p1state}, %{p2state} | %{p1state} eq "inactive" \|\| %{p2state} eq "inactive" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{p1state}, %{p2state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive"'). You can use the following variables: %\{p1state\}, %\{p2state\} | %\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{p1state\}, %\{p2state\} | | | | WARNINGUPDATETIME | Warning threshold for update time (in seconds) | | | | CRITICALUPDATETIME | Critical threshold for update time (in seconds) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -437,7 +437,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -560,9 +560,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -589,8 +589,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Check only VPNs whose name match the given regular expression. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{p1state}, %{p2state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{p1state} eq "inactive" \|\| %{p2state} eq "inactive"'). You can use the following variables: %{p1state}, %{p2state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{p1state\}, %\{p2state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive"'). You can use the following variables: %\{p1state\}, %\{p2state\} | | --warning-update-time | Warning threshold for update time (in seconds). | | --critical-update-time | Critical threshold for update time (in seconds). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md index e241161306c3..9ed38b2e17f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md @@ -348,8 +348,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -376,8 +376,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /not-connected/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /not-connected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /not-connected/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /not-connected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -486,7 +486,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -591,9 +591,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -649,8 +649,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /not-connected/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /not-connected/i'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md index 582b4c4cf350..73b95688955f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md @@ -226,15 +226,15 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{status}, %{display} | | | -| UNKNOWNSYNCSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{enabled}, %{status} | | | -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{state}, %{stateLast} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "up"'). Can use special variables like: %{status}, %{display} | %{status} ne "up" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{status}, %{display} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast}'). Can use special variables like: %{state}, %{stateLast} | %{state} ne %{stateLast} | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{state}, %{stateLast} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{status} ne "synchronized"'). Can use special variables like: %{enabled}, %{status} | %{enabled} eq "yes" and %{status} ne "synchronized" | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{enabled}, %{status} | | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{status\}, %\{display\} | | | +| UNKNOWNSYNCSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "up"'). Can use special variables like: %\{status\}, %\{display\} | %\{status\} ne "up" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{status\}, %\{display\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\}'). Can use special variables like: %\{state\}, %\{stateLast\} | %\{state\} ne %\{stateLast\} | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{status\} ne "synchronized"'). Can use special variables like: %\{enabled\}, %\{status\} | %\{enabled\} eq "yes" and %\{status\} ne "synchronized" | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -243,9 +243,9 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter interface name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "active"'). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | %{state} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "active"'). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | %\{state\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -255,11 +255,11 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | | | | WARNINGIPSECTOTAL | Thresholds | | | | CRITICALIPSECTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ike\_phase1\_state} eq "down" or %{state} ne "active"'). You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | %{ike\_phase1\_state} eq "down" or %{state} ne "active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ike_phase1_state\} eq "down" or %\{state\} ne "active"'). You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | %\{ike_phase1_state\} eq "down" or %\{state\} ne "active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -268,8 +268,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | FILTERFEATURE | Filter license by feature (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{expired} eq "yes"'). Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | %{expired} eq "yes" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{expired\} eq "yes"'). Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | %\{expired\} eq "yes" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -279,8 +279,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | WARNINGAVUPDATE | Thresholds | | | | CRITICALAVUPDATE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_mode} !~ /normal/i'). You can use the following variables: %{oper\_mode} | %{oper\_mode} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_mode\} !~ /normal/i'). You can use the following variables: %\{oper_mode\} | %\{oper_mode\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_mode\} | | | | WARNINGTHREATUPDATE | Thresholds | | | | CRITICALTHREATUPDATE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -385,7 +385,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -455,15 +455,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-sync-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{enabled}, %{status} | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{enabled}, %{status} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{status} ne "synchronized"'). Can use special variables like: %{enabled}, %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast}'). Can use special variables like: %{state}, %{stateLast} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "up"'). Can use special variables like: %{status}, %{display} | +| --unknown-sync-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{status\} ne "synchronized"'). Can use special variables like: %\{enabled\}, %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\}'). Can use special variables like: %\{state\}, %\{stateLast\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "up"'). Can use special variables like: %\{status\}, %\{display\} | @@ -471,9 +471,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter interface name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "active"'). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "active"'). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -482,9 +482,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter tunnels by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ike\_phase1\_state} eq "down" or %{state} ne "active"'). You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ike_phase1_state\} eq "down" or %\{state\} ne "active"'). You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | | --warning-* --critical-* | Thresholds. Can be: 'ipsec-total'. | @@ -493,8 +493,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-feature | Filter license by feature (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{expired} eq "yes"'). Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{expired\} eq "yes"'). Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | @@ -515,8 +515,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --timezone | Timezone options. Default is 'GMT'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_mode} !~ /normal/i'). You can use the following variables: %{oper\_mode} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_mode\} !~ /normal/i'). You can use the following variables: %\{oper_mode\} | | --warning-* --critical-* | Thresholds. Can be: 'av-update' (s), 'threat-update' (s), 'sessions-traffic' (b/s), 'sessions-total-active'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md index 72fafdecf8f9..16bdd248dde8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md @@ -446,7 +446,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Only keep perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md index f0ef9ff9866b..244ef35f7358 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md @@ -326,7 +326,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md index 3a7add236dce..7cb06c436bd1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md @@ -385,7 +385,7 @@ yum install centreon-plugin-Network-Firewalls-Stonesoft | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -479,7 +479,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -539,9 +539,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{node\_status} =~ /unknown/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{node\_status} =~ /lockedOnline/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{node\_status} =~ /^(?:offline\|goingOffline\|lockedOffline\|goingLockedOffline\|stand by\|goingStandby)$/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{node_status\} =~ /unknown/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{node_status\} =~ /lockedOnline/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{node_status\} =~ /^(?:offline\|goingOffline\|lockedOffline\|goingLockedOffline\|stand by\|goingStandby)$/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | @@ -673,9 +673,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -721,9 +721,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md index 943c6ad1802c..6aaf7003fcb5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md @@ -310,8 +310,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -328,8 +328,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| CRITICALDDOSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} eq "attacking" | | -| WARNINGDDOSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALDDOSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} eq "attacking" | | +| WARNINGDDOSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -348,8 +348,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp |:---------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERNAME | Filter virtual servers by name | | | | FILTERVDOM | Filter virtual servers by vdom name | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | %{status} eq "unhealthy" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | %\{status\} eq "unhealthy" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | | | | WARNINGVIRTUALSERVERCONNECTIONS | Threshold | | | | CRITICALVIRTUALSERVERCONNECTIONS | Threshold | | | | WARNINGVIRTUALSERVERSDETECTED | Threshold | | | @@ -381,7 +381,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-ddos-status='' \ - --critical-ddos-status='%{status} eq "attacking"' + --critical-ddos-status='%\{status\} eq "attacking"' ``` La commande devrait retourner un message de sortie similaire à : @@ -467,7 +467,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -533,9 +533,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -583,8 +583,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-ddos-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-ddos-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "attacking"'). You can use the following variables: %{status} | +| --warning-ddos-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-ddos-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "attacking"'). You can use the following variables: %\{status\} | @@ -620,9 +620,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter virtual servers by name. | | --filter-vdom | Filter virtual servers by vdom name. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "unhealthy"'). You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "unhealthy"'). You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | | --warning-* --critical-* | Thresholds. Can be: 'virtualservers-detected', 'virtualservers-healthy', 'virtualserver-connections', 'virtualserver-throughput'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md index 19ed311f5c30..bcc44ac428cb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md @@ -301,7 +301,7 @@ yum install centreon-plugin-Network-Fortinet-Fortiauthenticator-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------|:-----------:| | UNKNOWNHASTATUS | Threshold | | | -| CRITICALHASTATUS | Threshold | %{ha\_status} ne %{ha\_status\_last} | | +| CRITICALHASTATUS | Threshold | %\{ha_status\} ne %\{ha_status_last\}| | | WARNINGHASTATUS | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -325,8 +325,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiauthenticator-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -463,7 +463,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -519,8 +519,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | @@ -547,9 +547,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md index 7ea1111f436e..55ce1ec20140 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Network-Fortinet-Fortigate-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| | FILTERVDOM | Filter vdom by name | | | -| CRITICALHEALTH | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /success/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /success/i | | -| WARNINGHEALTH | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALHEALTH | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /success/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /success/i | | +| WARNINGHEALTH | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -228,8 +228,8 @@ yum install centreon-plugin-Network-Fortinet-Fortigate-Restapi | UNIT | Select the time unit for thresholds. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds | | | | WARNINGEXPIRES | Thresholds | | | | CRITICALEXPIRES | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /expired/i'). You can use the following variables: %{name}, %{status} | %{status} =~ /expired/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{name\}, %\{status\} | %\{status\} =~ /expired/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -333,7 +333,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -384,9 +384,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-vdom | Filter vdom by name. | -| --unknown-health | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-health | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-health | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /success/i'). You can use the following variables: %{status}, %{name} | +| --unknown-health | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-health | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-health | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /success/i'). You can use the following variables: %\{status\}, %\{name\} | @@ -394,8 +394,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter licenses by name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /expired/i'). You can use the following variables: %{name}, %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{name\}, %\{status\}. | | --unit | Select the unit for expires threshold. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'expires'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md index 430203e35250..4d18fa6dc231 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Fortinet-Fortimail-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------|:-----------:| -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | %{ha\_status} ne %{ha\_status\_last} | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\}| %\{ha_status\} ne %\{ha_status_last\}| | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -335,8 +335,8 @@ yum install centreon-plugin-Network-Fortinet-Fortimail-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -470,7 +470,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -551,8 +551,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | @@ -592,9 +592,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md index c57a08810d6a..b533225c0584 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md @@ -234,16 +234,16 @@ yum install centreon-plugin-Network-Fortinet-Fortimanager-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERNAME | Filter by device name (can be a regexp) | | | -| WARNINGDEVICECONFIGSTATUS | Set warning threshold for device configuration status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICECONFIGSTATUS | Set critical threshold for device configuration status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICECONSTATUS | Set critical threshold for device connection status. You can use the following variables: %{status}, %{name} | %{status} =~ /down/i | | -| WARNINGDEVICECONSTATUS | Set warning threshold for device connection status. You can use the following variables: %{status}, %{name} | | | -| WARNINGDEVICEDBSTATUS | Set warning threshold for device DB status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICEDBSTATUS | Set critical threshold for device DB status. You can use the following variables: %{status}, %{name} | | | -| WARNINGDEVICEPOLICYSTATUS | Set warning threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | | | -| CRITICALDEVICEPOLICYSTATUS | Set critical threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | | | -| WARNINGDEVICESTATUS | Set warning threshold for device status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICESTATUS | Set critical threshold for device status You can use the following variables: %{status}, %{name} | | | +| WARNINGDEVICECONFIGSTATUS | Set warning threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICECONFIGSTATUS | Set critical threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICECONSTATUS | Set critical threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /down/i | | +| WARNINGDEVICECONSTATUS | Set warning threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | | | +| WARNINGDEVICEDBSTATUS | Set warning threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICEDBSTATUS | Set critical threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | | | +| WARNINGDEVICEPOLICYSTATUS | Set warning threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | | | +| CRITICALDEVICEPOLICYSTATUS | Set critical threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | | | +| WARNINGDEVICESTATUS | Set warning threshold for device status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICESTATUS | Set critical threshold for device status You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -288,7 +288,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-device-status='' \ --critical-device-status='' \ --warning-device-con-status='' \ - --critical-device-con-status='%{status} =~ /down/i' \ + --critical-device-con-status='%\{status\} =~ /down/i' \ --warning-device-db-status='' \ --critical-device-db-status='' \ --warning-device-config-status='' \ @@ -381,7 +381,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -424,16 +424,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:----------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter by device name (can be a regexp). | -| --warning-device-status | Set warning threshold for device status. You can use the following variables: %{status}, %{name} | -| --critical-device-status | Set critical threshold for device status You can use the following variables: %{status}, %{name} | -| --warning-device-con-status | Set warning threshold for device connection status. You can use the following variables: %{status}, %{name} | -| --critical-device-con-status | Set critical threshold for device connection status (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{name} | -| --warning-device-db-status | Set warning threshold for device DB status. You can use the following variables: %{status}, %{name} | -| --critical-device-db-status | Set critical threshold for device DB status. You can use the following variables: %{status}, %{name} | -| --warning-device-config-status | Set warning threshold for device configuration status. You can use the following variables: %{status}, %{name} | -| --critical-device-config-status | Set critical threshold for device configuration status. You can use the following variables: %{status}, %{name} | -| --warning-device-policy-package-status | Set warning threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | -| --critical-device-policy-package-status | Set critical threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | +| --warning-device-status | Set warning threshold for device status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-status | Set critical threshold for device status You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-con-status | Set warning threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-con-status | Set critical threshold for device connection status (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-db-status | Set warning threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-db-status | Set critical threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-config-status | Set warning threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-config-status | Set critical threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-policy-package-status | Set warning threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | +| --critical-device-policy-package-status | Set critical threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md index 2f5956617aab..5f49e3181b6b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md @@ -299,8 +299,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -351,7 +351,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -425,7 +425,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -522,9 +522,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md index b05dbe85d988..4a44788600b7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md @@ -237,8 +237,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiweb-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -263,8 +263,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiweb-Snmp | CRITICALCPULOAD | Thresholds | | | | WARNINGDISKUSAGE | Thresholds | | | | CRITICALDISKUSAGE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_mode} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_mode} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_mode\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_mode\} | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -351,7 +351,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -425,9 +425,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -462,8 +462,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='memory-usage' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_mode} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_mode} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_mode\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_mode\} | | --warning-* --critical-* | Thresholds. Can be: 'disk-usage' (%), 'memory-usage' (%), 'cpu-load' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-freebox-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-freebox-restapi.md index 05fa72caed89..da88ec9efea6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-freebox-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-freebox-restapi.md @@ -86,7 +86,7 @@ Il est nécessaire au préalable d'autoriser le client, de choisir un _app\_id_ `curl http:///api/v4/login/authorize -d '{"app_id":"centreon","app_name":"centreon","app_version":"3.0","device_name":"Freebox"}'` - Validez depuis l'écran de la Freebox et récupérez le token -- Ouvrez la page suivante http:///api/v4/login/authorize/ +- Ouvrez la page suivante http://\/api/v4/login/authorize/\ - Vérifiez que l'application est correcte et possède les bons droits Conservez précieusement votre _app\_id_ et le token car ils seront nécessaires durant la configuration de l'hôte. @@ -234,8 +234,8 @@ yum install centreon-plugin-Network-Freebox-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALDISKSTATUS | Set critical threshold for disk status (default: '%{status} =~ /error/i'). You can use the following variables: %{status} | %{status} =~ /error/i | | -| WARNINGDISKSTATUS | Set warning threshold for disk status. You can use the following variables: %{status} | | | +| CRITICALDISKSTATUS | Set critical threshold for disk status (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\} | %\{status\} =~ /error/i | | +| WARNINGDISKSTATUS | Set warning threshold for disk status. You can use the following variables: %\{status\} | | | | WARNINGFANSPEED | Thresholds | | | | CRITICALFANSPEED | Thresholds | | | | WARNINGTEMPERATURECPUB | Thresholds | | | @@ -244,8 +244,8 @@ yum install centreon-plugin-Network-Freebox-Restapi | CRITICALTEMPERATURECPUM | Thresholds | | | | WARNINGTEMPERATURESWITCH | Thresholds | | | | CRITICALTEMPERATURESWITCH | Thresholds | | | -| WARNINGWIFISTATUS | Set warning threshold for wifi status (default: '%{status} =~ /bad\_param/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /bad\_param/i | | -| CRITICALWIFISTATUS | Set critical threshold for wifi status (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /failed/i | | +| WARNINGWIFISTATUS | Set warning threshold for wifi status (default: '%\{status\} =~ /bad\_param/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /bad\_param/i | | +| CRITICALWIFISTATUS | Set critical threshold for wifi status (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /failed/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -333,7 +333,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -392,10 +392,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^temperature-cpum$' | -| --warning-wifi-status | Set warning threshold for wifi status (default: '%{status} =~ /bad\_param/i'). You can use the following variables: %{status}, %{display} | -| --critical-wifi-status | Set critical threshold for wifi status (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{display} | -| --warning-disk-status | Set warning threshold for disk status. You can use the following variables: %{status} | -| --critical-disk-status | Set critical threshold for disk status (default: '%{status} =~ /error/i'). You can use the following variables: %{status} | +| --warning-wifi-status | Set warning threshold for wifi status (default: '%\{status\} =~ /bad\_param/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-wifi-status | Set critical threshold for wifi status (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-disk-status | Set warning threshold for disk status. You can use the following variables: %\{status\} | +| --critical-disk-status | Set critical threshold for disk status (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature-cpum', 'temperature-cpub', 'temperature-switch', 'fan-speed'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fritzbox-upnp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fritzbox-upnp.md index c5ec627a2416..bdaee2298fe9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fritzbox-upnp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-fritzbox-upnp.md @@ -276,7 +276,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -323,8 +323,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='uptime' | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{connection\_status}, %{link\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} !~ /^up$/i and %{connection\_status} !~ /^connected$/i'). Can use special variables like: %{connection\_status}, %{link\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{connection_status\}, %\{link_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} !~ /^up$/i and %\{connection_status\} !~ /^connected$/i'). Can use special variables like: %\{connection_status\}, %\{link_status\} | | --unit | Select the unit for uptime threshold. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | | --warning-* --critical-* | Thresholds. Can be: 'uptime'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md index d18cac333641..8658b81aa0f4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md @@ -396,7 +396,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-h3c-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-h3c-snmp.md index c650b9f62e9a..a0ae76f111a8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-h3c-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-h3c-snmp.md @@ -317,7 +317,7 @@ yum install centreon-plugin-Network-H3c-Snmp | WARNINGIN | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -425,7 +425,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -553,9 +553,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'voltage' (mV), 'module-temperature' (C). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md index 6bce6db10df7..860106afa952 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md @@ -248,8 +248,8 @@ yum install centreon-plugin-Network-Hp-Moonshot-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -291,7 +291,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -362,7 +362,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -443,9 +443,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-standard-snmp.md index c937917e8f7f..21c21e213402 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-standard-snmp.md @@ -295,7 +295,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTMCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -316,7 +316,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTMCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -375,7 +375,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -384,8 +384,8 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -422,7 +422,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -523,7 +523,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -597,9 +597,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -717,9 +717,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -746,8 +746,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -774,9 +774,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-vc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-vc-snmp.md index e0e3786aa753..07cb5f4d1f7d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-vc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-hp-vc-snmp.md @@ -244,7 +244,7 @@ yum install centreon-plugin-Network-Hp-Vc-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -331,7 +331,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -415,9 +415,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-huawei-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-huawei-snmp.md index 1eb7e243b391..52756c34cf04 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-huawei-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-huawei-snmp.md @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Huawei-Snmp | CRITICALOUTPUTPOWER | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | | WARNINGOUTTRAFFIC | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | | CRITICALOUTTRAFFIC | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -313,7 +313,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -395,7 +395,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,9 +478,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical metrics. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will supersede --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md index 3a4cdbe46e1e..ca7f700dd1e9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md @@ -344,7 +344,7 @@ yum install centreon-plugin-Network-Ibm-Bladecenter-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -402,7 +402,7 @@ yum install centreon-plugin-Network-Ibm-Bladecenter-Snmp | CRITICALINTRAFFIC | Thresholds | 90 | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -503,7 +503,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -602,9 +602,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -692,9 +692,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-infoblox-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-infoblox-snmp.md index 1e81e6d8855a..836c8643b1bf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-infoblox-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-infoblox-snmp.md @@ -317,8 +317,8 @@ yum install centreon-plugin-Network-Infoblox-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -339,8 +339,8 @@ yum install centreon-plugin-Network-Infoblox-Snmp | CRITICALCPU2TEMPERATURE | Thresholds | | | | WARNINGCPULOAD | Thresholds | | | | CRITICALCPULOAD | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\} | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | | WARNINGSWAPUSAGE | Thresholds | | | @@ -373,7 +373,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -448,7 +448,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -570,9 +570,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -610,8 +610,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-load' (%), 'cpu1-temperature', 'cpu2-temperature', 'swap-usage' (%), 'memory-usage' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md index f24f3f92ac8c..b44eaccc0e20 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md @@ -304,7 +304,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md index d01ed0e2319e..99a2b3d233fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md @@ -276,7 +276,7 @@ yum install centreon-plugin-Network-Juniper-Isg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -366,7 +366,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -489,9 +489,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md index cfa263ed7a22..10a7ad4f0ec9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Network-Juniper-Trapeze-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{opstatus}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{opstatus} !~ /init\|redundant\|operationnal/'). You can use the following variables: %{opstatus}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{opstatus\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{opstatus\} !~ /init\|redundant\|operationnal/'). You can use the following variables: %\{opstatus\}, %\{display\} | | | | WARNINGTOTAL | Set warning threshold for number of AP linked to the WLC | | | | CRITICALTOTAL | Set critical threshold for number of AP linked to the WLC | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -344,7 +344,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -399,8 +399,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter AP name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{opstatus} !~ /init\|redundant\|operationnal/'). You can use the following variables: %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{opstatus\} !~ /init\|redundant\|operationnal/'). You can use the following variables: %\{opstatus\}, %\{display\} | | --warning-total | Set warning threshold for number of AP linked to the WLC | | --critical-total | Set critical threshold for number of AP linked to the WLC | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md index f0291e8d21c3..fccae7b21349 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md @@ -267,15 +267,15 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{class} | %{status} eq "unknown" | | +| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "unknown" | | | WARNINGFANSFAILED | Threshold | | | | CRITICALFANSFAILED | Threshold | | | -| CRITICALPSUSTATUS | Threshold | %{status} eq "bad" | | -| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALPSUSTATUS | Threshold | %\{status\} eq "bad" | | +| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGTEMPERATURE | Threshold | | | | CRITICALTEMPERATURE | Threshold | | | -| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{class} | %{status} eq "warn" | | -| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{class} | %{status} eq "hot" | | +| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "warn" | | +| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "hot" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -283,9 +283,9 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /MINOR/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /MAJOR\|CRITICAL/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /MINOR/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /MAJOR\|CRITICAL/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -295,10 +295,10 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------|:-----------:| | FILTERNAME | Filter ports by name (can be a regexp) | | | | FILTERTYPE | Filter ports by type (can be a regexp). You can use the following types: 'Network Port', 'Port Group' and 'Tool Port' | | | -| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /invalid\_software\_version/ | | -| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | %{adminStatus} eq "enabled" and %{operationalStatus} ne "up" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | | | +| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /invalid\_software\_version/ | | +| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | %\{adminStatus\} eq "enabled" and %\{operationalStatus\} ne "up" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | | | | WARNINGPACKETSDROPPED | Threshold | | | | CRITICALPACKETSDROPPED | Threshold | | | | WARNINGPACKETSIN | Threshold | | | @@ -327,7 +327,7 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | TIMEZONE | Override the timezone of distant equipment. Can use format: 'Europe/London' or '+0100' | | | | NTPHOSTNAME | Set the NTP hostname (if not set, localtime is used) | | | | NTPPORT | Set the NTP port (default: 123) | | | -| CRITICALNTPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} !~ /in\_reach\|in\_sync/ | | +| CRITICALNTPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} !~ /in\_reach\|in\_sync/ | | | WARNINGNTPSTATUS | Define the conditions to match for the status to be WARNING | | | | WARNINGOFFSET | Define the time offset (in seconds) that will trigger a WARNING status | | | | CRITICALOFFSET | Define the time offset (in seconds) that will trigger a CRITICAL status | | | @@ -365,15 +365,15 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --port='8000' \ --api-username='username' \ --api-password='*****' \ - --unknown-temperature-status='%{status} eq "unknown"' \ - --warning-temperature-status='%{status} eq "warn"' \ - --critical-temperature-status='%{status} eq "hot"' \ + --unknown-temperature-status='%\{status\} eq "unknown"' \ + --warning-temperature-status='%\{status\} eq "warn"' \ + --critical-temperature-status='%\{status\} eq "hot"' \ --warning-temperature='' \ --critical-temperature='' \ --warning-fans-failed='' \ --critical-fans-failed='' \ --warning-psu-status='' \ - --critical-psu-status='%{status} eq "bad"' \ + --critical-psu-status='%\{status\} eq "bad"' \ --verbose ``` @@ -440,7 +440,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -493,12 +493,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default : '%{status} eq "unknown"'). You can use the following variables: %{status}, %{class} | -| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default : '%{status} eq "warn"'). You can use the following variables: %{status}, %{class} | -| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "hot"'); You can use the following variables: %{status}, %{class} | -| --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-psu-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'); You can use the following variables: %{status}, %{name} | +| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default : '%\{status\} eq "unknown"'). You can use the following variables: %\{status\}, %\{class\} | +| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default : '%\{status\} eq "warn"'). You can use the following variables: %\{status\}, %\{class\} | +| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "hot"'); You can use the following variables: %\{status\}, %\{class\} | +| --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-psu-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'); You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature', 'fans-failed'. | @@ -506,9 +506,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /MINOR/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /MAJOR\|CRITICAL/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /MINOR/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /MAJOR\|CRITICAL/i'). You can use the following variables: %\{status\} | @@ -517,12 +517,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ports by name (can be a regexp). | | --filter-type | Filter ports by type (can be a regexp). You can use the following types: 'Network Port', 'Port Group' and 'Tool Port' | -| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-license-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /invalid\_software\_version/'). You can use the following variables: %{status}, %{name} | -| --critical-license-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminStatus} eq "enabled" and %{operationalStatus} ne "up"'). You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | +| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-license-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /invalid\_software\_version/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-license-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminStatus\} eq "enabled" and %\{operationalStatus\} ne "up"'). You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-out-prct', 'traffic-out', 'packets-out', 'packets-dropped', 'packets-pass', 'packets-insp'. | @@ -532,7 +532,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --unknown-ntp-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-ntp-status | Define the conditions to match for the status to be WARNING. | -| --critical-ntp-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in\_reach\|in\_sync/i') You can use the following variables: %{status} | +| --critical-ntp-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in\_reach\|in\_sync/i') You can use the following variables: %\{status\} | | --warning-offset | Define the time offset (in seconds) that will trigger a WARNING status. | | --critical-offset | Define the time offset (in seconds) that will trigger a CRITICAL status. | | --ntp-hostname | Set the NTP hostname (if not set, localtime is used). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md index 38529fc45181..6b0cb15cf5a2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md @@ -342,7 +342,7 @@ yum install centreon-plugin-Network-Lenovo-Flexsystem-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -400,7 +400,7 @@ yum install centreon-plugin-Network-Lenovo-Flexsystem-Snmp | CRITICALINTRAFFIC | Thresholds | 90 | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -501,7 +501,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -602,9 +602,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -692,9 +692,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md index a230cd1ffcc0..64504b2963c4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md @@ -257,8 +257,8 @@ yum install centreon-plugin-Network-Lenovo-Rackswitch-Snmp | CRITICALFANSPEED | Thresholds | | | | WARNINGSENSORTEMPERATURE | Thresholds | | | | CRITICALSENSORTEMPERATURE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} eq "noncritical"'). You can use the following variables: %{status} | %{status} eq "noncritical" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "critical"'). You can use the following variables: %{status} | %{status} eq "critical" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "noncritical"'). You can use the following variables: %\{status\} | %\{status\} eq "noncritical" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "critical"'). You can use the following variables: %\{status\} | %\{status\} eq "critical" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -281,8 +281,8 @@ yum install centreon-plugin-Network-Lenovo-Rackswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -333,7 +333,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -406,7 +406,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -467,9 +467,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} eq "noncritical"'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "critical"'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "noncritical"'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "critical"'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'sensor-temperature', 'fan-speed'. | @@ -497,9 +497,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-libraesva-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-libraesva-snmp.md index 19d51173d543..05045aab66a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-libraesva-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-libraesva-snmp.md @@ -288,8 +288,8 @@ yum install centreon-plugin-Network-Libraesva-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -356,8 +356,8 @@ yum install centreon-plugin-Network-Libraesva-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{cluster\_status} | | | -| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{cluster\_status} =~ /error/i'). You can use the following variables: %{cluster\_status} | | | +| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{cluster_status\} | | | +| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{cluster_status\} =~ /error/i'). You can use the following variables: %\{cluster_status\} | | | | WARNINGMAILSBOUNCED | Thresholds | | | | CRITICALMAILSBOUNCED | Thresholds | | | | WARNINGMAILSQUEUEIN | Thresholds | | | @@ -462,7 +462,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -536,9 +536,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -642,9 +642,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^mail-sent$' | -| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{cluster\_status} | -| --warning-cluster-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{cluster\_status} | -| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL (default: '%{cluster\_status} =~ /error/i'). You can use the following variables: %{cluster\_status} | +| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{cluster_status\} | +| --warning-cluster-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{cluster_status\} | +| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL (default: '%\{cluster_status\} =~ /error/i'). You can use the following variables: %\{cluster_status\} | | --warning-* --critical-* | Thresholds. Can be: 'mails-sent', 'mails-received', 'mails-rejected', 'mails-bounced', 'mails-queue-in', 'mails-queue-out', 'messages-spam', 'messages-virus', | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md index 61c568b0b5f7..f4183f2ee1d5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md @@ -319,7 +319,7 @@ yum install centreon-plugin-Network-Loadbalancers-A10-AX-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -330,8 +330,8 @@ yum install centreon-plugin-Network-Loadbalancers-A10-AX-Snmp | FILTERNAME | Filter by virtual server name (can be a regexp) | | | | WARNINGCURRENTCON | Warning threshold | | | | CRITICALCURRENTCON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALCON | Warning threshold | | | | CRITICALTOTALCON | Critical threshold | | | | WARNINGTRAFFICIN | Warning threshold | | | @@ -433,7 +433,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -565,9 +565,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -606,8 +606,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'current-con', 'total-con', 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: 'current-con', 'total-con', 'traffic-in', 'traffic-out'. | | --filter-name | Filter by virtual server name (can be a regexp). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md index caaaed9278c7..ed27bd329602 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md @@ -335,10 +335,10 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------|:-----------:| -| CRITICALFAILOVERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{failoverstatus} =~ /unknown/'). You can use the following variables: %{failoverstatus} | %{failoverstatus} =~ /unknown/ | | -| WARNINGFAILOVERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{failoverstatus} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %{syncstatus} | %{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/ | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{syncstatus} | | | +| CRITICALFAILOVERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{failoverstatus\} =~ /unknown/'). You can use the following variables: %\{failoverstatus\} | %\{failoverstatus\} =~ /unknown/ | | +| WARNINGFAILOVERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{failoverstatus\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %\{syncstatus\} | %\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/ | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{syncstatus\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -379,11 +379,11 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | | | WARNINGCURRENTSERVERCONNECTIONS | Thresholds | | | | CRITICALCURRENTSERVERCONNECTIONS | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -392,15 +392,15 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | | | | WARNINGCURRENTACTIVEMEMBERS | Thresholds | | | | CRITICALCURRENTACTIVEMEMBERS | Thresholds | | | | WARNINGCURRENTSERVERCONNECTIONS | Thresholds | | | | CRITICALCURRENTSERVERCONNECTIONS | Thresholds | | | | WARNINGCURRENTTOTALMEMBERS | Thresholds | | | | CRITICALCURRENTTOTALMEMBERS | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -432,10 +432,10 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | UNITS | Units of thresholds for the traffic (Default: '%') ('%', 'b/s') | % | | | FILTERNAME | Filter by trunks name (regexp can be used) | | | -| UNKNOWNINTERFACESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| WARNINGINTERFACESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALINTERFACESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNINTERFACESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGINTERFACESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALINTERFACESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGINTERFACESTOTAL | Thresholds | | | | CRITICALINTERFACESTOTAL | Thresholds | | | | WARNINGPACKETSDROPIN | Thresholds | | | @@ -446,8 +446,8 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | CRITICALPACKETSERRORIN | Thresholds | | | | WARNINGPACKETSERROROUT | Thresholds | | | | CRITICALPACKETSERROROUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /uninitialized\|down/'). You can use the following variables: %{status}, %{display} | %{status} =~ /uninitialized\|down/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /uninitialized\|down/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /uninitialized\|down/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -460,9 +460,9 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -564,7 +564,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -661,10 +661,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). | -| --warning-sync-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{syncstatus} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %{syncstatus} | -| --warning-failover-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{failoverstatus} | -| --critical-failover-status | Define the conditions to match for the status to be CRITICAL (Default: '%{failoverstatus} =~ /unknown/'). You can use the following variables: %{failoverstatus} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{syncstatus\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %\{syncstatus\} | +| --warning-failover-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{failoverstatus\} | +| --critical-failover-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{failoverstatus\} =~ /unknown/'). You can use the following variables: %\{failoverstatus\} | @@ -720,9 +720,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current-server-connections'. | @@ -731,12 +731,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | | --warning-* --critical-* | Thresholds. Can be: 'current-server-connections', 'current-active-members', 'current-total-members'. | @@ -782,12 +782,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --units-traffic | Units of thresholds for the traffic (Default: '%') ('%', 'b/s'). | | --speed | Set trunk speed in Mbps (Default: sysTrunkOperBw). If not setand sysTrunkOperBw OID value is 0, percentage thresholds will not be applied on traffic metrics. | | --add-interfaces | Monitor trunk interfaces. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /uninitialized\|down/'). You can use the following variables: %{status}, %{display} | -| --unknown-interface-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-interface-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-interface-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /uninitialized\|down/'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-interface-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-interface-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-interface-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'packets-error-in' (%), 'packets-error-out' (%), 'packets-drop-in' (%), 'packets-drop-out' (%), 'total-interfaces'. | @@ -796,9 +796,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current-client-connections'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md index 83ab9721b4ec..8dac89ef2f0d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md @@ -301,10 +301,10 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -337,8 +337,8 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALINTRAFFIC | Critical threshold | | | | WARNINGOUTRAFFIC | Warning threshold | | | | CRITICALOUTRAFFIC | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /inService\|disabled/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /inService\|disabled/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -375,7 +375,7 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -390,8 +390,8 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALINTRAFFIC | Critical threshold | | | | WARNINGOUTRAFFIC | Warning threshold | | | | CRITICALOUTRAFFIC | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /inService\|disabled\|redirect/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /inService\|disabled\|redirect/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -418,7 +418,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -484,7 +484,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -559,10 +559,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^ha-status$' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | @@ -603,8 +603,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter real server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | | --critical-* | Critical threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | @@ -633,9 +633,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -676,8 +676,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter virtual server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | | --critical-* | Critical threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md index 7dd0dc697f19..76ab8f5b3d3e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md @@ -484,7 +484,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -563,12 +563,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%{ha\_status} =~ /unknown/i'). Can use special variables like: %{ha\_status} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %{ha\_status}, %{ha\_mode} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{ha\_status} =~ /down\|partialFail\|monitorFail\|completeFail\|partialFailSsl\|routem onitorFail/i'). Can use special variables like: %{ha\_status}, %{ha\_mode} | -| --unknown-peer-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%{peer\_status} =~ /unknown/i'). Can use special variables like: %{peer\_status}, %{ha\_mode} | -| --warning-peer-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %{peer\_status} | -| --critical-peer-status | Define the conditions to match for the status to be CRITICAL. (Default: ''). Can use special variables like: %{peer\_status} | +| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%\{ha_status\} =~ /unknown/i'). Can use special variables like: %\{ha_status\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %\{ha_status\}, %\{ha_mode\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{ha_status\} =~ /down\|partialFail\|monitorFail\|completeFail\|partialFailSsl\|routem onitorFail/i'). Can use special variables like: %\{ha_status\}, %\{ha_mode\} | +| --unknown-peer-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%\{peer_status\} =~ /unknown/i'). Can use special variables like: %\{peer_status\}, %\{ha_mode\} | +| --warning-peer-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %\{peer_status\} | +| --critical-peer-status | Define the conditions to match for the status to be CRITICAL. (Default: ''). Can use special variables like: %\{peer_status\} | @@ -628,9 +628,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-meru-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-meru-snmp.md index 0b63c8a236a9..c94457c90ff3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-meru-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-meru-snmp.md @@ -274,8 +274,8 @@ yum install centreon-plugin-Network-Meru-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -383,7 +383,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -471,9 +471,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md index 201e12f0fec5..dd1ceaea787e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md @@ -339,8 +339,8 @@ yum install centreon-plugin-Network-Microsens-G6-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -387,8 +387,8 @@ yum install centreon-plugin-Network-Microsens-G6-Snmp | CRITICALINPUTPOWER | Thresholds | | | | WARNINGOUTPUTPOWER | Thresholds | | | | CRITICALOUTPUTPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %{status}, %{port}, %{location} | %{status} =~ /txFailure\|lossOfSignal\|readError/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{location} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %\{status\}, %\{port\}, %\{location\} | %\{status\} =~ /txFailure\|lossOfSignal\|readError/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{location\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -424,7 +424,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --filter-port='' \ --warning-status='' \ - --critical-status='%{status} =~ /txFailure|lossOfSignal|readError/' \ + --critical-status='%\{status\} =~ /txFailure|lossOfSignal|readError/' \ --warning-temperature='' \ --critical-temperature='' \ --warning-input-power='' \ @@ -492,7 +492,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -598,9 +598,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -646,8 +646,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter ports by index (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{location} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %{status}, %{port}, %{location} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{location\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %\{status\}, %\{port\}, %\{location\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature', 'input-power', 'output-power'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mikrotik-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mikrotik-snmp.md index 61c596a9c2ba..f596c99eb159 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mikrotik-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mikrotik-snmp.md @@ -355,8 +355,8 @@ yum install centreon-plugin-Network-Mikrotik-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | CRITICALSPEED | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | CRITICALTOTALADMINDOWN | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | WARNINGTOTALADMINUP | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | @@ -493,7 +493,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -590,9 +590,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will superseed --\[warning\|critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md index 14c818e2ecd8..b2e5150264c3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md @@ -284,7 +284,7 @@ yum install centreon-plugin-Network-Mitel-3300icp-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -397,7 +397,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,9 +479,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md index 93ca62fafc0a..df8d79c59e20 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md @@ -275,7 +275,7 @@ yum install centreon-plugin-Network-Switchs-Moxa-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | #NOM? | | @@ -372,7 +372,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -461,9 +461,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md index 6ea78235addc..33d91b23b06f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md @@ -267,8 +267,8 @@ yum install centreon-plugin-Network-Netgear-Mseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -306,7 +306,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -378,7 +378,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -474,9 +474,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md index bdf0540cca6e..95f9fc66412c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md @@ -268,8 +268,8 @@ yum install centreon-plugin-Network-Netgear-Sseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -311,7 +311,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -383,7 +383,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,9 +478,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md index 1fd48cdd10a2..9d16ed4db761 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md @@ -266,14 +266,14 @@ yum install centreon-plugin-Network-Nokia-Isam-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| DISPLAYNAME | Define the name to display. Available macros: %{SvcDescription}, %{IfName}, %{SapEncapName}, %{SapDescription}, %{SapPortId}. | %{SvcDescription}.%{IfName}.%{SapEncapName} | | +| DISPLAYNAME | Define the name to display. Available macros: %\{SvcDescription\}, %\{IfName\}, %\{SapEncapName\}, %\{SapDescription\}, %\{SapPortId\}. | %\{SvcDescription\}.%\{IfName\}.%\{SapEncapName\} | | | FILTERNAME | Filter by Service Access Point (SAP) name (can be a regexp) | | | | WARNINGINTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALINTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | WARNINGOUTTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALOUTTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default: '%{admin} =~ /up/i and %{status} !~ /up/i'. You can use the following variables: %{admin}, %{status}, %{display} | %{admin} =~ /up/i and %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default: '%\{admin\} =~ /up/i and %\{status\} !~ /up/i'. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | %\{admin\} =~ /up/i and %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | | | WARNINGTOTALINTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALTOTALINTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | WARNINGTOTALOUTTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | @@ -290,8 +290,8 @@ yum install centreon-plugin-Network-Nokia-Isam-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -394,7 +394,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -480,15 +480,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --display-name | Define the name to display (default: '%{SvcDescription}.%{IfName}.%{SapEncapName}'). Other available macros: %{SapDescription}, %{SapPortId} | +| --display-name | Define the name to display (default: '%\{SvcDescription\}.%\{IfName\}.%\{SapEncapName\}'). Other available macros: %\{SapDescription\}, %\{SapPortId\} | | --filter-name | Filter by Service Access Point (SAP) name (can be a regexp). | | --speed-in | Define the actual maximum incoming traffic speed you can have on the interfaces in megabits per second. | | --speed-out | Define the actual maximum outgoing traffic speed you can have on the interfaces in megabits per second. | | --speed-total-in | Define the actual maximum total incoming traffic speed you can have on the interfaces in megabits per second. | | --speed-total-out | Define the actual maximum total outgoing traffic speed you can have on the interfaces in megabits per second. | | --units-traffic | Define the unit to use to apply to thresholds (default: '%') ('%', 'b/s'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Default: '%{admin} =~ /up/i and %{status} !~ /up/i'. You can use the following variables: %{admin}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Default: '%\{admin\} =~ /up/i and %\{status\} !~ /up/i'. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | --warning-* | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic'. | | --critical-* | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic'. | | --reload-cache-time | Time in seconds before reloading the cache file (default: 300). | @@ -518,9 +518,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md index 901266ba7d4f..fe9e2540646d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md @@ -335,8 +335,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | ACTIVEPREFIXES | Threshold | | | | SENTPREFIXES | Threshold | | | | RECEIVEDPREFIXES | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | %{state} =~ /outOfService/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | %\{state\} =~ /outOfService/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -375,8 +375,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters | | @@ -387,8 +387,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | FILTERNAME | Filter by instance name (can be a regexp) | | | | TOTALINTINSERVICE | Threshold | | | | TOTALINTOUTSERVICE | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state} | %{admin\_state} eq "inService" and %{oper\_state} !~ /inService\|transition/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\} | %\{admin_state\} eq "inService" and %\{oper_state\} !~ /inService\|transition/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -404,8 +404,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALPEERTUNNELTOTAL | Threshold | | | | WARNINGPEERTUNNELTOTALSESSIONS | Threshold | | | | CRITICALPEERTUNNELTOTALSESSIONS | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | | | | WARNINGVRTRTUNNELACTIVESESSIONS | Threshold | | | | CRITICALVRTRTUNNELACTIVESESSIONS | Threshold | | | | WARNINGVRTRTUNNELTOTAL | Threshold | | | @@ -428,8 +428,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALIPV4ACTIVETARGETADJ | Threshold | | | | WARNINGIPV4OPERDOWNEVENTS | Threshold | | | | CRITICALIPV4OPERDOWNEVENTS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | %{admin\_state} eq "inService" and %{ipv4\_oper\_state} !~ /inService\|transition/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | %\{admin_state\} eq "inService" and %\{ipv4_oper_state\} !~ /inService\|transition/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -451,8 +451,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | TRAFFICINABOVECIR | Threshold | | | | TRAFFICOUTBELOWCIR | Threshold | | | | TRAFFICOUTABOVECIR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{admin\_state} eq "up" and %{oper\_state} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{admin_state\} eq "up" and %\{oper_state\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -461,8 +461,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------|:-----------:| | FILTERNAME | Filter alarm input (tmnxSasAlarmInputDescription) (can be a regexp) | | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{alarm\_input\_admin\_state}, %{alarm\_input\_status}, %{alarm\_output\_severity} | %{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /minor/ | | -| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | %{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{alarm_input_admin_state\}, %\{alarm_input_status\}, %\{alarm_output_severity\} | %\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /minor/ | | +| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | %\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -500,7 +500,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -610,7 +610,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -646,8 +646,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'active-prefixes', 'sent-prefixes', 'received-prefixes'. | | --critical-* | Critical threshold. Can be: 'active-prefixes', 'sent-prefixes', 'received-prefixes'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /outOfService/') You can use the following variables: %{display}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /outOfService/') You can use the following variables: %\{display\}, %\{state\} | | --filter-name | Filter by BGP name (can be a regexp). Syntax: VrtrName:peeraddr:peerAS:description | @@ -670,7 +670,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --no-component | Define the expected status if no components are found (default: critical). | | --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='entity,fan..*,CRITICAL,booting' | | --warning | Set warning threshold (syntax: type,regexp,threshold) Example: --warning='temperature,.*,20' | -| --critical | Set critical threshold (syntax: type,regexp,threshold) Example: --critical='temperature,.*,30' package network::nokia::timos::snmp::mode::components::entity; use strict; use warnings; my %map\_class = ( 1 =\> 'other', 2 =\> 'unknown', 3 =\> 'physChassis', 4 =\> 'container', 5 =\> 'powerSupply', 6 =\> 'fan', 7 =\> 'sensor', 8 =\> 'ioModule', 9 =\> 'cpmModule', 10 =\> 'fabricModule', 11 =\> 'mdaModule', 12 =\> 'flashDiskModule', 13 =\> 'port', 14 =\> 'mcm', 15 =\> 'ccm', 16 =\> 'oesCard', 17 =\> 'oesControlCard', 18 =\> 'oesUserPanel', 19 =\> 'alarmInputModule', ); my %map\_truth = (1 =\> 'true', 2 =\> 'false'); my %map\_oper\_state = ( 1 =\> 'unknown', 2 =\> 'inService', 3 =\> 'outOfService', 4 =\> 'diagnosing', 5 =\> 'failed', 6 =\> 'booting', 7 =\> 'empty', 8 =\> 'provisioned', 9 =\> 'unprovisioned', 10 =\> 'upgrade', 11 =\> 'downgrade', 12 =\> 'inServiceUpgrade', 13 =\> 'inServiceDowngrade', 14 =\> 'resetPending', 15 =\> 'softReset', 16 =\> 'preExtension', ); my $mapping = { tmnxHwClass =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.7', map =\> \%map\_class }, tmnxHwName =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.8' }, tmnxHwOperState =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.16', map =\> \%map\_oper\_state }, tmnxHwTempSensor =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.17', map =\> \%map\_truth }, tmnxHwTemperature =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.18' }, tmnxHwTempThreshold =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.19' }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, { oid =\> $mapping-\>{tmnxHwClass}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwName}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTempSensor}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwOperState}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTemperature}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTempThreshold}-\>{oid} }; } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking entities"); $self-\>{components}-\>{entity} = {name =\> 'entity', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'entity')); my ($exit, $warn, $crit, $checked); foreach my $oid ($self-\>{snmp}-\>oid\_lex\_sort(keys %{$self-\>{results}})) { next if ($oid !~ /^$mapping-\>{tmnxHwName}-\>{oid}\.(.*)$/); my $instance = $1; my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping, results =\> $self-\>{results}, instance =\> $instance); next if ($self-\>check\_filter(section =\> 'entity', instance =\> $result-\>{tmnxHwClass} . '.' . $instance)); $self-\>{components}-\>{entity}-\>{total}++; $self-\>{output}-\>output\_add( long\_msg =\> sprintf( "%s '%s' status is '%s' \[instance = %s, temperature = %s\]", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwOperState}, $result-\>{tmnxHwClass} . '.' . $instance, $result-\>{tmnxHwTempSensor} eq 'true' ? $result-\>{tmnxHwTemperature} : '-' ) ); $exit = $self-\>get\_severity(label =\> 'default', section =\> 'entity', instance =\> $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwOperState}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf("%s '%s' status is '%s'", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwOperState})); } next if ($result-\>{tmnxHwTempSensor} eq 'false'); ($exit, $warn, $crit, $checked) = $self-\>get\_severity\_numeric(section =\> 'temperature', instance =\> $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwTemperature}); if ($checked == 0 && $result-\>{tmnxHwTempThreshold} != -1 ) { $self-\>{perfdata}-\>threshold\_validate(label =\> 'critical-temperature-instance-' . $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwTempThreshold}); $exit = $self-\>{perfdata}-\>threshold\_check(value =\> $result-\>{tmnxHwTemperature}, threshold =\> \[ { label =\> 'critical-temperature-instance-' . $instance, exit\_litteral =\> 'critical' }\]); $warn = undef; $crit = $self-\>{perfdata}-\>get\_perfdata\_for\_output(label =\> 'critical-temperature-instance-' . $result-\>{tmnxHwClass} . '.' . $instance); } if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf( "%s '%s' temperature is '%s' C", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwTemperature} ) ); } $self-\>{output}-\>perfdata\_add( label =\> 'temperature', unit =\> 'C', nlabel =\> 'hardware.entity.temperature.celsius', instances =\> $result-\>{tmnxHwName}, value =\> $result-\>{tmnxHwTemperature}, warning =\> $warn, critical =\> $crit ); } } 1; | +| --critical | Set critical threshold (syntax: type,regexp,threshold) Example: --critical='temperature,.*,30' package network::nokia::timos::snmp::mode::components::entity; use strict; use warnings; my %map\_class = ( 1 =\> 'other', 2 =\> 'unknown', 3 =\> 'physChassis', 4 =\> 'container', 5 =\> 'powerSupply', 6 =\> 'fan', 7 =\> 'sensor', 8 =\> 'ioModule', 9 =\> 'cpmModule', 10 =\> 'fabricModule', 11 =\> 'mdaModule', 12 =\> 'flashDiskModule', 13 =\> 'port', 14 =\> 'mcm', 15 =\> 'ccm', 16 =\> 'oesCard', 17 =\> 'oesControlCard', 18 =\> 'oesUserPanel', 19 =\> 'alarmInputModule', ); my %map\_truth = (1 =\> 'true', 2 =\> 'false'); my %map\_oper\_state = ( 1 =\> 'unknown', 2 =\> 'inService', 3 =\> 'outOfService', 4 =\> 'diagnosing', 5 =\> 'failed', 6 =\> 'booting', 7 =\> 'empty', 8 =\> 'provisioned', 9 =\> 'unprovisioned', 10 =\> 'upgrade', 11 =\> 'downgrade', 12 =\> 'inServiceUpgrade', 13 =\> 'inServiceDowngrade', 14 =\> 'resetPending', 15 =\> 'softReset', 16 =\> 'preExtension', ); my $mapping = \{ tmnxHwClass =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.7', map =\> \%map\_class \}, tmnxHwName =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.8' \}, tmnxHwOperState =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.16', map =\> \%map\_oper\_state \}, tmnxHwTempSensor =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.17', map =\> \%map\_truth \}, tmnxHwTemperature =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.18' \}, tmnxHwTempThreshold =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.19' \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}\}, \{ oid =\> $mapping-\>\{tmnxHwClass\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwName\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTempSensor\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwOperState\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTemperature\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTempThreshold\}-\>\{oid\} \}; \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking entities"); $self-\>\{components\}-\>\{entity\} = \{name =\> 'entity', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'entity')); my ($exit, $warn, $crit, $checked); foreach my $oid ($self-\>\{snmp\}-\>oid\_lex\_sort(keys %\{$self-\>\{results\}\})) \{ next if ($oid !~ /^$mapping-\>\{tmnxHwName\}-\>\{oid\}\.(.*)$/); my $instance = $1; my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping, results =\> $self-\>\{results\}, instance =\> $instance); next if ($self-\>check\_filter(section =\> 'entity', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance)); $self-\>\{components\}-\>\{entity\}-\>\{total\}++; $self-\>\{output\}-\>output\_add( long\_msg =\> sprintf( "%s '%s' status is '%s' \[instance = %s, temperature = %s\]", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwOperState\}, $result-\>\{tmnxHwClass\} . '.' . $instance, $result-\>\{tmnxHwTempSensor\} eq 'true' ? $result-\>\{tmnxHwTemperature\} : '-' ) ); $exit = $self-\>get\_severity(label =\> 'default', section =\> 'entity', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwOperState\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf("%s '%s' status is '%s'", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwOperState\})); \} next if ($result-\>\{tmnxHwTempSensor\} eq 'false'); ($exit, $warn, $crit, $checked) = $self-\>get\_severity\_numeric(section =\> 'temperature', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwTemperature\}); if ($checked == 0 && $result-\>\{tmnxHwTempThreshold\} != -1 ) \{ $self-\>\{perfdata\}-\>threshold\_validate(label =\> 'critical-temperature-instance-' . $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwTempThreshold\}); $exit = $self-\>\{perfdata\}-\>threshold\_check(value =\> $result-\>\{tmnxHwTemperature\}, threshold =\> \[ \{ label =\> 'critical-temperature-instance-' . $instance, exit\_litteral =\> 'critical' \}\]); $warn = undef; $crit = $self-\>\{perfdata\}-\>get\_perfdata\_for\_output(label =\> 'critical-temperature-instance-' . $result-\>\{tmnxHwClass\} . '.' . $instance); \} if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf( "%s '%s' temperature is '%s' C", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwTemperature\} ) ); \} $self-\>\{output\}-\>perfdata\_add( label =\> 'temperature', unit =\> 'C', nlabel =\> 'hardware.entity.temperature.celsius', instances =\> $result-\>\{tmnxHwName\}, value =\> $result-\>\{tmnxHwTemperature\}, warning =\> $warn, critical =\> $crit ); \} \} 1; | | --warning-count-* | Define the warning threshold for the number of components of one type (replace '*' with the component type). | | --critical-count-* | Define the critical threshold for the number of components of one type (replace '*' with the component type). | @@ -700,9 +700,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -732,8 +732,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'total-int-inservice', 'total-int-outservice'. | | --critical-* | Critical threshold. Can be: 'total-int-inservice', 'total-int-outservice'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "inService" and %{oper\_state} !~ /inService\|transition/'). You can use the following variables: %{display}, %{oper\_state}, %{admin\_state}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "inService" and %\{oper_state\} !~ /inService\|transition/'). You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\}. | | --filter-name | Filter by instance name (can be a regexp). | @@ -744,8 +744,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'vrtr-tunnel-total', 'vrtr-tunnel-active-sessions', 'vrtr-tunnel-total-sessions', 'peer-tunnel-total', 'peer-tunnel-active-sessions', 'peer-tunnel-total-sessions'. | | --critical-* | Critical threshold. Can be: 'vrtr-tunnel-total', 'vrtr-tunnel-active-sessions', 'vrtr-tunnel-total-sessions', 'peer-tunnel-total', 'peer-tunnel-active-sessions', 'peer-tunnel-total-sessions'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | | --filter-vrtr-name | Filter by vrtr name (can be a regexp). | | --filter-peer-addr | Filter by peer addr (can be a regexp). | @@ -757,8 +757,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'ipv4-oper-down-events', 'ipv4-active-sessions', 'ipv4-active-link-adj', 'ipv4-active-target-adj'. | | --critical-* | Critical threshold. Can be: 'ipv4-oper-down-events', 'ipv4-active-sessions', 'ipv4-active-link-adj', 'ipv4-active-target-adj'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "inService" and %{ipv4\_oper\_state} !~ /inService\|transition/'). You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "inService" and %\{ipv4_oper_state\} !~ /inService\|transition/'). You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | --filter-name | Filter by LDP instance name (can be a regexp). | @@ -776,8 +776,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "up" and %{oper\_state} !~ /up/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "up" and %\{oper_state\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'traffic-in-above-cir', 'traffic-in-below-cir', 'traffic-out-above-cir', 'traffic-out-below-cir'. | | --critical-* | Critical threshold. Can be: 'traffic-in-above-cir', 'traffic-in-below-cir', 'traffic-out-above-cir', 'traffic-out-below-cir'. | | --filter-name | Filter by virtual server name (can be a regexp). | @@ -788,8 +788,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Set warning threshold for status. (Default: '%{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /minor/') You can use the following variables: %{alarm\_input\_admin\_state}, %{alarm\_input\_status}, %{alarm\_output\_severity} | -| --critical-status | Set critical threshold for status (Default: '%{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /major\|critical/'). You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | +| --warning-status | Set warning threshold for status. (Default: '%\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /minor/') You can use the following variables: %\{alarm_input_admin_state\}, %\{alarm_input_status\}, %\{alarm_output_severity\} | +| --critical-status | Set critical threshold for status (Default: '%\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /major\|critical/'). You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | --filter-name | Filter alarm input (tmnxSasAlarmInputDescription) (can be a regexp). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md index f6798042c35a..e299e43ae7f4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md @@ -342,7 +342,7 @@ yum install centreon-plugin-Network-Nortel-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -351,11 +351,11 @@ yum install centreon-plugin-Network-Nortel-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------|:-----------:| | UNIT | Select the time unit for the performance data and thresholds.May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds | s | | -| UNKNOWNUNITSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{operState}, %{adminState}, %{serial} | | | +| UNKNOWNUNITSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | | | | WARNINGUNITDETECTED | Thresholds | | | | CRITICALUNITDETECTED | Thresholds | | | -| WARNINGUNITSTATUS | Define the conditions to match for the status to be WARNING (default: '%{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | %{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i | | -| CRITICALUNITSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "enable" && %{operState} =~ /fatalErr/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | %{adminState} eq "enable" && %{operState} =~ /fatalErr/i | | +| WARNINGUNITSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | %\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i | | +| CRITICALUNITSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | %\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i | | | WARNINGUNITSTOTAL | Thresholds | | | | CRITICALUNITSTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -482,7 +482,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -583,9 +583,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -611,9 +611,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-unit-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{operState}, %{adminState}, %{serial} | -| --warning-unit-status | Define the conditions to match for the status to be WARNING (default: '%{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | -| --critical-unit-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "enable" && %{operState} =~ /fatalErr/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | +| --unknown-unit-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | +| --warning-unit-status | Define the conditions to match for the status to be WARNING (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | +| --critical-unit-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | | --unit | Select the time unit for the performance data and thresholds.May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'units-total', 'unit-detected'. | @@ -642,9 +642,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oneaccess-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oneaccess-snmp.md index e0810d8014db..3b3b9a0e2605 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oneaccess-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oneaccess-snmp.md @@ -243,8 +243,8 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | CRITICALMODULECELLRADIOSNR | Thresholds | | | | WARNINGMODULESCELLRADIODETECTED | Thresholds | | | | CRITICALMODULESCELLRADIODETECTED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{signalQuality} =~ /poor/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | %{signalQuality} =~ /poor/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | %{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{signalQuality\} =~ /poor/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | %\{signalQuality\} =~ /poor/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | %\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -276,8 +276,8 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -297,7 +297,7 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | FILTERTAG | Filter probes by name | | | | WARNINGPROBECOMPLETIONTIME | Thresholds | | | | CRITICALPROBECOMPLETIONTIME | Thresholds | | | -| CRITICALPROBESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{adminStatus} eq "active" and %{status} ne "ok"'). You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | %{adminStatus} eq "active" and %{status} ne "ok" | | +| CRITICALPROBESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{adminStatus\} eq "active" and %\{status\} ne "ok"'). You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | %\{adminStatus\} eq "active" and %\{status\} ne "ok" | | | WARNINGPROBESTATUS | | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -380,7 +380,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -436,9 +436,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:----------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-cell-id | Filter cell modules by id (IMEI or MEID). | | --custom-perfdata-instances | Define perfdatas instance (default: '%(cellId) %(operator)') | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{signalQuality} =~ /poor/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{signalQuality\} =~ /poor/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | | --warning-* --critical-* | Thresholds. Can be: 'modules-cellradio-detected', 'module-cellradio-rsrp', ''module-cellradio-rsrq', 'module-cellradio-rssi', 'module-cellradio-snr'. | @@ -474,9 +474,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -512,9 +512,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-tag | Filter probes by name. | -| --unknown-probe-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | -| --warning-probe-estatus | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | -| --critical-probe-status | Define the conditions to match for the status to be CRITICAL (Default: '%{adminStatus} eq "active" and %{status} ne "ok"'). You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | +| --unknown-probe-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | +| --warning-probe-estatus | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | +| --critical-probe-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{adminStatus\} eq "active" and %\{status\} ne "ok"'). You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | | --warning-* --critical-* | Thresholds. Can be: 'probe-completion-time'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-opengear-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-opengear-snmp.md index 14834b50b371..aea160df9e19 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-opengear-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-opengear-snmp.md @@ -315,8 +315,8 @@ yum install centreon-plugin-Network-Opengear-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -463,7 +463,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -557,9 +557,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md index 1d76dde7eaaa..97ea8aa0d45f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md @@ -325,7 +325,7 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,10 +336,10 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | FILTERCOUNTERS | Only display some counters (regexp can be used). | | | | IBNAME | Filter by infiniband name (can be a regexp) | | | | IBGWNAME | Filter by infiniband gateway name (can be a regexp) | | | -| CRITICALIBGWSTATUS | Critical threshold | %{status} !~ /up/i | | +| CRITICALIBGWSTATUS | Critical threshold | %\{status\} !~ /up/i | | | WARNINGIBGWSTATUS | Warning threshold | | | -| CRITICALIBSTATUS | Set critical threshold for ib status (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /active/i | | -| WARNINGIBSTATUS | Set warning threshold for ib status. You can use the following variables: %{status}, %{display} | | | +| CRITICALIBSTATUS | Set critical threshold for ib status (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /active/i | | +| WARNINGIBSTATUS | Set warning threshold for ib status. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGIN | Warning threshold | 80 | | | CRITICALIN | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | @@ -395,7 +395,7 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -490,7 +490,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -596,9 +596,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -642,8 +642,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --speed-in | Set interface speed for incoming traffic (in Mb). | | --speed-out | Set interface speed for outgoing traffic (in Mb). | | --units-traffic | Units of thresholds for the traffic (default: '%') ('%', 'b/s'). | -| --warning-ib-status | Set warning threshold for ib status. You can use the following variables: %{status}, %{display} | -| --critical-ib-status | Set critical threshold for ib status (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | +| --warning-ib-status | Set warning threshold for ib status. You can use the following variables: %\{status\}, %\{display\} | +| --critical-ib-status | Set critical threshold for ib status (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'in', 'out'. | | --critical-* | Critical threshold. Can be: 'in', 'out'. | @@ -700,9 +700,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md index 6112a0ac93c1..5fbcdf5a7af3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md @@ -359,7 +359,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md index 688b479c98cb..30b631832139 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Peplink-Pepwave-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -294,8 +294,8 @@ yum install centreon-plugin-Network-Peplink-Pepwave-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter wan name (can be a regexp) | | | -| WARNINGHEALTHSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health\_status}, %{display} | | | -| CRITICALHEALTHSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health\_status} =~ /fail/'). You can use the following variables: %{health\_status}, %{display} | | | +| WARNINGHEALTHSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health_status\}, %\{display\} | | | +| CRITICALHEALTHSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health_status\} =~ /fail/'). You can use the following variables: %\{health_status\}, %\{display\} | | | | WARNINGSIGNAL | Warning threshold | | | | CRITICALSIGNAL | Critical threshold | | | | WARNINGTRAFFICIN | Warning threshold | | | @@ -332,7 +332,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --oid-filter='ifname' \ --oid-display='ifname' \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -431,7 +431,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -513,9 +513,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -564,8 +564,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^traffic-in$' | | --filter-name | Filter wan name (can be a regexp). | -| --warning-health-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health\_status}, %{display} | -| --critical-health-status | Define the conditions to match for the status to be CRITICAL (default: '%{health\_status} =~ /fail/'). You can use the following variables: %{health\_status}, %{display} | +| --warning-health-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health_status\}, %\{display\} | +| --critical-health-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health_status\} =~ /fail/'). You can use the following variables: %\{health_status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: Can be: 'traffic-in', 'traffic-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-perle-ids-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-perle-ids-snmp.md index 207b6f386cea..3ac1e87b76ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-perle-ids-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-perle-ids-snmp.md @@ -217,8 +217,8 @@ yum install centreon-plugin-Network-Perle-Ids-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -267,8 +267,8 @@ yum install centreon-plugin-Network-Perle-Ids-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -376,7 +376,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -443,8 +443,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -486,9 +486,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md index 596236c52f17..20ad7fb5de52 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md @@ -223,8 +223,8 @@ yum install centreon-plugin-Network-Rad-Airmux-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor\|warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor\|warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Rad-Airmux-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -383,7 +383,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -450,8 +450,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -467,9 +467,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md index 034d236e029a..b6a86340d464 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Radware-Alteon-Snmp | FILTERNAME | Filter by virtual server name (can be a regexp) | | | | WARNINGCURRENTSESSIONS | Warning threshold | | | | CRITICALCURRENTSESSIONS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | | | CRITICALTOTALSESSION | Critical threshold | | | | WARNINGTOTALSESSIONS | Warning threshold | | | | WARNINGTRAFFIC | Warning threshold | | | @@ -384,7 +384,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,8 +479,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --warning-* | Warning threshold. Can be: 'traffic', 'total-sessions', 'current-sessions'. | | --critical-* | Critical threshold. Can be: 'traffic', 'total-sessions', 'current-sessions'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | --filter-name | Filter by virtual server name (can be a regexp). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-raisecom-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-raisecom-snmp.md index 980009646289..eafa7663d175 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-raisecom-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-raisecom-snmp.md @@ -280,8 +280,8 @@ yum install centreon-plugin-Network-Raisecom-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -404,7 +404,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -470,9 +470,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md index 1d4a03faa8a7..ea8f2f365034 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md @@ -391,7 +391,7 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | CRITICALOUTDISCARD | Threshold | | | | WARNINGOUTERROR | Threshold | | | | CRITICALOUTERROR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -399,8 +399,8 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{health}, %{status} | %{health} !~ /Healthy/ \|\| %{status} !~ /running/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{health\}, %\{status\} | %\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{status\} | | | | WARNINGUPTIME | Warning thresholds in seconds | | | | CRITICALUPTIME | Critical thresholds in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -415,7 +415,7 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -544,7 +544,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -689,9 +689,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -719,8 +719,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /Healthy/ \|\| %{status} !~ /running/'). You can use the following variables: %{health}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/'). You can use the following variables: %\{health\}, %\{status\} | | --warning-uptime | Warning thresholds in seconds. | | --critical-uptime | Critical thresholds in seconds. | @@ -750,9 +750,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md index aec39080207a..b7ca5f03b2a9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md @@ -498,7 +498,7 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | CRITICALOUTDISCARD | Threshold | | | | WARNINGOUTERROR | Threshold | | | | CRITICALOUTERROR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -506,8 +506,8 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{health}, %{status} | %{health} !~ /Healthy/ \|\| %{status} !~ /running/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{health\}, %\{status\} | %\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{status\} | | | | WARNINGUPTIME | Warning thresholds in seconds | | | | CRITICALUPTIME | Critical thresholds in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -531,7 +531,7 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -664,7 +664,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -827,9 +827,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -856,8 +856,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /Healthy/ \|\| %{status} !~ /running/'). You can use the following variables: %{health}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/'). You can use the following variables: %\{health\}, %\{status\} | | --warning-uptime | Warning thresholds in seconds. | | --critical-uptime | Critical thresholds in seconds. | @@ -894,9 +894,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md index b1f399fccff5..040753ae2f6e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md @@ -264,7 +264,7 @@ yum install centreon-plugin-Network-Routers-Atrica-Snmp | WARNINGOUTEIR | Thresholds | | | | CRITICALOUTEIRDISCARD | Thresholds | | | | WARNINGOUTEIRDISCARD | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%{admstatus} eq "on" and %{opstatus} ne "inService"' '%{admstatus} eq "up" and %{opstatus} ne "up"' You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%\{admstatus\} eq "on" and %\{opstatus\} ne "inService"' '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -359,9 +359,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-status | Check interface status (by default if no --add-* option is set). | | --add-traffic | Check interface traffic. | | --add-errors | Check interface errors. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up" or %{opstatus} eq "inService"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%{admstatus} eq "on" and %{opstatus} ne "inService"' '%{admstatus} eq "up" and %{opstatus} ne "up"' You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up" or %\{opstatus\} eq "inService"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%\{admstatus\} eq "on" and %\{opstatus\} ne "inService"' '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'in-cir', 'in-eir', 'out-cir', 'out-eir', 'in-eir-discard', 'out-eir-discard'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md index 3aac23825bad..9df1b611faeb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md @@ -327,8 +327,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTER | Filter by peer identifier (can be regexp) | | | | FILTERREMOTEIP | Filter by remote ip address (can be regexp) | | | | FILTERLOCALAS | Filter by local AS (can be regexp) | | | -| CRITICALSTATUS | Specify critical threshold (default: '%{peer\_status} =~ /running/ && %{peer\_state} !~ /established/'). Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | %{peer\_status} =~ /running/ && %{peer\_state} !~ /established/ | | -| WARNINGSTATUS | Specify warning threshold. Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | | | +| CRITICALSTATUS | Specify critical threshold (default: '%\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/'). Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | %\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/ | | +| WARNINGSTATUS | Specify warning threshold. Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -400,8 +400,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERPEER | Filter entities and/or peer | | | | WARNINGLASTCHANGE | Warning threshold in seconds | | | | CRITICALLASTCHANGE | Critical threshold in seconds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /operational/i'). You can use the following variables: %{state} | %{state} !~ /operational/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /operational/i'). You can use the following variables: %\{state\} | %\{state\} !~ /operational/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -414,8 +414,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERTO | Filter LSPs | | | | WARNINGLASTTRANSITION | Warning threshold | | | | CRITICALLASTTRANSITION | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | %{state} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | %\{state\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | WARNINGTRANSITIONCOUNT | Warning threshold | | | | CRITICALTRANSITIONCOUNT | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -442,8 +442,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERNAME | Filter sessions | | | | FILTERFROM | Filter sessions | | | | FILTERTO | Filter sessions | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | %{state} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | %\{state\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -480,7 +480,7 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | CRITICALIN | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 90 | | | WARNINGOUT | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 80 | | | CRITICALOUT | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -577,7 +577,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -643,8 +643,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-peer | Filter by peer identifier (can be regexp) | | --filter-remote-ip | Filter by remote ip address (can be regexp) | | --filter-local-as | Filter by local AS (can be regexp) | -| --warning-status | Specify warning threshold. Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | -| --critical-status | Specify critical threshold (default: '%{peer\_status} =~ /running/ && %{peer\_state} !~ /established/'). Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | +| --warning-status | Specify warning threshold. Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | +| --critical-status | Specify critical threshold (default: '%\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/'). Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | @@ -725,8 +725,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter entities and/or peer. Can be: 'entity', 'peer' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /operational/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /operational/i'). You can use the following variables: %\{state\} | | --warning-last-change | Warning threshold in seconds. | | --critical-last-change | Critical threshold in seconds. | @@ -736,8 +736,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter LSPs. Can be: 'name', 'from', 'to' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | | --warning-* | Warning threshold. Can be: 'transition-count', 'last-transition' (seconds). | | --critical-* | Critical threshold. Can be: 'transition-count', 'last-transition' (seconds). | @@ -755,8 +755,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter sessions. Can be: 'name', 'from', 'to' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | @@ -784,9 +784,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical metrics. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will superseed --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md index a7e991f55e6f..cc129499ff68 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md @@ -281,7 +281,7 @@ yum install centreon-plugin-Network-Routers-Peplink-Balance-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | #NOM? | | @@ -318,7 +318,7 @@ yum install centreon-plugin-Network-Routers-Peplink-Balance-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | #NOM? | | @@ -405,7 +405,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -495,9 +495,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -544,9 +544,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-redback-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-redback-snmp.md index 2c39b810d843..361e9787c05b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-redback-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-routers-redback-snmp.md @@ -338,7 +338,7 @@ yum install centreon-plugin-Network-Routers-Redback-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -375,7 +375,7 @@ yum install centreon-plugin-Network-Routers-Redback-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -465,7 +465,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -578,9 +578,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -626,9 +626,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md index 88a6024da8e1..4b2fc518a9f7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md @@ -288,8 +288,8 @@ yum install centreon-plugin-Network-Ruckus-Icx-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --use-new-perfdata | | @@ -318,7 +318,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -416,7 +416,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -501,9 +501,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md index e4309d29595f..4fc0c7fa4f87 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md @@ -344,8 +344,8 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| | FILTERNAME | Filter by AP name (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{configuration\_status} !~ /^Up-to-date$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | %{configuration\_status} !~ /^Up-to-date$/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /^Disconnect$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | %{connection\_status} =~ /^Disconnect$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{configuration_status\} !~ /^Up-to-date$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | %\{configuration_status\} !~ /^Up-to-date$/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /^Disconnect$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | %\{connection_status\} =~ /^Disconnect$/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -444,7 +444,7 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | CRITICALOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -522,7 +522,7 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -628,7 +628,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -683,8 +683,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by AP name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{configuration\_status} !~ /^Up-to-date$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /^Disconnect$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{configuration_status\} !~ /^Up-to-date$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /^Disconnect$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | @@ -784,9 +784,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -874,9 +874,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md index 7e6ccbcfd933..b821eec78570 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md @@ -283,8 +283,8 @@ yum install centreon-plugin-Network-Ruckus-Smartzone-Snmp | FILTERNAME | Filter by access point name (can be a regexp) | .* | | | WARNINGCONNECTIONCLIENTDEVICESAUTHORIZED | Thresholds | | | | CRITICALCONNECTIONCLIENTDEVICESAUTHORIZED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -322,8 +322,8 @@ yum install centreon-plugin-Network-Ruckus-Smartzone-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --use-new-perfdata | | @@ -463,7 +463,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -530,9 +530,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-name | Filter by access point name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'connection-client-devices-authorized'. | @@ -571,9 +571,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-snmp.md index d76017f9b27b..963065f127dc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-snmp.md @@ -251,7 +251,7 @@ yum install centreon-plugin-Network-Ruckus-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -352,7 +352,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -442,9 +442,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md index 2a249bb82f9c..263116386683 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md @@ -231,8 +231,8 @@ yum install centreon-plugin-Network-Ruckus-Zonedirector-Snmp | CRITICALCPUUTILIZATION | Thresholds | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{zd\_connection\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{zd\_connection\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{zd_connection_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{zd_connection_status\} | | | | WARNINGTRAFFICOUT | Thresholds | | | | CRITICALTRAFFICOUT | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -339,7 +339,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -406,9 +406,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by access point name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{zd\_connection\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{zd\_connection\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{zd\_connection\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{zd_connection_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{zd_connection_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{zd_connection_status\} | | --warning-* --critical-* | Thresholds. Can be: 'memory-usage', 'memory-usage-free', 'memory-usage-prct', 'traffic-in', 'traffic-out', 'cpu-utilization', 'connection-accesspoints', 'connection-client-devices-authorized', 'connection-rogue-devices'. | @@ -416,9 +416,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{system\_status}, %{peer\_connected\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{system\_status}, %{peer\_connected\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system\_status}, %{peer\_connected\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | | --warning-* --critical-* | Thresholds. Can be: 'memory-usage', 'usage-free', 'usage-prct', 'traffic-in', 'traffic-out', 'cpu-utilization', 'connection-accesspoints', 'connection-client-devices-authorized', 'connection-rogue-devices'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruggedcom.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruggedcom.md index 0ce2180c5f6a..2d6cd016f555 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruggedcom.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ruggedcom.md @@ -285,7 +285,7 @@ yum install centreon-plugin-Network-Ruggedcom | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -374,7 +374,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -483,9 +483,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-securactive-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-securactive-snmp.md index 204abadea5ba..2510d7203d81 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-securactive-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-securactive-snmp.md @@ -293,7 +293,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-silverpeak-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-silverpeak-snmp.md index 6d26fa3c0b2f..6697988d8dc0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-silverpeak-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-silverpeak-snmp.md @@ -219,8 +219,8 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -228,8 +228,8 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Trigger warning on %{operStatus} values | | | -| CRITICALSTATUS | Trigger critical on %{operStatus} values (default: '%{operStatus} !~ /(Normal)/') | | | +| WARNINGSTATUS | Trigger warning on %\{operStatus\} values | | | +| CRITICALSTATUS | Trigger critical on %\{operStatus\} values (default: '%\{operStatus\} !~ /(Normal)/') | | | @@ -265,7 +265,7 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -363,7 +363,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -430,8 +430,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -439,8 +439,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------| -| --warning-status | Trigger warning on %{operStatus} values | -| --critical-status | Trigger critical on %{operStatus} values (default: '%{operStatus} !~ /(Normal)/') | +| --warning-status | Trigger warning on %\{operStatus\} values | +| --critical-status | Trigger critical on %\{operStatus\} values (default: '%\{operStatus\} !~ /(Normal)/') | @@ -467,9 +467,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md index 4a61b3a0fd0c..46a39db9dfd3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md @@ -397,8 +397,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALCHANNELSWAITINGFORDIGITS | Thresholds | | | | WARNINGCHANNELSWAITINGFORROUTE | Thresholds | | | | CRITICALCHANNELSWAITINGFORROUTE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /up\|idle\|connected/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /up\|idle\|connected/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -440,8 +440,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALCHANNELSACTIVE | Thresholds | | | | WARNINGCPUUTILIZATION | Thresholds | | | | CRITICALCPUUTILIZATION | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{display} | %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -464,8 +464,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -620,7 +620,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -698,8 +698,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-slot-id | Filter channels by slot ID (can be a regexp). | | --filter-port-id | Filter channels by port ID (can be a regexp). | | --filter-channel-id | Filter channels by channel ID (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'channels-total', 'channels-outofservice', 'channels-idle', 'channels-pending', 'channels-waitingforroute', 'channels-actionlist', 'channels-waitingfordigits', 'channels-remotesetup', 'channels-peersetup', 'channels-alerting', 'channels-inbandinfo', 'channels-connected', 'channels-tonegeneration', 'channels-releasing', 'channels-aborting', 'channels-resetting', 'channels-up', 'channels-down', 'channel-lifetime'. | @@ -777,8 +777,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'channels-active'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{display\} | @@ -805,9 +805,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sophos-es-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sophos-es-snmp.md index 901d454d5c05..874d433e7047 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sophos-es-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-sophos-es-snmp.md @@ -296,7 +296,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-api.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-api.md index 5ddcdf691178..b86fa5bc3c4d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-api.md @@ -268,11 +268,11 @@ yum install centreon-plugin-Network-Stormshield-Api | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNMEMBERLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{linkStatus} =~ /unknown/i'). You can use the following variables: %{linkStatus}, %{name} | %{linkStatus} =~ /unknown/i | | -| WARNINGMEMBERCONFIG | Define the conditions to match for the status to be WARNING (default: '%{isConfigSync} eq "no"'). You can use the following variables: %{isConfigSync}, %{name} | %{isConfigSync} eq "no" | | -| CRITICALMEMBERCONFIG | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{isConfigSync}, %{name} | | | -| CRITICALMEMBERLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{linkStatus} =~ /failed\|failing/i'). You can use the following variables: %{linkStatus}, %{name} | %{linkStatus} =~ /failed\|failing/i | | -| WARNINGMEMBERLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkStatus}, %{name} | | | +| UNKNOWNMEMBERLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{linkStatus\} =~ /unknown/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | %\{linkStatus\} =~ /unknown/i | | +| WARNINGMEMBERCONFIG | Define the conditions to match for the status to be WARNING (default: '%\{isConfigSync\} eq "no"'). You can use the following variables: %\{isConfigSync\}, %\{name\} | %\{isConfigSync\} eq "no" | | +| CRITICALMEMBERCONFIG | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{isConfigSync\}, %\{name\} | | | +| CRITICALMEMBERLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{linkStatus\} =~ /failed\|failing/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | %\{linkStatus\} =~ /failed\|failing/i | | +| WARNINGMEMBERLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkStatus\}, %\{name\} | | | | WARNINGMEMBERQUALITY | Thresholds | | | | CRITICALMEMBERQUALITY | Thresholds | | | | WARNINGMEMBERSDETECTED | Thresholds | | | @@ -291,8 +291,8 @@ yum install centreon-plugin-Network-Stormshield-Api | CRITICALMEMBERSRUNNING | Thresholds | | | | WARNINGMEMBERSSTARTING | Thresholds | | | | CRITICALMEMBERSSTARTING | Thresholds | | | -| WARNINGMEMBERSTATE | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{name}. | | | -| CRITICALMEMBERSTATE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{name}. | | | +| WARNINGMEMBERSTATE | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{name\}. | | | +| CRITICALMEMBERSTATE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{name\}. | | | | WARNINGMEMBERSWAITINGPEER | Thresholds | | | | CRITICALMEMBERSWAITINGPEER | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -311,8 +311,8 @@ yum install centreon-plugin-Network-Stormshield-Api | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERSERIAL | Filter by firewalls by serial (can be a regexp) | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /minor/i | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /major/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /minor/i | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -330,8 +330,8 @@ yum install centreon-plugin-Network-Stormshield-Api | CRITICALPACKETSACCEPTED | Thresholds | | | | WARNINGPACKETSBLOCKED | Thresholds | | | | CRITICALPACKETSBLOCKED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: "%{state} eq 'enabled' and %{plugged} eq 'unplugged'") You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | %{state} eq "enabled" and %{plugged} eq "unplugged" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: "%\{state\} eq 'enabled' and %\{plugged\} eq 'unplugged'") You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | %\{state\} eq "enabled" and %\{plugged\} eq "unplugged" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -463,7 +463,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -525,15 +525,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-member-state | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{name} | -| --warning-member-state | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{name} | -| --critical-member-state | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{name} | -| --unknown-member-link-status | Define the conditions to match for the status to be UNKNOWN (default: '%{linkStatus} =~ /unknown/i'). You can use the following variables: %{linkStatus}, %{name} | -| --warning-member-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkStatus}, %{name} | -| --critical-member-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{linkStatus} =~ /failed\|failing/i'). You can use the following variables: %{linkStatus}, %{name} | -| --unknown-member-config | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{isConfigSync}, %{name} | -| --warning-member-config | Define the conditions to match for the status to be WARNING (default: '%{isConfigSync} eq "no"'). You can use the following variables: %{isConfigSync}, %{name} | -| --critical-member-config | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{isConfigSync}, %{name} | +| --unknown-member-state | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{name\} | +| --warning-member-state | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{name\} | +| --critical-member-state | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{name\} | +| --unknown-member-link-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{linkStatus\} =~ /unknown/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | +| --warning-member-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkStatus\}, %\{name\} | +| --critical-member-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{linkStatus\} =~ /failed\|failing/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | +| --unknown-member-config | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{isConfigSync\}, %\{name\} | +| --warning-member-config | Define the conditions to match for the status to be WARNING (default: '%\{isConfigSync\} eq "no"'). You can use the following variables: %\{isConfigSync\}, %\{name\} | +| --critical-member-config | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{isConfigSync\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'member-quality', 'members-detected', 'members-none', 'members-starting', 'members-waiting-peer', 'members-running', 'members-ready', 'members-reboot', 'members-down', 'members-initializing'. | @@ -554,9 +554,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-serial | Filter by firewalls by serial (can be a regexp). | -| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | +| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | @@ -569,9 +569,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-traffic | Check interface traffic. | | --add-errors | Check interface errors. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: "%{state} eq 'enabled' and %{plugged} eq 'unplugged'") You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: "%\{state\} eq 'enabled' and %\{plugged\} eq 'unplugged'") You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | | --warning-* --critical-* | Thresholds. Can be: 'in-traffic', 'out-traffic', 'packets-accepted', 'packets-blocked', | | --speed | Set interface speed (in Mb). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-snmp.md index 5aa4c5fae57c..0e57b76c6e14 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-snmp.md @@ -406,8 +406,8 @@ yum install centreon-plugin-Network-Stormshield-Snmp | CRITICALDEADNODES | Critical threshold for dead nodes (absolute unless --percent is used) | | | | WARNINGHEALTH | Warning threshold for health level (example: --warning 90:) | | | | CRITICALHEALTH | Critical threshold for health level (example --critical 80:) | | | -| WARNINGSTATE | Set warning threshold for state. You can use the following variables: %{state}, %{role} | | | -| CRITICALSTATE | Set critical threshold for state. (default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{role} | | | +| WARNINGSTATE | Set warning threshold for state. You can use the following variables: %\{state\}, %\{role\} | | | +| CRITICALSTATE | Set critical threshold for state. (default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{role\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -423,9 +423,9 @@ yum install centreon-plugin-Network-Stormshield-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSERVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /minor/i | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /major/i | | +| UNKNOWNSERVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /minor/i | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -534,7 +534,7 @@ yum install centreon-plugin-Network-Stormshield-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -545,8 +545,8 @@ yum install centreon-plugin-Network-Stormshield-Snmp | FILTERID | Filter by ID (regexp can be used) | | | | FILTERSRCIP | Filter by source IP address (regexp can be used) | | | | FILTERDSTIP | Filter by destination IP address (regexp can be used) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} eq "dead"'). You can use the following variables: %{state}, %{srcIp}, %{dstIp} | %{state} eq "dead" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} eq "dead"'). You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | %\{state\} eq "dead" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | | | | WARNINGTRAFFIC | Thresholds | | | | CRITICALTRAFFIC | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -580,7 +580,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-id='' \ --filter-src-ip='' \ --filter-dst-ip='' \ - --warning-status='%{state} eq "dead"' \ + --warning-status='%\{state\} eq "dead"' \ --critical-status='' \ --warning-traffic='' \ --critical-traffic='' \ @@ -657,7 +657,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -805,8 +805,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-health | Critical threshold on health level (example --critical 80:). | | --warning-dead-nodes | Warning threshold on dead nodes (absolute unless --percent is used). | | --critical-dead-nodes | Critical threshold on dead nodes (absolute unless --percent is used). | -| --warning-state | Set warning threshold for state. You can use the following variables: %{state}, %{role}. | -| --critical-state | Set critical threshold for state. (default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{role}. | +| --warning-state | Set warning threshold for state. You can use the following variables: %\{state\}, %\{role\}. | +| --critical-state | Set critical threshold for state. (default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{role\}. | | --percent | Set this option if you want to warn on percent . | @@ -827,9 +827,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-serial | Filter by firewall serial (can be a regexp). | -| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | +| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | @@ -914,9 +914,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -957,9 +957,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-id | Filter by ID (regexp can be used). | | --filter-src-ip | Filter by source IP address (regexp can be used). | | --filter-dst-ip | Filter by destination IP address (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} eq "dead"'). You can use the following variables: %{state}, %{srcIp}, %{dstIp} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} eq "dead"'). You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | | --warning-* --critical-* | Thresholds. Can be: 'vpn-detected', 'traffic', 'traffic-in', 'traffic-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-ssh.md index bb7865f2bc89..43c899841b39 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-stormshield-ssh.md @@ -300,7 +300,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md index dd3f5c879742..642e7592a8ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md @@ -289,8 +289,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -308,8 +308,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -319,8 +319,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | WARNINGCHASSISDETECTED | Thresholds | | | | CRITICALCHASSISDETECTED | Thresholds | | | -| CRITICALCHASSISSTATUS | Define the conditions to match for the status to be CRITICAL (default: %{status} !~ /init\|running/) You can use the following variables: %{role}, %{status}, %{mac} | %{status} !~ /init\|running/ | | -| WARNINGCHASSISSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{status}, %{mac} | | | +| CRITICALCHASSISSTATUS | Define the conditions to match for the status to be CRITICAL (default: %\{status\} !~ /init\|running/) You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | %\{status\} !~ /init\|running/ | | +| WARNINGCHASSISSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -349,7 +349,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -425,7 +425,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -525,9 +525,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -562,17 +562,17 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | | Option | Description | |:--------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-chassis-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{status}, %{mac} | -| --warning-chassis-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{status}, %{mac} | -| --critical-chassis-status | Define the conditions to match for the status to be CRITICAL (default: %{status} !~ /init\|running/) You can use the following variables: %{role}, %{status}, %{mac} | +| --unknown-chassis-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | +| --warning-chassis-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | +| --critical-chassis-status | Define the conditions to match for the status to be CRITICAL (default: %\{status\} !~ /init\|running/) You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | | --warning-* --critical-* | Thresholds. Can be: 'chassis-detected'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md index be4be5770a86..b8e9887ad908 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md @@ -326,7 +326,7 @@ yum install centreon-plugin-Network-Switchs-Arista-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -379,7 +379,7 @@ yum install centreon-plugin-Network-Switchs-Arista-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -479,7 +479,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -583,9 +583,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -655,9 +655,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md index b0b79bedae9f..b4630f78920c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md @@ -357,16 +357,16 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------------|:--------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| WARNINGCONNECTEDCURRENT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALCONNECTEDCURRENT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGCONTROLLERBOOTSTRAP | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALCONTROLLERBOOTSTRAP | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGREBOOT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALREBOOT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALSTATUS | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | %{status} !~ /up/i | | -| WARNINGSTATUS | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGUPTIME | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALUPTIME | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | +| WARNINGCONNECTEDCURRENT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALCONNECTEDCURRENT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGCONTROLLERBOOTSTRAP | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALCONTROLLERBOOTSTRAP | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGREBOOT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALREBOOT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALSTATUS | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGUPTIME | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALUPTIME | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -374,10 +374,10 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------------|:----------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| WARNINGCONNECTEDCURRENT | Warning threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | | | -| CRITICALCONNECTEDCURRENT | Critical threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | | | -| CRITICALSTATUS | Critical threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | %{status} !~ /active/i | | -| WARNINGSTATUS | Warning threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | | | +| WARNINGCONNECTEDCURRENT | Warning threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | | | +| CRITICALCONNECTEDCURRENT | Critical threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | | | +| CRITICALSTATUS | Critical threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Warning threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -426,8 +426,8 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Critical threshold. Can use special variables like: %{key}, %{service}, %{flag}, %{expires} (default: '%{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400)') | %{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400) | | -| WARNINGSTATUS | Warning threshold. Can use special variables like:%{key}, %{service}, %{flag}, %{expires} (default: '') | | | +| CRITICALSTATUS | Critical threshold. Can use special variables like: %\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '%\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400)') | %\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400) | | +| WARNINGSTATUS | Warning threshold. Can use special variables like:%\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -485,7 +485,7 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -626,7 +626,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -689,7 +689,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* --critical-* | Thresholds. Can be: 'connected-current' (global), 'uptime', 'controller-bootstrap', 'reboot', 'status' (per AP). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | +| --warning-* --critical-* | Thresholds. Can be: 'connected-current' (global), 'uptime', 'controller-bootstrap', 'reboot', 'status' (per AP). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | --filter-* | Filter by 'ip', 'name', 'group' (regexp can be used). | @@ -697,8 +697,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Warning threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | -| --critical-* | Critical threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | +| --warning-* | Warning threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | +| --critical-* | Critical threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | | --filter-* | Filter by 'ip', 'name', 'location' (regexp can be used). | @@ -754,8 +754,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Warning threshold. Can use special variables like:%{key}, %{service}, %{flag}, %{expires} (default: '') | -| --critical-status | Critical threshold. Can use special variables like: %{key}, %{service}, %{flag}, %{expires} (default: '%{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400)') | +| --warning-status | Warning threshold. Can use special variables like:%\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '') | +| --critical-status | Critical threshold. Can use special variables like: %\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '%\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400)') | @@ -790,9 +790,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -848,9 +848,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md index e630ab59435d..7cd6fbaacced 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md @@ -306,7 +306,7 @@ yum install centreon-plugin-Network-Switchs-Brocade-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -343,7 +343,7 @@ yum install centreon-plugin-Network-Switchs-Brocade-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -432,7 +432,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -536,9 +536,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -583,9 +583,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -630,9 +630,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md index d0481e11d36b..61d10aeb5928 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md @@ -306,7 +306,7 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -315,8 +315,8 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -353,7 +353,7 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -444,7 +444,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -539,9 +539,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -568,8 +568,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -596,9 +596,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md index f52d9497a20f..cc5f7c2a3610 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md @@ -256,8 +256,8 @@ yum install centreon-plugin-Network-Dell-Xseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -295,7 +295,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -366,7 +366,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -460,9 +460,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md index c5d061396af2..df514df8ea19 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md @@ -232,8 +232,8 @@ yum install centreon-plugin-Network-Switchs-Hirschmann | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status} | %{config\_status} =~ /notInSync\|outOfSync/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\} | %\{config_status\} =~ /notInSync\|outOfSync/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -313,7 +313,7 @@ yum install centreon-plugin-Network-Switchs-Hirschmann | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -429,7 +429,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -463,8 +463,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default : '%{config\_status} =~ /notInSync\|outOfSync/'). You can use the following variables: %{config\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default : '%\{config_status\} =~ /notInSync\|outOfSync/'). You can use the following variables: %\{config_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\} | @@ -531,9 +531,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md index 75e220aaebe7..9ead83510f00 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md @@ -281,10 +281,10 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | %{role} ne %{roleLast} | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | %{admin\_status} eq "up" and %{oper\_status} ne "up" | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | %\{role\} ne %\{roleLast\} | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | %\{admin_status\} eq "up" and %\{oper_status\} ne "up" | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -321,7 +321,7 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | WARNINGIN | Threshold on warning-in-traffic | 80 | | | CRITICALOUT | Threshold on critical-in-traffic | 90 | | | WARNINGOUT | Threshold on warning-out-traffic | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -332,10 +332,10 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | FILTERMEMBERSERIAL | Filter members by serial (can be a regexp) | | | | WARNINGCPUUTILIZATION | Threshold | | | | CRITICALCPUUTILIZATION | Threshold | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %{link\_status}, %{display} | %{link\_status} eq "down" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{stateLast} | %{state} ne %{stateLast} \|\| %{state} =~ /communicationFailure\|incompatibleOS/i | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{stateLast} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} eq "down" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{stateLast\} | %\{state\} ne %\{stateLast\} \|\| %\{state\} =~ /communicationFailure\|incompatibleOS/i | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{stateLast\} | | | | WARNINGMEMBERSTOTAL | Threshold | | | | CRITICALMEMBERSTOTAL | Threshold | | | | WARNINGMEMORYUSAGE | Threshold | | | @@ -344,8 +344,8 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | CRITICALMEMORYUSAGEFREE | Threshold | | | | WARNINGMEMORYUSAGEPRCT | Threshold | | | | CRITICALMEMORYUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} !~ /active/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -370,7 +370,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --snmp-community='my-snmp-community' \ --filter-member-serial='' \ --warning-member-status='' \ - --critical-member-status='%{state} ne %{stateLast} || %{state} =~ /communicationFailure|incompatibleOS/i' \ + --critical-member-status='%\{state\} ne %\{stateLast\} || %\{state\} =~ /communicationFailure|incompatibleOS/i' \ --warning-cpu-utilization='' \ --critical-cpu-utilization='' \ --warning-memory-usage='' \ @@ -380,11 +380,11 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-memory-usage-prct='' \ --critical-memory-usage-prct='' \ --warning-status='' \ - --critical-status='%{status} !~ /active/i' \ + --critical-status='%\{status\} !~ /active/i' \ --warning-members-total='' \ --critical-members-total='' \ --warning-link-status='' \ - --critical-link-status='%{link\_status} eq "down"' \ + --critical-link-status='%\{link_status\} eq "down"' \ --verbose ``` @@ -469,7 +469,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -534,12 +534,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\ |yyyy$' | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast}'). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admin\_status} eq "up" and %{oper\_status} ne "up"'). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\}'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admin_status\} eq "up" and %\{oper_status\} ne "up"'). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | @@ -555,9 +555,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'voltage' (mV), 'module-temperature' (C), 'poe-power-actual'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -592,8 +592,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --add-poe | Check power over thernet. | | --add-optical | Check interface optical metrics. | -| --warning-poe-status | Set warning threshold for poe status. You can use the following variables: %{admstatus}, %{opstatus}, %{poestatus}, %{display} | -| --critical-poe-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{poestatus}, %{display} | +| --warning-poe-status | Set warning threshold for poe status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{poestatus\}, %\{display\} | +| --critical-poe-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{poestatus\}, %\{display\} | @@ -602,15 +602,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-member-serial | Filter members by serial (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast} \|\| %{state} =~ /communicationFailure\|incompatibleOS/i'). You can use the following variables: %{state}, %{stateLast} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} eq "down"'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\} \|\| %\{state\} =~ /communicationFailure\|incompatibleOS/i'). You can use the following variables: %\{state\}, %\{stateLast\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} eq "down"'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total', 'memory-usage-prct', 'memory-usage', 'memory-usage-free', 'cpu-utilization'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md index 60e213862b15..58d4daa88507 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md @@ -351,7 +351,7 @@ yum install centreon-plugin-Network-Switchs-Juniper-Ex-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -442,7 +442,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -597,9 +597,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md index cf092a530829..fba70b663227 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md @@ -211,8 +211,8 @@ yum install centreon-plugin-Network-Switchs-Mrv-Optiswitch-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "enabled" and %{linkstatus} ne "true"'). You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "enabled" and %\{linkstatus\} ne "true"'). You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -249,7 +249,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --add-status \ --add-traffic \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -312,7 +312,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -397,9 +397,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "enabled" and %{linkstatus} eq "true"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "enabled" and %{linkstatus} ne "true"'). You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "enabled" and %\{linkstatus\} eq "true"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "enabled" and %\{linkstatus\} ne "true"'). You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'total-link-up', 'total-link-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md index b9ce2a42b80f..d6b314a26da8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md @@ -237,7 +237,7 @@ yum install centreon-plugin-Network-Symbol-Wing-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -296,7 +296,7 @@ yum install centreon-plugin-Network-Symbol-Wing-Snmp | CRITICALIN | Thresholds | 80 | | | WARNINGOUT | Thresholds | 90 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -323,7 +323,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='80' \ --warning-out-traffic='90' \ @@ -383,7 +383,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -457,9 +457,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -514,9 +514,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teldat-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teldat-snmp.md index ae2a155338db..f62e41060769 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teldat-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teldat-snmp.md @@ -263,8 +263,8 @@ yum install centreon-plugin-Network-Teldat-Snmp | CRITICALMODULECELLRADIOSNR | Thresholds on cellular mobile signal versus noise ratio (SINR). | | | | WARNINGMODULESCELLRADIODETECTED | Thresholds on detected cellular mobile(s) | | | | CRITICALMODULESCELLRADIODETECTED | Thresholds on detected cellular mobile(s) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | '%{interfaceState} =~ /disconnect/' | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | '%{simStatus} =~ /LOCKED/ or %{simStatus} =~ /DETECTING/' | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | '%\{interfaceState\} =~ /disconnect/' | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | '%\{simStatus\} =~ /LOCKED/ or %\{simStatus\} =~ /DETECTING/' | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -300,8 +300,8 @@ yum install centreon-plugin-Network-Teldat-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -410,7 +410,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -467,10 +467,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-module | Filter cellular radio interfaces by module. | | --filter-imei | Filter cellular radio interfaces by IMEI. | | --filter-interface-type | Filter cellular radio interfaces by type. | -| --custom-perfdata-instances | Define perfdata instances (default: '%(cellId) %(operator)'). You can use the following variables: %{cellId}, %{simIcc}, %{operator} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{interfaceState} =~ /disconnect/'). You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} =~ /LOCKED/ \|\| %{simStatus} =~ /DETECTING/'). You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | +| --custom-perfdata-instances | Define perfdata instances (default: '%(cellId) %(operator)'). You can use the following variables: %\{cellId\}, %\{simIcc\}, %\{operator\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{interfaceState\} =~ /disconnect/'). You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} =~ /LOCKED/ \|\| %\{simStatus\} =~ /DETECTING/'). You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | | --warning-* --critical-* | Thresholds. Can be: 'modules-cellradio-detected', 'module-cellradio-rsrp', ''module-cellradio-rsrq', 'module-cellradio-rscp', 'module-cellradio-csq' 'module-cellradio-snr'. | @@ -505,9 +505,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Set critical threshold for status. (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Set critical threshold for status. (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teltonika-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teltonika-snmp.md index 5f6d635b12b5..d88900f22e93 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teltonika-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-teltonika-snmp.md @@ -220,8 +220,8 @@ yum install centreon-plugin-Network-Teltonika-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -235,8 +235,8 @@ yum install centreon-plugin-Network-Teltonika-Snmp | CRITICALSIGNALRECEIVEQUALITY | Thresholds | | | | WARNINGSIGNALSTRENGTH | Thresholds | | | | CRITICALSIGNALSTRENGTH | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | %{connectionState} !~ /connected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | %\{connectionState\} !~ /connected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -265,7 +265,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --hostname='10.0.0.1' \ --snmp-version='2c' \ --snmp-community='my-snmp-community' \ - --critical-status='%{connectionState} !~ /connected/i' \ + --critical-status='%\{connectionState\} !~ /connected/i' \ --verbose ``` @@ -321,7 +321,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -395,9 +395,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -424,8 +424,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connectionState} !~ /connected/i'). You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connectionState\} !~ /connected/i'). You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | | --warning-* --critical-* | Thresholds. Can be: 'signal-strength', 'temperature', 'traffic-in', 'traffic-out' 'signal-receive-power', 'signal-receive-quality'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-tplink-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-tplink-snmp.md index 4587ec64845e..752b5fc74460 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-tplink-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-tplink-snmp.md @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Tplink-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --use-new-perfdata | | @@ -365,7 +365,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -446,9 +446,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md index 8e70e6f8181b..fa55ccbce8c3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md @@ -254,8 +254,8 @@ yum install centreon-plugin-Network-Ubiquiti-Airfiber-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -294,8 +294,8 @@ yum install centreon-plugin-Network-Ubiquiti-Airfiber-Snmp | CRITICALCHAIN0SIGNALRECEIVEPOWER | Threshold | | | | WARNINGCHAIN1SIGNALRECEIVEPOWER | Threshold | | | | CRITICALCHAIN1SIGNALRECEIVEPOWER | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{enabled}, %{state}, %{name} | %{enabled} eq "yes" and %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{enabled}, %{state}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | %\{enabled\} eq "yes" and %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | | | | WARNINGTRAFFICIN | Threshold | | | | CRITICALTRAFFICIN | Threshold | | | | WARNINGTRAFFICOUT | Threshold | | | @@ -410,7 +410,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -464,9 +464,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -508,9 +508,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter interface by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{enabled}, %{state}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{enabled}, %{state}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{state} eq "down"'). You can use the following variables: %{enabled}, %{state}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{state\} eq "down"'). You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'chain0-signal-receive-power', 'chain1-signal-receive-power'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md index 60991314c7b0..f20949f034ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md @@ -355,8 +355,8 @@ yum install centreon-plugin-Network-Ubiquiti-Unifi-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --use-new-perfdata | | @@ -402,11 +402,11 @@ yum install centreon-plugin-Network-Ubiquiti-Unifi-Snmp |:------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | FILTERAPNAME | Filter virtual access points by name (can be a regexp) | | | | FILTERAPSSID | Filter virtual access points by SSID (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{ssid}, %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | | | WARNINGCLIENTSCONNECTED | Thresholds | | | | CRITICALCLIENTSCONNECTED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{name}, %{ssid}, %{status} | %{status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{ssid}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | %\{status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALCLIENTSCONNECTED | Thresholds | | | @@ -441,7 +441,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-ssid='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} eq "down"' \ + --critical-status='%\{status\} eq "down"' \ --warning-total='' \ --critical-total='' \ --warning-total-clients-connected='' \ @@ -514,7 +514,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -637,9 +637,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -733,9 +733,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter virtual access points by name (can be a regexp). | | --filter-ssid | Filter virtual access points by SSID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{ssid}, %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{ssid}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{name}, %{ssid}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-clients-connected', 'clients-connected', 'traffic-in', 'traffic-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ucopia-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ucopia-snmp.md index bcecfacec04d..127022350517 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ucopia-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-ucopia-snmp.md @@ -234,10 +234,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -255,10 +255,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | %{status} eq "stopped" | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "stopped" | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -276,10 +276,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -297,10 +297,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -393,7 +393,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -448,10 +448,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -460,10 +460,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -472,10 +472,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -484,10 +484,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-versa-director-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-versa-director-restapi.md index 983be4141806..74ab1952ab44 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-versa-director-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-versa-director-restapi.md @@ -154,7 +154,7 @@ Une fois le Plugin installé, vous pouvez tester directement celui-ci en ligne d --organization='.*' \ --filter-device-name='^CENFRGW101$' \ --warning-status='' \ - --critical-status='%{ping_status} ne "reachable" or %{services_status} ne "good"' \ + --critical-status='%\{ping_status\} ne "reachable" or %\{services_status\} ne "good"' \ --verbose ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-watchguard-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-watchguard-snmp.md index caf56fb5b860..903b4c7aa27b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-watchguard-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-watchguard-snmp.md @@ -275,16 +275,16 @@ yum install centreon-plugin-Network-Watchguard-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------------|:----------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state} | | | -| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state} | | | +| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\} | | | +| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\} | | | | WARNINGMEMBERHEALTHHARDWARE | Thresholds | | | | CRITICALMEMBERHEALTHHARDWARE | Thresholds | | | | WARNINGMEMBERHEALTHSYSTEM | Thresholds | | | | CRITICALMEMBERHEALTHSYSTEM | Thresholds | | | | WARNINGMEMBERSDETECTED | Thresholds | | | | CRITICALMEMBERSDETECTED | Thresholds | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{serial} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{serial} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{serial\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{serial\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -373,7 +373,7 @@ yum install centreon-plugin-Network-Watchguard-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -472,7 +472,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -526,12 +526,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------| -| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state} | -| --warning-cluster-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state} | -| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{serial} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{serial} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{serial} | +| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\} | +| --warning-cluster-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\} | +| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{serial\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{serial\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{serial\} | | --warning-* --critical-* | Thresholds. Can be: 'members-detected', 'member-health-hardware', 'member-health-system'. | @@ -678,9 +678,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-zyxel-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-zyxel-snmp.md index 0dfe5a351856..a92f9bdc3766 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-zyxel-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/network-zyxel-snmp.md @@ -293,7 +293,7 @@ yum install centreon-plugin-Network-Zyxel-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -302,8 +302,8 @@ yum install centreon-plugin-Network-Zyxel-Snmp | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | FILTERNAME | Filter vpn name with regexp | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connectstatus} eq "disconnected"'). You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | %{connectstatus} eq "disconnected" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connectstatus\} eq "disconnected"'). You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | %\{connectstatus\} eq "disconnected" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | | | | WARNINGTRAFFICIN | Warning threshold | | | | CRITICALTRAFFICIN | Critical threshold | | | | WARNINGTRAFFICOUT | Warning threshold | | | @@ -398,7 +398,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -497,9 +497,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -540,8 +540,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter vpn name with regexp. | | --warning-* | Warning threshold. Can be: 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: 'traffic-in', 'traffic-out'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connectstatus} eq "disconnected"'). You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connectstatus\} eq "disconnected"'). You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md index 658ab914c00e..e323072a9a3d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md @@ -376,7 +376,7 @@ yum install centreon-plugin-Operatingsystems-Aix-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -470,7 +470,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -658,9 +658,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md index 28c2cb0bd687..32f4e3fced7a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md @@ -279,9 +279,9 @@ yum install centreon-plugin-Operatingsystems-Aix-Local | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERTYPE | Filter filesystem type (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | %{state} =~ /stale/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | %\{state\} =~ /stale/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -291,8 +291,8 @@ yum install centreon-plugin-Operatingsystems-Aix-Local |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERCOMMAND | Filter process commands (regexp can be used) | | | | FILTERPPID | Filter process ppid (regexp can be used) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -337,7 +337,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --warning-usage='' \ --critical-usage='' \ --warning-usage-prct='' \ - --critical-usage-prct='' + --critical-usage-prct='' ``` La commande devrait retourner un message de sortie similaire à : @@ -399,7 +399,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -484,9 +484,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-type | Filter filesystem type (regexp can be used). | | --filter-mount | Filter storage mount point (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /stale/i'). You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /stale/i'). You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | @@ -498,8 +498,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-arg | Filter process arguments (regexp can be used). | | --filter-ppid | Filter process ppid (regexp can be used). | | --filter-state | Filter process states (regexp can be used). You can use: 'Canceled', 'Nonexistent', 'Active', 'Swapped', 'Idle', 'Stopped', 'Running', 'Sleeping'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md index 9d604e3b896e..e0f5da165cc9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md @@ -272,9 +272,9 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | COMMANDNAME | Specify the command to execute (required) | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /failed/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /failed/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -282,10 +282,10 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Valeur par défaut | Obligatoire | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/i | | | DISKNAME | Filter disks by name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitControl)$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitControl)$/i | | | WARNINGUSAGEPRCT | Thresholds | | | | CRITICALUSAGEPRCT | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -296,7 +296,7 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | JOBQUEUES | | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGJOBSACTIVE | Thresholds | | | | CRITICALJOBSACTIVE | Thresholds | | | | WARNINGJOBSHELD | Thresholds | | | @@ -305,8 +305,8 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | CRITICALJOBSSCHEDULED | Thresholds | | | | WARNINGJOBSTOTAL | Thresholds | | | | CRITICALJOBSTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | %{status} =~ /HELD/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | %\{status\} =~ /HELD/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -352,7 +352,7 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| | FILTERNAME | Filter subsystems by name (can be a regexp) | | | | FILTERLIBRARY | Filter subsystems by library (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGACTIVE | Thresholds | | | | CRITICALACTIVE | Thresholds | | | | WARNINGENDING | Thresholds | | | @@ -365,8 +365,8 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | CRITICALRESTRICTED | Thresholds | | | | WARNINGSTARTING | Thresholds | | | | CRITICALSTARTING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | %{status} =~ /ending\|restricted\|starting/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | %\{status\} =~ /ending\|restricted\|starting/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -476,7 +476,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -522,9 +522,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --command-name | Specify the command to execute (required). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{name\} | @@ -533,9 +533,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --disk-name | Check exact disk. | | --filter-disk-name | Filter disks by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i') . You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitContr ol)$/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i') . You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitContr ol)$/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct', 'reserved', 'disks-total', 'disks-active', 'disks-errors', 'disks-gap-repartition'. | @@ -543,9 +543,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /HELD/i'). You can use the following variables: %{status}, %{name}, %{library} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /HELD/i'). You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | --warning-* --critical-* | Thresholds. Can be: 'jobqueues-total', 'jobqueue-jobs-active', 'jobqueue-jobs-scheduled', 'jobqueue-jobs-held'. | @@ -586,9 +586,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:---------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-subsystem-name | Filter subsystems by name (can be a regexp). | | --filter-subsystem-library | Filter subsystems by library (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /ending\|restricted\|starting/i'). You can use the following variables: %{status}, %{name}, %{library} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /ending\|restricted\|starting/i'). You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | --warning-* --critical-* | Thresholds. Can be: 'subsystems-total', 'subsystems-active', 'subsystems-ending', 'subsystems-inactive', 'subsystems-restricted', 'subsystems-starting', 'jobs-active'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md index 1294c4fc01dd..f710749c8f11 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md @@ -451,7 +451,7 @@ yum install centreon-plugin-Operatingsystems-Freebsd-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -562,7 +562,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -793,9 +793,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md index 08f84b9267db..0d93e1fb1da2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md @@ -713,8 +713,8 @@ Ce connecteur de supervision s'appuie sur une intégration prise en charge par C | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --use-new-perfdata --verbose | | @@ -803,8 +803,8 @@ Ce connecteur de supervision s'appuie sur une intégration prise en charge par C |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -946,7 +946,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1187,9 +1187,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1218,9 +1218,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1310,8 +1310,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1334,9 +1334,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md index e2fdcd888c5d..d7baa099e568 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md @@ -848,8 +848,8 @@ yum install nagios-plugins-nrpe | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --use-new-perfdata --verbose | | @@ -938,8 +938,8 @@ yum install nagios-plugins-nrpe |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -1082,7 +1082,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1323,9 +1323,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1354,9 +1354,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1446,8 +1446,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1470,9 +1470,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md index f13305c55aa8..31c0152eeb8c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md @@ -549,7 +549,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -616,7 +616,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -730,7 +730,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -945,9 +945,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -1052,9 +1052,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md index 474507b6f1a2..bc419cccb6e6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md @@ -475,8 +475,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -646,7 +646,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -828,9 +828,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md index 30032c4f9eac..1480f2476e2e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md @@ -610,7 +610,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | FILTERDEVICE | Filter device name (can use regexp) | | | | FILTERMOUNTPOINT | Filter mount point name (can use regexp) | | | | FILTERTYPE | Filter mount point type (can use regexp) | | | -| CRITICALSTATUS | Critical threshold (default: '%{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i') | %{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i | | +| CRITICALSTATUS | Critical threshold (default: '%\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i') | %\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i | | | WARNINGSTATUS | Warning threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -622,13 +622,13 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | NTPMODE | Default mode for parsing and command: 'ntpq' (default), 'chronyc' or 'all' | ntpq | | | FILTERNAME | Filter peer name (can be a regexp) | | | | FILTERSTATE | Filter peer state (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGOFFSET | Warning threshold offset deviation value in milliseconds | | | | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -652,7 +652,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERSTATE | Filter filesystem type (regexp can be used) | | | | FILTERINTERFACE | Filter interface name (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGINDISCARD | Thresholds | | | | CRITICALINDISCARD | Thresholds | | | | WARNINGINERROR | Thresholds | | | @@ -661,8 +661,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | %{status} ne "RU" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | %\{status\} ne "RU" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -768,8 +768,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | %{active} =~ /failed/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | %\{active\} =~ /failed/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -786,13 +786,13 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERINTERFACE | Filter interface name (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGIN | Warning threshold in percent for 'in' traffic | | | | CRITICALIN | Critical threshold in percent for 'in' traffic | | | | WARNINGOUT | Warning threshold in percent for 'out' traffic | | | | CRITICALOUT | Critical threshold in percent for 'out' traffic | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | %{status} ne "RU" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} ne "RU" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -829,7 +829,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-interface='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} ne "RU"' \ + --critical-status='%\{status\} ne "RU"' \ --warning-in='' \ --critical-in='' \ --warning-out='' \ @@ -921,7 +921,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1132,7 +1132,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --exclude-device | Exclude device name (can use regexp). | | --filter-type | Filter mount point type (can use regexp). | | --warning-status | Warning threshold. | -| --critical-status | Critical threshold (default: '%{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i'). | +| --critical-status | Critical threshold (default: '%\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i'). | @@ -1148,9 +1148,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1179,9 +1179,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1316,8 +1316,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1340,9 +1340,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md index eef4f16ac5a6..f30617b9f8a5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md @@ -876,8 +876,8 @@ Ce connecteur de supervision s'appuie sur une intégration prise en charge par C | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --use-new-perfdata --verbose | | @@ -966,8 +966,8 @@ Ce connecteur de supervision s'appuie sur une intégration prise en charge par C |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -1109,7 +1109,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1350,9 +1350,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1381,9 +1381,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1473,8 +1473,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1497,9 +1497,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md index 1dffda41cc4f..414e612062a8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md @@ -450,7 +450,7 @@ yum install centreon-plugin-Operatingsystems-Mac-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -561,7 +561,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -792,9 +792,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md index 43b81d0eff76..cfed7b6ecf67 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md @@ -337,8 +337,8 @@ Ce connecteur de supervision s'appuie sur une intégration prise en charge par C | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | `%{RebootPending} =~ /true/i` | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | `%{RebootPending} =~ /true/i` | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | TIMEOUT | Set timeout time for command execution | 10 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -460,7 +460,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -599,8 +599,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md index 08908c401afc..3b165b5eb327 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md @@ -385,8 +385,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | %{RebootPending} =~ /true/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | %\{RebootPending\} =~ /true/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -593,7 +593,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -639,7 +639,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -665,7 +665,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -691,7 +691,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -717,7 +717,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -743,7 +743,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -769,7 +769,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -795,7 +795,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -821,7 +821,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -848,8 +848,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | @@ -873,7 +873,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -899,7 +899,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -925,7 +925,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -977,7 +977,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -1003,7 +1003,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -1046,7 +1046,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md index 43327498ef54..f7d067b6b44e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md @@ -398,8 +398,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Snmp | CRITICALPAUSED | Thresholds on services count | | | | WARNINGPAUSEPENDING | Thresholds on services count | | | | CRITICALPAUSEPENDING | Thresholds on services count | | | -| WARNINGSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state} | | | -| CRITICALSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state} | | | +| WARNINGSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\} | | | +| CRITICALSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (example: a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -445,7 +445,7 @@ yum install centreon-plugin-Operatingsystems-Windows-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (example: a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -543,7 +543,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -709,7 +709,7 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-----------------------------------|:-------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by service name (can be a regexp). | -| --warning-status --critical-status | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state}. | +| --warning-status --critical-status | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\}. | | --warning-* --critical-* | Thresholds on services count. Can be: 'total', 'active', 'continue-pending', 'pause-pending', 'paused'. | | --warning | DEPRECATED. Use --warning-active instead. | | --critical | DEPRECATED. Use --critical-active instead. | @@ -751,9 +751,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md index 6a4c42ce06b7..ace87ab794a6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md @@ -321,8 +321,8 @@ services se mettront à jour dans les minutes qui suivront. | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | `%{RebootPending} =~ /true/i` | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | `%{RebootPending} =~ /true/i` | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | TIMEOUT | Set timeout time for command execution (default: 50 sec). | 10 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -412,7 +412,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,8 +479,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md index b755332eaed6..a655ce8a82f0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md @@ -381,8 +381,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Wsman | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | %{RebootPending} =~ /true/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | %\{RebootPending\} =~ /true/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -570,7 +570,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -685,8 +685,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md index ddebdf803059..c4f8e9199b6d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md @@ -220,10 +220,10 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNRAIDSTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNPHYSICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNLOGICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNHOSTSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | +| UNKNOWNRAIDSTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNPHYSICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNLOGICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNHOSTSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | | FILTERNAME | Filter hosts by name | | | | WARNINGHOSTCOMPONENTSGREEN | Thresholds | | | | CRITICALHOSTCOMPONENTSGREEN | Thresholds | | | @@ -243,16 +243,16 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | CRITICALHOSTSREMOVED | Thresholds | | | | WARNINGHOSTSSUSPECTED | Thresholds | | | | CRITICALHOSTSSUSPECTED | Thresholds | | | -| WARNINGHOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /suspected/ | | -| CRITICALHOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /faulty/ | | +| WARNINGHOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /suspected/ | | +| CRITICALHOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /faulty/ | | | WARNINGHOSTSUNKNOWN | Thresholds | | | | CRITICALHOSTSUNKNOWN | Thresholds | | | -| WARNINGLOGICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALLOGICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | -| WARNINGPHYSICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALPHYSICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | -| WARNINGRAIDSTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALRAIDSTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | +| WARNINGLOGICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALLOGICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | +| WARNINGPHYSICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALPHYSICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | +| WARNINGRAIDSTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALRAIDSTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -280,10 +280,10 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNHASTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ha\_status}, %{vm\_name} | %{ha\_status} =~ /unknown/ | | +| UNKNOWNHASTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ha_status\}, %\{vm_name\} | %\{ha_status\} =~ /unknown/ | | | FILTERVMNAME | Filter virtual machines by virtual machine name | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{vm\_name} | %{ha\_status} =~ /degraded/ | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status}, %{vm\_name} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{vm_name\} | %\{ha_status\} =~ /degraded/ | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\}, %\{vm_name\} | | | | WARNINGSPACEUSAGE | Thresholds | | | | CRITICALSPACEUSAGE | Thresholds | | | | WARNINGSPACEUSAGEFREE | Thresholds | | | @@ -335,18 +335,18 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --critical-hosts-suspected='' \ --warning-hosts-unknown='' \ --critical-hosts-unknown='' \ - --unknown-raid-status='%{status} =~ /unknown/' \ - --warning-raid-status='%{status} =~ /yellow/' \ - --critical-raid-status='%{status} =~ /red/' \ - --unknown-physical-drive-status='%{status} =~ /unknown/' \ - --warning-physical-drive-status='%{status} =~ /yellow/' \ - --critical-physical-drive-status='%{status} =~ /red/' \ - --unknown-logical-drive-status='%{status} =~ /unknown/' \ - --warning-logical-drive-status='%{status} =~ /yellow/' \ - --critical-logical-drive-status='%{status} =~ /red/' \ - --unknown-host-status='%{status} =~ /unknown/' \ - --warning-host-status='%{status} =~ /suspected/' \ - --critical-host-status='%{status} =~ /faulty/' \ + --unknown-raid-status='%\{status\} =~ /unknown/' \ + --warning-raid-status='%\{status\} =~ /yellow/' \ + --critical-raid-status='%\{status\} =~ /red/' \ + --unknown-physical-drive-status='%\{status\} =~ /unknown/' \ + --warning-physical-drive-status='%\{status\} =~ /yellow/' \ + --critical-physical-drive-status='%\{status\} =~ /red/' \ + --unknown-logical-drive-status='%\{status\} =~ /unknown/' \ + --warning-logical-drive-status='%\{status\} =~ /yellow/' \ + --critical-logical-drive-status='%\{status\} =~ /red/' \ + --unknown-host-status='%\{status\} =~ /unknown/' \ + --warning-host-status='%\{status\} =~ /suspected/' \ + --critical-host-status='%\{status\} =~ /faulty/' \ --verbose ``` @@ -471,7 +471,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -526,18 +526,18 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter hosts by name. | -| --unknown-host-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-host-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /suspected/'). You can use the following variables: %{status}, %{name} | -| --critical-host-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /faulty/'). You can use the following variables: %{status}, %{name} | -| --unknown-raid-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-raid-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-raid-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | -| --unknown-logical-drive-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-logical-drive-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-logical-drive-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | -| --unknown-physical-drive-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-physical-drive-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-physical-drive-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | +| --unknown-host-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-host-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /suspected/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-host-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /faulty/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-raid-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-raid-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-raid-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-logical-drive-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-logical-drive-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-logical-drive-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-physical-drive-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-physical-drive-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-physical-drive-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'hosts-alive', 'hosts-faulty', 'hosts-managed', 'hosts-removed', 'hosts-suspected', 'hosts-unknown', 'host-components-green', 'host-components-yellow', 'host-components-red', 'host-components-unknown'. | @@ -554,9 +554,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-vm-name | Filter virtual machines by virtual machine name. | -| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{ha\_status}, %{vm\_name} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded/'). You can use the following variables: %{ha\_status}, %{vm\_name} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status}, %{vm\_name} | +| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{ha_status\}, %\{vm_name\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded/'). You can use the following variables: %\{ha_status\}, %\{vm_name\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\}, %\{vm_name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md index 91132484c2ef..3d08a31fc4eb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md @@ -261,10 +261,10 @@ yum install centreon-nrpe3-plugin | FILTERSTATUS | Filter virtual machine status (can be a regexp) | Running | | | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | %{integration\_service\_state} =~ /Update required/i | | -| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | not %{primary\_status} =~ /Ok/i | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | | | +| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | %\{integration_service_state\}=~ /Update required/i | | +| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | not %\{primary_status\} =~ /Ok/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -273,8 +273,8 @@ yum install centreon-nrpe3-plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -298,8 +298,8 @@ yum install centreon-nrpe3-plugin |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | not %{status} =~ /Operating normally/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | not %\{status\} =~ /Operating normally/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -311,8 +311,8 @@ yum install centreon-nrpe3-plugin | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{vmaddition}, %{status} | %{vmaddition} =~ /not detected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %{vm}, %{vmaddition}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | %\{vmaddition\} =~ /not detected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -336,8 +336,8 @@ yum install centreon-nrpe3-plugin | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{status}, %{hostgroup} | not %{status} =~ /Running\|Stopped/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %{vm}, %{status}, %{hostgroup} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | not %\{status\} =~ /Running\|Stopped/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -363,7 +363,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-description="" \ --filter-hostgroup="" \ --warning-status="" \ - --critical-status="not %{status} =~ /Running|Stopped/i" \ + --critical-status="not %\{status\} =~ /Running|Stopped/i" \ --verbose' ``` @@ -428,7 +428,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -467,10 +467,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | | --filter-status | Filter virtual machine status (can be a regexp) (default: 'running'). | -| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%{integration\_service\_state} =~ /Update required/i'). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{primary\_status} !~ /Ok/i'). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | +| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%\{integration_service_state\}=~ /Update required/i'). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{primary_status\} !~ /Ok/i'). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | @@ -485,8 +485,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /Warning/i'). You can use the following variables: %{vm}, %{state}, %{health} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /Critical/i'). You can use the following variables: %{vm}, %{state}, %{health} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /Warning/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /Critical/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | @@ -520,8 +520,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Operating normally/i'). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Operating normally/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | @@ -543,8 +543,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-description | Filter by description (can be a regexp). | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{vmaddition}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{vmaddition} =~ /not detected/i'). You can use the following variables: %{vm}, %{vmaddition}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vmaddition\} =~ /not detected/i'). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | @@ -588,8 +588,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | | --filter-description | Filter by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{status}, %{hostgroup} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Running\|Stopped/i'). You can use the following variables: %{vm}, %{status}, %{hostgroup} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Running\|Stopped/i'). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md index e07e500b0aec..9da27bb8ba08 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md @@ -291,10 +291,10 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | | FILTERSTATUS | Filter virtual machine status (can be a regexp) | Running | | -| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | %{integration\_service\_state} =~ /Update required/i | | -| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | not %{primary\_status} =~ /Ok/i | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | | | +| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | %\{integration_service_state\}=~ /Update required/i | | +| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | not %\{primary_status\} =~ /Ok/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -303,8 +303,8 @@ yum install | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -328,8 +328,8 @@ yum install |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | not %{status} =~ /Operating normally/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | not %\{status\} =~ /Operating normally/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -341,8 +341,8 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{vmaddition}, %{status} | %{vmaddition} =~ /not detected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{vmaddition}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | %\{vmaddition\} =~ /not detected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -366,8 +366,8 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{status}, %{hostgroup} | not %{status} =~ /Running\|Stopped/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{status}, %{hostgroup} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | not %\{status\} =~ /Running\|Stopped/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -406,7 +406,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --filter-description="" \ --filter-hostgroup="" \ --warning-status="" \ - --critical-status="not %{status} =~ /Running|Stopped/i" \ + --critical-status="not %\{status\} =~ /Running|Stopped/i" \ --verbose' ``` @@ -471,7 +471,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -510,10 +510,10 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | | --filter-status | Filter virtual machine status (can be a regexp) (default: 'running'). | -| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%{integration\_service\_state} =~ /Update required/i'). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{primary\_status} !~ /Ok/i'). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | +| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%\{integration_service_state\}=~ /Update required/i'). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{primary_status\} !~ /Ok/i'). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | @@ -528,8 +528,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /Warning/i'). You can use the following variables: %{vm}, %{state}, %{health} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /Critical/i'). You can use the following variables: %{vm}, %{state}, %{health} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /Warning/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /Critical/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | @@ -563,8 +563,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Operating normally/i'). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Operating normally/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | @@ -586,8 +586,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-description | Filter by description (can be a regexp). | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{vmaddition}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{vmaddition} =~ /not detected/i'). You can use the following variables: %{vm}, %{vmaddition}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vmaddition\} =~ /not detected/i'). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | @@ -631,8 +631,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | | --filter-description | Filter by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{status}, %{hostgroup} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Running\|Stopped/i'). You can use the following variables: %{vm}, %{status}, %{hostgroup} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Running\|Stopped/i'). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md index af721eb534f1..123106e58505 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md @@ -551,12 +551,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGREAD | Warning threshold | | | | CRITICALREAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGTOTALREAD | Warning threshold | | | | CRITICALTOTALREAD | Critical threshold | | | | WARNINGTOTALWRITE | Warning threshold | | | @@ -570,7 +570,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | @@ -578,8 +578,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALREADTOTAL | Thresholds | | | | WARNINGREADVM | Thresholds | | | | CRITICALREADVM | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | WARNINGWRITETOTAL | Thresholds | | | @@ -593,12 +593,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGSNAPSHOT | Warning threshold | | | | CRITICALSNAPSHOT | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -608,13 +608,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | UNIT | | % | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | | CRITICALPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 80 | | | CRITICALUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 90 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -624,14 +624,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -648,8 +648,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERTIME | The connector will ignore any alert older than the time period specified here (in seconds). | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -661,13 +661,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTOTALCPUMHZ | Warning threshold | | | | CRITICALTOTALCPUMHZ | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -678,11 +678,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGWRITELATENCY | Warning threshold | | | | CRITICALWRITELATENCY | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -692,15 +692,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGPROBLEMS | Thresholds | | | | CRITICALPROBLEMS | Thresholds | | | | WARNINGPROBLEMSRED | Thresholds | | | | CRITICALPROBLEMSRED | Thresholds | | | | WARNINGPROBLEMSYELLOW | Thresholds | | | | CRITICALPROBLEMSYELLOW | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTOTALPROBLEMS | Thresholds | | | | CRITICALTOTALPROBLEMS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -710,15 +710,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNING | Warning threshold (can use unit option) | | | | CRITICAL | Critical threshold (can use unit option) | | | | WARNINGOVERHEADMEMORY | Overhead threshold | | | | CRITICALOVERHEADMEMORY | Critical threshold | | | | WARNINGSTATEMEMORY | Warning threshold. For state != 'high': --warning-state=0 | | | | CRITICALSTATEMEMORY | Critical threshold. For state != 'high': --warning-state=0 | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -726,12 +726,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i && %{maintenance} =~ /false/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i | | | FILTERSERVICES | Filter services you want to check (can be a regexp) | ^(?!(snmpd\|xorg)$) | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | %{policy} =~ /^on\|automatic/i && !%{running} | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | %\{policy\} =~ /^on\|automatic/i && !%\{running\} | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -739,12 +739,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -752,7 +752,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | %{status} !~ /^connected$/i && %{maintenance} =~ /false/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | %\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i | | | FILTERADAPTERNAME | Filter adapters by name (can be a regexp) | | | | FILTERLUNNAME | Filter luns by name (can be a regexp) | | | | FILTERPATHNAME | Filter paths by name (can be a regexp) | | | @@ -762,8 +762,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALADAPTERSOFFLINE | Thresholds | | | | WARNINGADAPTERSONLINE | Thresholds | | | | CRITICALADAPTERSONLINE | Thresholds | | | -| CRITICALADAPTERSTATUS | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /fault/ | | -| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALADAPTERSTATUS | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /fault/ | | +| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGADAPTERSTOTAL | Thresholds | | | | CRITICALADAPTERSTOTAL | Thresholds | | | | WARNINGADAPTERSUNKNOWN | Thresholds | | | @@ -778,8 +778,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALLUNSOK | Threshold | | | | WARNINGLUNSQUIESCED | Threshold | | | | CRITICALLUNSQUIESCED | Threshold | | | -| WARNINGLUNSTATUS | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /degraded\|quiesced/ | | -| CRITICALLUNSTATUS | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /lostcommunication\|error/ | | +| WARNINGLUNSTATUS | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /degraded\|quiesced/ | | +| CRITICALLUNSTATUS | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /lostcommunication\|error/ | | | WARNINGLUNSTOTAL | Threshold | | | | CRITICALLUNSTOTAL | Threshold | | | | WARNINGLUNSUNKNOWN | Threshold | | | @@ -792,14 +792,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALPATHSDISABLED | Threshold | | | | WARNINGPATHSSTANDBY | Threshold | | | | CRITICALPATHSSTANDBY | Threshold | | | -| CRITICALPATHSTATUS | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /dead/ | | -| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALPATHSTATUS | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /dead/ | | +| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGPATHSTOTAL | Threshold | | | | CRITICALPATHSTOTAL | Threshold | | | | WARNINGPATHSUNKNOWN | Threshold | | | | CRITICALPATHSUNKNOWN | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -807,9 +807,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -821,9 +821,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | -2:2 | | | CRITICALTIME | Critical threshold in seconds | -5:5 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -834,8 +834,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERNICNAME | ESX nic to check. If not set, we check all nics | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGDROPPEDIN | Thresholds | | | | CRITICALDROPPEDIN | Thresholds | | | | WARNINGDROPPEDOUT | Thresholds | | | @@ -846,12 +846,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALHOSTTRAFFICOUT | Thresholds | | | | WARNINGIN | Thresholds | 80 | | | CRITICALIN | Thresholds | 90 | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | %{link\_status} !~ /up/ | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} !~ /up/ | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -859,9 +859,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | | | | CRITICALTIME | Critical threshold in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -871,13 +871,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -893,11 +893,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | %{maintenance} !~ /false/ | | -| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | %\{maintenance\} !~ /false/ | | +| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -922,7 +922,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --connector-port='5700' \ --container='default' \ --esx-hostname='' \ - --unknown-status='%{status} !~ /^connected$/i' \ + --unknown-status='%\{status\} !~ /^connected$/i' \ --warning-status='' \ --critical-status='' \ --warning-total-on='' \ @@ -1034,7 +1034,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1063,9 +1063,9 @@ Les options génériques sont listées ci-dessous : | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different than 300 or 20. | | --time-shift | Can shift the time. We the following option you can average X counters values (default: 0). | | --case-insensitive | Searchs are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Options des modes @@ -1079,9 +1079,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | | --critical-* | Critical threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | @@ -1094,9 +1094,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --detail-iops-min | Only display VMs with iops higher value (default: 50). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: 'read-total', 'write-total', 'read', 'write', 'read-vm', 'write-vm'. | @@ -1107,9 +1107,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total', 'snapshot'. | | --critical-* | Critical threshold. Can be: 'total', 'snapshot'. | @@ -1123,9 +1123,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --filter-host | Filter datastores attached to hosts (can be a regexp). | | --refresh | Explicitly ask vmware to refreshes free-space and capacity values (slower). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned'. | @@ -1136,9 +1136,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1165,8 +1165,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-time | The connector will ignore any alert older than the time period specified here (in seconds). | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1179,9 +1179,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | @@ -1196,9 +1196,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'read-latency', 'write-latency'. | | --critical-* | Critical threshold. Can be: 'read-latency', 'write-latency'. | @@ -1212,9 +1212,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --storage-status | Check storage(s) status. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-problems', 'problems', 'problems-yellow', 'problems-red', 'sensor-temperature', 'sensor-fan', 'sensor-voltage', 'sensor-power'. | @@ -1228,9 +1228,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-consumed-memory | Warning threshold (can use unit option). | | --critical-consumed-memory | Critical threshold (can use unit option). | | --warning-overhead-memory | Overhead threshold. | @@ -1249,11 +1249,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-services | Filter services you want to check (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | @@ -1264,12 +1264,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -1283,15 +1283,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-adapter-name | Filter adapters by name (can be a regexp). | | --filter-lun-name | Filter luns by name (can be a regexp). | | --filter-path-name | Filter paths by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | -| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-adapter-status | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-lun-status | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | -| --critical-lun-status | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-path-status | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-path-status | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-adapter-status | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-lun-status | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-lun-status | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-path-status | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-path-status | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'adapters-total', 'adapters-online', 'adapters-offline', 'adapters-fault', 'adapters-unknown', | @@ -1303,9 +1303,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | @@ -1318,9 +1318,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1335,12 +1335,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --nic-name | ESX nic to check. If not set, we check all nics. | | --filter-vswitch-name | Filter vswitch by name. It monitors only ESX nic that belongs to the filtered vswitches. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'host-traffic-in' (b/s), 'host-traffic-out' (b/s), 'vswitch-traffic-in' (b/s), 'vswitch-traffic-out' (b/s), 'link-traffic-in' (%), 'link-traffic-out' (%), 'link-dropped-in', 'link-dropped-out'. | | --no-proxyswitch | Use the following option if you are checking an ESX 3.x version (it's mandatory). | @@ -1353,9 +1353,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1368,9 +1368,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1383,11 +1383,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | -| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | +| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md index c9313106ab3e..54e0bb13ca79 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md @@ -791,9 +791,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -802,9 +802,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------|:-----------:| | FILTERNAME | Cluster to check. If not set, we check all clusters | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -813,8 +813,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERTIME | Do not check alarms older than specified time (value in seconds) | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -828,8 +828,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Datacenter to check. If not set, we check all datacenters | .* | | | FILTERTIME | Do not check alarms older than specified time (value in seconds) | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -842,11 +842,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGREAD | Warning threshold | | | | CRITICALREAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGTOTALREAD | Warning threshold | | | | CRITICALTOTALREAD | Critical threshold | | | | WARNINGTOTALWRITE | Warning threshold | | | @@ -861,15 +861,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADTOTAL | Thresholds | | | | CRITICALREADTOTAL | Thresholds | | | | WARNINGREADVM | Thresholds | | | | CRITICALREADVM | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | WARNINGWRITETOTAL | Thresholds | | | @@ -884,11 +884,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGSNAPSHOT | Warning threshold | | | | CRITICALSNAPSHOT | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -900,11 +900,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | | UNIT | Set this option to '%' if you want the thresholds to be interpreted as a percentage of the maximum possible value instead of as an absolute threshold. | % | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | | CRITICALPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 80 | | | CRITICALUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 90 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -915,13 +915,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -939,8 +939,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERTIME | The connector will ignore any alert older than the time period specified here (in seconds). | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -953,13 +953,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTOTALCPUMHZ | Warning threshold | | | | CRITICALTOTALCPUMHZ | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -971,11 +971,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERESXNAME | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGWRITELATENCY | Warning threshold | | | | CRITICALWRITELATENCY | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -986,15 +986,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGPROBLEMS | Thresholds | | | | CRITICALPROBLEMS | Thresholds | | | | WARNINGPROBLEMSRED | Thresholds | | | | CRITICALPROBLEMSRED | Thresholds | | | | WARNINGPROBLEMSYELLOW | Thresholds | | | | CRITICALPROBLEMSYELLOW | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTOTALPROBLEMS | Thresholds | | | | CRITICALTOTALPROBLEMS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1005,15 +1005,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNING | Warning threshold (can use unit option) | | | | CRITICAL | Critical threshold (can use unit option) | | | | WARNINGOVERHEADMEMORY | Overhead threshold | | | | CRITICALOVERHEADMEMORY | Critical threshold | | | | WARNINGSTATEMEMORY | Warning threshold. For state != 'high': --warning-state=0 | | | | CRITICALSTATEMEMORY | Critical threshold. For state != 'high': --warning-state=0 | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1023,11 +1023,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERSERVICES | Filter services you want to check (can be a regexp) | ^(?!(snmpd\|xorg)$) | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\ |automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | %{policy} =~ /^on\|automatic/i && !%{running} | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running}, %{label}, %{policy} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\ |automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | %\{policy\} =~ /^on\|automatic/i && !%\{running\} | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1036,12 +1036,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1053,15 +1053,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTERADAPTERNAME | Filter adapters by name (can be a regexp) | | | | FILTERLUNNAME | Filter luns by name (can be a regexp) | | | | FILTERPATHNAME | Filter paths by name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | | | | WARNINGADAPTERSFAULT | Thresholds | | | | CRITICALADAPTERSFAULT | Thresholds | | | | WARNINGADAPTERSOFFLINE | Thresholds | | | | CRITICALADAPTERSOFFLINE | Thresholds | | | | WARNINGADAPTERSONLINE | Thresholds | | | | CRITICALADAPTERSONLINE | Thresholds | | | -| CRITICALADAPTERSTATUS | Set critical threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /fault/ | | -| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALADAPTERSTATUS | Set critical threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /fault/ | | +| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGADAPTERSTOTAL | Thresholds | | | | CRITICALADAPTERSTOTAL | Thresholds | | | | WARNINGADAPTERSUNKNOWN | Thresholds | | | @@ -1076,8 +1076,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALLUNSOK | Set critical threshold for the count of LUNs that are operational. | | | | WARNINGLUNSQUIESCED | Set warning threshold for the count of LUNs that are in a quiesced state. | | | | CRITICALLUNSQUIESCED | Set critical threshold for the count of LUNs that are in a quiesced state. | | | -| WARNINGLUNSTATUS | Set warning threshold for lun status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /degraded\|quiesced/ | | -| CRITICALLUNSTATUS | Set critical threshold for lun status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /lostcommunication\|error/ | | +| WARNINGLUNSTATUS | Set warning threshold for lun status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /degraded\|quiesced/ | | +| CRITICALLUNSTATUS | Set critical threshold for lun status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /lostcommunication\|error/ | | | WARNINGLUNSTOTAL | Set warning threshold for the total count of LUNs. | | | | CRITICALLUNSTOTAL | Set critical threshold for the total count of LUNs. | | | | WARNINGLUNSUNKNOWN | Set warning threshold for the count of LUNs with an unknown status. | | | @@ -1090,14 +1090,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALPATHSDISABLED | Set critical threshold for the count of disabled storage paths. | | | | WARNINGPATHSSTANDBY | Set warning threshold for the count of storage paths in standby mode. | | | | CRITICALPATHSSTANDBY | Set critical threshold for the count of storage paths in standby mode. | | | -| CRITICALPATHSTATUS | Set critical threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /dead/ | | -| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALPATHSTATUS | Set critical threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /dead/ | | +| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGPATHSTOTAL | Set warning threshold for the total count of storage paths. | | | | CRITICALPATHSTOTAL | Set critical threshold for the total count of storage paths. | | | | WARNINGPATHSUNKNOWN | Set warning threshold for the count of storage paths with an unknown status. | | | | CRITICALPATHSUNKNOWN | Set critical threshold for the count of storage paths with an unknown status. | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1106,9 +1106,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -1121,9 +1121,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | -2:2 | | | CRITICALTIME | Critical threshold in seconds | -5:5 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1135,8 +1135,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERESXNAME | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERNICNAME | ESX nic to check. If not set, we check all nics | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGDROPPEDIN | Thresholds | | | | CRITICALDROPPEDIN | Thresholds | | | | WARNINGDROPPEDOUT | Thresholds | | | @@ -1147,12 +1147,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALHOSTTRAFFICOUT | Thresholds | | | | WARNINGIN | Thresholds | 80 | | | CRITICALIN | Thresholds | 90 | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1161,9 +1161,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | | | | CRITICALTIME | Critical threshold in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1174,13 +1174,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -1197,11 +1197,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:--------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{maintenance} | %{maintenance} !~ /false/ | | -| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{maintenance} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{maintenance\} | %\{maintenance\} !~ /false/ | | +| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{maintenance\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1231,13 +1231,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGREADY | Warning threshold | 5 | | | CRITICALREADY | Critical threshold | 10 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGUSAGE | Warning threshold | 80 | | | CRITICALUSAGE | Critical threshold | 90 | | | WARNINGUSAGEMHZ | Warning threshold | | | @@ -1252,13 +1252,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGMAXTOTALLATENCY | Thresholds | | | | CRITICALMAXTOTALLATENCY | Thresholds | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1271,9 +1271,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | | FILTERDEVICE | Device to check (Required) (Example: --device='VirtualCdrom') | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | | CRITICALTOTALDEVICECONNECTED | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1285,12 +1285,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | +| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1300,7 +1300,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGACTIVE | Warning threshold | | | @@ -1311,8 +1311,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALOVERHEAD | Critical threshold | | | | WARNINGSHARED | Warning threshold | | | | CRITICALSHARED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1332,13 +1332,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -1348,9 +1348,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -1597,7 +1597,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1626,9 +1626,9 @@ Les options génériques sont listées ci-dessous : | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different than 300 or 20. | | --time-shift | Can shift the time. We the following option you can average X counters values (default: 0). | | --case-insensitive | Searchs are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Options des modes @@ -1662,9 +1662,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --cluster-name | cluster to check. If not set, we check all clusters. | | --filter | Cluster name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | @@ -1674,9 +1674,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --cluster-name | cluster to check. If not set, we check all clusters. | | --filter | Cluster name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | @@ -1701,8 +1701,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-time | Do not check alarms older than specified time (value in seconds). | | --filter-type | Check only alarms for specified type(s). Can be a regex. Can be for example: --filter-type='VirtualMachine' will only show alarms for VirtualMachines. | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1729,8 +1729,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-time | Do not check alarms older than specified time (value in seconds). | | --filter-type | Check only alarms for specified type(s). Can be a regex. Can be for example: --filter-type='VirtualMachine' will only show alarms for VirtualMachines. | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1742,9 +1742,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | | --critical-* | Critical threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | @@ -1757,9 +1757,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --detail-iops-min | Only display VMs with iops higher value (default: 50). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: 'read-total', 'write-total', 'read', 'write', 'read-vm', 'write-vm'. | @@ -1770,9 +1770,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total', 'snapshot'. | | --critical-* | Critical threshold. Can be: 'total', 'snapshot'. | @@ -1786,9 +1786,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --filter-host | Filter datastores attached to hosts (can be a regexp). | | --refresh | Explicitly ask vmware to refreshes free-space and capacity values (slower). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned'. | @@ -1799,9 +1799,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1828,8 +1828,8 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-time | The connector will ignore any alert older than the time period specified here (in seconds). | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1842,9 +1842,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | @@ -1859,9 +1859,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'read-latency', 'write-latency'. | | --critical-* | Critical threshold. Can be: 'read-latency', 'write-latency'. | @@ -1875,9 +1875,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --storage-status | Check storage(s) status. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-problems', 'problems', 'problems-yellow', 'problems-red', 'sensor-temperature', 'sensor-fan', 'sensor-voltage', 'sensor-power'. | @@ -1891,9 +1891,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-consumed-memory | Warning threshold (can use unit option). | | --critical-consumed-memory | Critical threshold (can use unit option). | | --warning-overhead-memory | Overhead threshold. | @@ -1912,11 +1912,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-services | Filter services you want to check (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | @@ -1927,12 +1927,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -1946,15 +1946,15 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-adapter-name | Filter adapters by name (can be a regexp). | | --filter-lun-name | Filter luns by name (can be a regexp). | | --filter-path-name | Filter paths by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | -| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-adapter-status | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-lun-status | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | -| --critical-lun-status | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-path-status | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-path-status | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-adapter-status | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-lun-status | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-lun-status | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-path-status | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-path-status | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'adapters-total', 'adapters-online', 'adapters-offline', 'adapters-fault', 'adapters-unknown', | @@ -1966,9 +1966,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | @@ -1981,9 +1981,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1998,12 +1998,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --nic-name | ESX nic to check. If not set, we check all nics. | | --filter-vswitch-name | Filter vswitch by name. It monitors only ESX nic that belongs to the filtered vswitches. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'host-traffic-in' (b/s), 'host-traffic-out' (b/s), 'vswitch-traffic-in' (b/s), 'vswitch-traffic-out' (b/s), 'link-traffic-in' (%), 'link-traffic-out' (%), 'link-dropped-in', 'link-dropped-out'. | | --no-proxyswitch | Use the following option if you are checking an ESX 3.x version (it's mandatory). | @@ -2016,9 +2016,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -2031,9 +2031,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -2046,11 +2046,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | -| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | +| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | @@ -2076,9 +2076,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | @@ -2097,9 +2097,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | @@ -2116,9 +2116,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | | --device | Device to check (Required) (Example: --device='VirtualCdrom'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | | --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | @@ -2133,12 +2133,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-os | Filter also virtual machines OS name (can be a regexp). | | --display-description | Display virtual machine description. | | --check-disk-limit | Check disk limits (since vsphere 5.0). | -| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | @@ -2153,9 +2153,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | | --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | @@ -2194,12 +2194,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | -| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -2214,9 +2214,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index ca53f179ba36..f6457c47782d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -395,13 +395,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGREADY | Warning threshold | 5 | | | CRITICALREADY | Critical threshold | 10 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGUSAGE | Warning threshold | 80 | | | CRITICALUSAGE | Critical threshold | 90 | | | WARNINGUSAGEMHZ | Warning threshold | | | @@ -414,13 +414,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores. | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNINGMAXTOTALLATENCY | Thresholds | | | | CRITICALMAXTOTALLATENCY | Thresholds | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -430,10 +430,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | %{connection\_state} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | %\{connection_state\} !~ /^connected$/i | | | FILTERDEVICE | Device to check (required). (Example: --device='VirtualCdrom') | | X | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | | CRITICALTOTALDEVICECONNECTED | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -443,12 +443,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| -| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | +| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -456,7 +456,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGACTIVE | Warning threshold | | | @@ -467,8 +467,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALOVERHEAD | Critical threshold | | | | WARNINGSHARED | Warning threshold | | | | CRITICALSHARED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -485,12 +485,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | --verbose | | @@ -498,9 +498,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -548,7 +548,7 @@ telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : --container='default' \ --vm-hostname='' \ --filter-uuid='' \ - --unknown-status='%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i' \ + --unknown-status='%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i' \ --warning-status='' \ --critical-status='' \ --warning-swap-in='' \ @@ -652,7 +652,7 @@ Les options génériques sont listées ci-dessous : | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -681,9 +681,9 @@ Les options génériques sont listées ci-dessous : | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different from 300 or 20. | | --time-shift | Can shift the time. With the following option you can average X counter values (default: 0). | | --case-insensitive | Searches are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Options des modes @@ -701,9 +701,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in the following datacenter(s) (can be a regexp). | | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | @@ -722,9 +722,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Define which VMs should be monitored based on the datastores names. This option will be treated as a regular expression. | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | @@ -741,9 +741,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | | --device | Device to check (Required) (Example: --device='VirtualCdrom'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | | --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | @@ -758,12 +758,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --display-description | Display the description of the virtual machine. | | --check-disk-limit | Check disk limits (since vsphere 5.0). | -| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | @@ -778,9 +778,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | | --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | @@ -819,12 +819,12 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-datacenter | Search in the following datacenter(s) (can be a regexp). | | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | -| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -839,9 +839,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

+ +

Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

  • Ajouté : Indique que l'objet a été ajouté
  • Modifié : Indique que l'objet a été modifié
    • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

    La dernière colonne décrit la modification en elle-même :

    + +

    La dernière colonne décrit la modification en elle-même :

    • Nom du champ : Décrit le champ du formulaire modifié
    • Avant : Indique l'ancienne valeur
      • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/parameters/ldap.md index 95bce4b4eb9b..a55bb27752a3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/parameters/ldap.md @@ -106,9 +106,9 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** Sous CentOS 7, on peut définir de ne pas vérifier le certificat serveur avec la procédure suivante: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/secure-platform.md index 733a0a2ea3e3..39bca576803c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/administration/secure-platform.md @@ -679,17 +679,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1205,7 +1205,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/notif-config-for-teams.md index dda9e6edbfad..375924a4a128 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/resources-status.md index 5a6cc3849812..21fe99ac0f63 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/resources-status.md @@ -306,7 +306,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/ticketing.md index f40063645a43..e2189dc74110 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/alerts-notifications/ticketing.md @@ -147,9 +147,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/clapi.md index d911d420a037..215fac190475 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/clapi.md @@ -992,23 +992,35 @@ ipv4: -

      buffering_timeout

      -

      Buffering timeout

      -

      Time in seconds to wait before launching failover.

      + +

      buffering_timeout

      + + +

      Buffering timeout

      + + +

      Time in seconds to wait before launching failover.

      +
      -

      compression

      + +

      compression

      compression_buffer

      -

      compression_level

      -

      Compression (zlib)

      +

      compression_level

      + + +

      Compression (zlib)

      Compression buffer size

      -

      Compression level

      -

      Enable or not data stream compression.

      +

      Compression level

      + + +

      Enable or not data stream compression.

      The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

      -

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +
      • @@ -1016,71 +1028,121 @@ ipv4:
      -

      retry_interval

      -

      Retry interval

      -

      Time in seconds to wait between each connection attempt.

      + +

      retry_interval

      + + +

      Retry interval

      + + +

      Time in seconds to wait between each connection attempt.

      +
      -

      category

      -

      Filter category

      -

      Category filter for flux in input

      + +

      category

      + + +

      Filter category

      + + +

      Category filter for flux in input

      +
      -

      ca_certificate

      -

      host

      -

      Trusted CA's certificate

      -

      Host to connect to

      -

      Trusted CA's certificate.

      -

      IP address or hostname of the host to connect to (leave blank for listening mode).

      + +

      ca_certificate

      +

      host

      + + +

      Trusted CA's certificate

      +

      Host to connect to

      + + +

      Trusted CA's certificate.

      +

      IP address or hostname of the host to connect to (leave blank for listening mode).

      +
      -

      one_peer_retention_mode

      -

      port

      -

      One peer retention

      -

      Connection port

      -

      This allows the retention to work even if the socket is listening

      -

      Port to listen on (empty host) or to connect to (with host filled).

      + +

      one_peer_retention_mode

      +

      port

      + + +

      One peer retention

      +

      Connection port

      + + +

      This allows the retention to work even if the socket is listening

      +

      Port to listen on (empty host) or to connect to (with host filled).

      +
      -

      private_key

      -

      Private key file.

      -

      Private key file path when TLS encryption is used.

      + +

      private_key

      + + +

      Private key file.

      + + +

      Private key file path when TLS encryption is used.

      +
      -

      protocol

      -

      Serialization protocol

      -

      Serialization protocol.

      -

      ndo

      + +

      protocol

      + + +

      Serialization protocol

      + + +

      Serialization protocol.

      + + +

      ndo

      + -

      public_cert

      -

      Public certificate

      -

      Public certificate file path when TLS encryption is used.

      + +

      public_cert

      + + +

      Public certificate

      + + +

      Public certificate file path when TLS encryption is used.

      +
      -

      tls

      -

      Enable TLS encryption

      -

      Enable TLS encryption.

      + +

      tls

      + + +

      Enable TLS encryption

      + + +

      Enable TLS encryption.

      +
      @@ -1101,23 +1163,35 @@ ipv6: -

      buffering_timeout

      -

      Buffering timeout

      -

      Time in seconds to wait before launching failover.

      + +

      buffering_timeout

      + + +

      Buffering timeout

      + + +

      Time in seconds to wait before launching failover.

      +
      -

      compression

      + +

      compression

      compression_buffer

      -

      compression_level

      -

      Compression (zlib)

      +

      compression_level

      + + +

      Compression (zlib)

      Compression buffer size

      -

      Compression level

      -

      Enable or not data stream compression.

      +

      Compression level

      + + +

      Enable or not data stream compression.

      The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

      -

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +
      • @@ -1125,71 +1199,121 @@ ipv6:
      -

      retry_interval

      -

      Retry interval

      -

      Time in seconds to wait between each connection attempt.

      + +

      retry_interval

      + + +

      Retry interval

      + + +

      Time in seconds to wait between each connection attempt.

      +
      -

      category

      -

      Filter category

      -

      Category filter for flux in input

      + +

      category

      + + +

      Filter category

      + + +

      Category filter for flux in input

      +
      -

      ca_certificate

      -

      host

      -

      Trusted CA's certificate

      -

      Host to connect to

      -

      Trusted CA's certificate.

      -

      IP address or hostname of the host to connect to (leave blank for listening mode).

      + +

      ca_certificate

      +

      host

      + + +

      Trusted CA's certificate

      +

      Host to connect to

      + + +

      Trusted CA's certificate.

      +

      IP address or hostname of the host to connect to (leave blank for listening mode).

      +
      -

      one_peer_retention_mode

      -

      port

      -

      One peer retention

      -

      Connection port

      -

      This allows the retention to work even if the socket is listening

      -

      Port to listen on (empty host) or to connect to (with host filled).

      + +

      one_peer_retention_mode

      +

      port

      + + +

      One peer retention

      +

      Connection port

      + + +

      This allows the retention to work even if the socket is listening

      +

      Port to listen on (empty host) or to connect to (with host filled).

      +
      -

      private_key

      -

      Private key file.

      -

      Private key file path when TLS encryption is used.

      + +

      private_key

      + + +

      Private key file.

      + + +

      Private key file path when TLS encryption is used.

      +
      -

      protocol

      -

      Serialization protocol

      -

      Serialization protocol.

      -

      ndo

      + +

      protocol

      + + +

      Serialization protocol

      + + +

      Serialization protocol.

      + + +

      ndo

      + -

      public_cert

      -

      Public certificate

      -

      Public certificate file path when TLS encryption is used.

      + +

      public_cert

      + + +

      Public certificate

      + + +

      Public certificate file path when TLS encryption is used.

      +
      -

      tls

      -

      Enable TLS encryption

      -

      Enable TLS encryption.

      + +

      tls

      + + +

      Enable TLS encryption

      + + +

      Enable TLS encryption.

      +
      @@ -1210,23 +1334,35 @@ file: -

      buffering_timeout

      -

      Buffering timeout

      -

      Time in seconds to wait before launching failover.

      + +

      buffering_timeout

      + + +

      Buffering timeout

      + + +

      Time in seconds to wait before launching failover.

      +
      -

      compression

      + +

      compression

      compression_buffer

      -

      compression_level

      -

      Compression (zlib)

      +

      compression_level

      + + +

      Compression (zlib)

      Compression buffer size

      -

      Compression level

      -

      Enable or not data stream compression.

      +

      Compression level

      + + +

      Enable or not data stream compression.

      The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

      -

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +

      Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

      +
      • @@ -1234,34 +1370,60 @@ file:
      -

      retry_interval

      -

      Retry interval

      -

      Time in seconds to wait between each connection attempt.

      + +

      retry_interval

      + + +

      Retry interval

      + + +

      Time in seconds to wait between each connection attempt.

      +
      -

      max_size

      -

      Maximum size of file

      -

      Maximum size in bytes.

      + +

      max_size

      + + +

      Maximum size of file

      + + +

      Maximum size in bytes.

      +
      -

      path

      -

      File path

      -

      Path to the file.

      + +

      path

      + + +

      File path

      + + +

      Path to the file.

      +
      -

      protocol

      -

      Serialization protocol

      -

      Serialization protocol.

      -

      ndo

      + +

      protocol

      + + +

      Serialization protocol

      + + +

      Serialization protocol.

      + + +

      ndo

      + @@ -1281,50 +1443,88 @@ file: -

      config

      -

      Configuration messages

      -

      Enable or not configuration messages logging.

      + +

      config

      + + +

      Configuration messages

      + + +

      Enable or not configuration messages logging.

      +
      -

      debug

      -

      Debug messages

      -

      Enable or not debug messages logging.

      + +

      debug

      + + +

      Debug messages

      + + +

      Enable or not debug messages logging.

      +
      -

      error

      -

      Error messages

      -

      Enable or not error messages logging.

      + +

      error

      + + +

      Error messages

      + + +

      Enable or not error messages logging.

      +
      -

      info

      -

      Informational messages

      -

      Enable or not informational messages logging.

      + +

      info

      + + +

      Informational messages

      + + +

      Enable or not informational messages logging.

      +
      -

      level

      -

      Logging level

      -

      How much messages must be logged.

      -

      high,low,medium

      + +

      level

      + + +

      Logging level

      + + +

      How much messages must be logged.

      + + +

      high,low,medium

      + -

      max_size

      -

      name

      -

      Max file size in bytes

      -

      Name of the logger

      -

      The maximum size of log file.

      -

      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

      + +

      max_size

      +

      name

      + + +

      Max file size in bytes

      +

      Name of the logger

      + + +

      The maximum size of log file.

      +

      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

      +
      • @@ -1346,45 +1546,76 @@ standard: -

        config

        -

        Configuration messages

        -

        Enable or not configuration messages logging.

        + +

        config

        + + +

        Configuration messages

        + + +

        Enable or not configuration messages logging.

        +
        -

        debug

        -

        Debug messages

        -

        Enable or not debug messages logging.

        + +

        debug

        + + +

        Debug messages

        + + +

        Enable or not debug messages logging.

        +
        -

        error

        -

        Error messages

        -

        Enable or not error messages logging.

        + +

        error

        + + +

        Error messages

        + + +

        Enable or not error messages logging.

        +
        -

        info

        -

        Informational messages

        -

        Enable or not informational messages logging.

        + +

        info

        + + +

        Informational messages

        + + +

        Enable or not informational messages logging.

        +
        -

        level

        -

        name

        -

        Logging level

        -

        Name of the logger

        -

        How much messages must be logged.

        -

        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

        -

        high,low,medium

        + +

        level

        +

        name

        + + +

        Logging level

        +

        Name of the logger

        + + +

        How much messages must be logged.

        +

        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

        + + +

        high,low,medium

        @@ -1405,42 +1636,74 @@ syslog: -

        config

        -

        Configuration messages

        -

        Enable or not configuration messages logging.

        + +

        config

        + + +

        Configuration messages

        + + +

        Enable or not configuration messages logging.

        +
        -

        debug

        -

        Debug messages

        -

        Enable or not debug messages logging.

        + +

        debug

        + + +

        Debug messages

        + + +

        Enable or not debug messages logging.

        +
        -

        error

        -

        Error messages

        -

        Enable or not error messages logging.

        + +

        error

        + + +

        Error messages

        + + +

        Enable or not error messages logging.

        +
        -

        info

        -

        Informational messages

        -

        Enable or not informational messages logging.

        + +

        info

        + + +

        Informational messages

        + + +

        Enable or not informational messages logging.

        +
        -

        level

        -

        Logging level

        -

        How much messages must be logged.

        -

        high,low,medium

        + +

        level

        + + +

        Logging level

        + + +

        How much messages must be logged.

        + + +

        high,low,medium

        + @@ -1458,45 +1721,76 @@ monitoring: -

        config

        -

        Configuration messages

        -

        Enable or not configuration messages logging.

        + +

        config

        + + +

        Configuration messages

        + + +

        Enable or not configuration messages logging.

        +
        -

        debug

        -

        Debug messages

        -

        Enable or not debug messages logging.

        + +

        debug

        + + +

        Debug messages

        + + +

        Enable or not debug messages logging.

        +
        -

        error

        -

        Error messages

        -

        Enable or not error messages logging.

        + +

        error

        + + +

        Error messages

        + + +

        Enable or not error messages logging.

        +
        -

        info

        -

        Informational messages

        -

        Enable or not informational messages logging.

        + +

        info

        + + +

        Informational messages

        + + +

        Enable or not informational messages logging.

        +
        -

        level

        -

        name

        -

        Logging level

        -

        Name of the logger

        -

        How much messages must be logged.

        -

        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

        -

        high,low,medium

        + +

        level

        +

        name

        + + +

        Logging level

        +

        Name of the logger

        + + +

        How much messages must be logged.

        +

        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

        + + +

        high,low,medium

        @@ -1572,33 +1866,57 @@ rrd: -

        buffering_timeout

        -

        Buffering timeout

        -

        Time in seconds to wait before launching failover.

        + +

        buffering_timeout

        + + +

        Buffering timeout

        + + +

        Time in seconds to wait before launching failover.

        +
        -

        failover

        -

        Failover name

        -

        Name of the output which will act as failover

        + +

        failover

        + + +

        Failover name

        + + +

        Name of the output which will act as failover

        +
        -

        retry_interval

        -

        Retry interval

        -

        Time in seconds to wait between each connection attempt.

        + +

        retry_interval

        + + +

        Retry interval

        + + +

        Time in seconds to wait between each connection attempt.

        +
        -

        category

        -

        Filter category

        -

        Category filter for flux in output.

        + +

        category

        + + +

        Filter category

        + + +

        Category filter for flux in output.

        +
        • @@ -1606,15 +1924,21 @@ rrd:
        -

        metrics_path

        + +

        metrics_path

        path

        -

        port

        -

        RRD file directory for metrics

        +

        port

        + + +

        RRD file directory for metrics

        Unix socket

        -

        TCP port

        -

        RRD file directory, for example /var/lib/centreon/metrics

        +

        TCP port

        + + +

        RRD file directory, for example /var/lib/centreon/metrics

        The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

        -

        The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

        +

        The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

        +
        • @@ -1622,33 +1946,57 @@ rrd:
        -

        status_path

        -

        RRD file directory for statuses

        -

        RRD file directory, for example /var/lib/centreon/status

        + +

        status_path

        + + +

        RRD file directory for statuses

        + + +

        RRD file directory, for example /var/lib/centreon/status

        +
        -

        write_metrics

        -

        Enable write_metrics

        -

        Enable or not write_metrics.

        + +

        write_metrics

        + + +

        Enable write_metrics

        + + +

        Enable or not write_metrics.

        +
        -

        write_status

        -

        Enable write_status

        -

        Enable or not write_status.

        + +

        write_status

        + + +

        Enable write_status

        + + +

        Enable or not write_status.

        +
        -

        store_in_data_bin

        -

        Enable store_in_data_bin

        -

        Enable or not store in performance data in data_bin.

        + +

        store_in_data_bin

        + + +

        Enable store_in_data_bin

        + + +

        Enable or not store in performance data in data_bin.

        +
        • @@ -1671,36 +2019,60 @@ storage: -

          buffering_timeout

          -

          Buffering timeout

          -

          Time in seconds to wait before launching failover.

          + +

          buffering_timeout

          + + +

          Buffering timeout

          + + +

          Time in seconds to wait before launching failover.

          +
          -

          failover

          -

          Failover name

          -

          Name of the output which will act as failover

          + +

          failover

          + + +

          Failover name

          + + +

          Name of the output which will act as failover

          +
          -

          retry_interval

          -

          Retry interval

          -

          Time in seconds to wait between each connection attempt.

          + +

          retry_interval

          + + +

          Retry interval

          + + +

          Time in seconds to wait between each connection attempt.

          +
          -

          category

          -

          check_replication

          -

          Filter category

          -

          Replication enabled

          -

          Category filter for flux in output.

          -

          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

          + +

          category

          +

          check_replication

          + + +

          Filter category

          +

          Replication enabled

          + + +

          Category filter for flux in output.

          +

          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

          +
          • @@ -1711,91 +2083,159 @@ storage:
          -

          db_host

          -

          DB host

          -

          IP address or hostname of the database server.

          + +

          db_host

          + + +

          DB host

          + + +

          IP address or hostname of the database server.

          +
          -

          db_name

          -

          DB name

          -

          Database name.

          + +

          db_name

          + + +

          DB name

          + + +

          Database name.

          +
          -

          db_password

          -

          DB password

          -

          Password of database user.

          + +

          db_password

          + + +

          DB password

          + + +

          Password of database user.

          +
          -

          db_port

          -

          DB port

          -

          Port on which the DB server listens

          + +

          db_port

          + + +

          DB port

          + + +

          Port on which the DB server listens

          +
          -

          db_type

          -

          DB type

          -

          Target DBMS.

          -

          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

          + +

          db_type

          + + +

          DB type

          + + +

          Target DBMS.

          + + +

          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

          + -

          db_user

          -

          DB user

          -

          Database user.

          + +

          db_user

          + + +

          DB user

          + + +

          Database user.

          +
          -

          interval

          -

          Interval length

          -

          Interval length in seconds.

          + +

          interval

          + + +

          Interval length

          + + +

          Interval length in seconds.

          +
          -

          length

          -

          RRD length

          -

          RRD storage duration in seconds.

          + +

          length

          + + +

          RRD length

          + + +

          RRD storage duration in seconds.

          +
          -

          queries_per_transaction

          -

          Maximum queries per transaction

          -

          The maximum queries per transaction before commit.

          + +

          queries_per_transaction

          + + +

          Maximum queries per transaction

          + + +

          The maximum queries per transaction before commit.

          +
          -

          read_timeout

          -

          rebuild_check_interval

          -

          Transaction commit timeout

          -

          Rebuild check interval in seconds

          -

          The transaction timeout before running commit.

          -

          The interval between check if some metrics must be rebuild. The default value is 300s

          + +

          read_timeout

          +

          rebuild_check_interval

          + + +

          Transaction commit timeout

          +

          Rebuild check interval in seconds

          + + +

          The transaction timeout before running commit.

          +

          The interval between check if some metrics must be rebuild. The default value is 300s

          +
          -

          store_in_data_bin

          -

          Enable store_in_data_bin

          -

          Enable or not store in performance data in data_bin.

          + +

          store_in_data_bin

          + + +

          Enable store_in_data_bin

          + + +

          Enable or not store in performance data in data_bin.

          +
          • @@ -1818,36 +2258,60 @@ sql: -

            buffering_timeout

            -

            Buffering timeout

            -

            Time in seconds to wait before launching failover.

            + +

            buffering_timeout

            + + +

            Buffering timeout

            + + +

            Time in seconds to wait before launching failover.

            +
            -

            failover

            -

            Failover name

            -

            Name of the output which will act as failover

            + +

            failover

            + + +

            Failover name

            + + +

            Name of the output which will act as failover

            +
            -

            retry_interval

            -

            Retry interval

            -

            Time in seconds to wait between each connection attempt.

            + +

            retry_interval

            + + +

            Retry interval

            + + +

            Time in seconds to wait between each connection attempt.

            +
            -

            category

            -

            check_replication

            -

            Filter category

            -

            Replication enabled

            -

            Category filter for flux in output.

            -

            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

            + +

            category

            +

            check_replication

            + + +

            Filter category

            +

            Replication enabled

            + + +

            Category filter for flux in output.

            +

            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

            +
            • @@ -1858,63 +2322,113 @@ sql:
            -

            db_host

            -

            DB host

            -

            IP address or hostname of the database server.

            + +

            db_host

            + + +

            DB host

            + + +

            IP address or hostname of the database server.

            +
            -

            db_name

            -

            DB name

            -

            Database name.

            + +

            db_name

            + + +

            DB name

            + + +

            Database name.

            +
            -

            db_password

            -

            DB password

            -

            Password of database user.

            + +

            db_password

            + + +

            DB password

            + + +

            Password of database user.

            +
            -

            db_port

            -

            DB port

            -

            Port on which the DB server listens

            + +

            db_port

            + + +

            DB port

            + + +

            Port on which the DB server listens

            +
            -

            db_type

            -

            DB type

            -

            Target DBMS.

            -

            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

            + +

            db_type

            + + +

            DB type

            + + +

            Target DBMS.

            + + +

            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

            + -

            db_user

            -

            DB user

            -

            Database user.

            + +

            db_user

            + + +

            DB user

            + + +

            Database user.

            +
            -

            queries_per_transaction

            -

            Maximum queries per transaction

            -

            The maximum queries per transaction before commit.

            + +

            queries_per_transaction

            + + +

            Maximum queries per transaction

            + + +

            The maximum queries per transaction before commit.

            +
            -

            read_timeout

            -

            Transaction commit timeout

            -

            The transaction timeout before running commit.

            + +

            read_timeout

            + + +

            Transaction commit timeout

            + + +

            The transaction timeout before running commit.

            +
            diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-api.md index 684ae6ba257e..dadee7409257 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-api.md @@ -50,14 +50,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -71,7 +71,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -79,7 +79,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-map-api.md index 75261ddfaeb7..4c2032ee0b1d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 22.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 22.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/rest-api-v1.md index dda750d3cd2d..6139646d0eb5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/api/rest-api-v1.md @@ -2486,8 +2486,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/connect/openid.md index 9f6e0a63a2a8..fed0bc81d27e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/connect/openid.md @@ -233,8 +233,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -245,7 +245,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -253,8 +253,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -265,7 +265,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -273,8 +273,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -293,8 +293,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/install.md index 77cd8feb4b97..fb47da6686d3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/install.md @@ -139,7 +139,7 @@ Pour optimiser le client lourd, vous devez lui allouer plus de mémoire que la v ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/troubleshooter.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/troubleshooter.md index aed41db971f5..eb022d55443d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/troubleshooter.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/graph-views/troubleshooter.md @@ -147,7 +147,7 @@ Pour ouvrir les ports appropriés : /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Remplacez par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). +> Remplacez \ par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). Pour désactiver votre pare-feu, exécutez : @@ -256,7 +256,7 @@ Pour ce faire, modifiez le fichier : ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -328,7 +328,7 @@ Si elle augmente et semble atteindre une limite alors que votre CPU travaille fo ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-central-server/using-packages.md index a28b5afd162a..b0f237c8ef68 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-central-server/using-packages.md @@ -470,11 +470,11 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTIO FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. +> Remplacez **\** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. > -> Remplacez **** et **** par les identifiants de l'utilisateur. +> Remplacez **\** et **\** par les identifiants de l'utilisateur. -Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md/) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : +Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : ```SQL DROP USER ''@''; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-poller/using-packages.md index c4afc8c2a3a6..b27d03db820c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-poller/using-packages.md @@ -331,10 +331,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -386,19 +386,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md index 19935dabe828..07abfb0a1284 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md @@ -462,10 +462,10 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP avec laquelle le serveur Centreon +> Remplacez **\** par l'adresse IP avec laquelle le serveur Centreon > Remote Server se connectera au serveur de base de données. > -> Remplacez **** et **** par les identifiants de +> Remplacez **\** et **\** par les identifiants de > l'utilisateur. Une fois l'installation terminée, supprimez cet utilisateur via la commande : @@ -679,9 +679,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -761,19 +761,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/prerequisites.md index efcc5a8d418a..8069d698dfa6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain

            | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain
            | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain

            | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain
            | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -153,7 +153,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain

            | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain
            | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -218,7 +218,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain

            | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain
            | **Serveur de bases de données** @@ -299,7 +299,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain

            | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
            Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
            • taille de la partition /var/lib/mysql * 0,6
            • valable pour 1 sauvegarde complète et 6 partielles
            • attention, cela reste une estimation et n'exclut pas un contrôle humain
            | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-events.md index 6f12c249b14a..1bc0b3f27b09 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-events.md @@ -232,4 +232,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md index 8da4a03af3a4..7eaa4d064a7a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md @@ -235,4 +235,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-logstash-events.md index 1b2bf06b0ee0..20e1553174e1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-logstash-events.md @@ -233,4 +233,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *8080*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-events.md index e3627abeaa15..db8f7443cda9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md index 4058bed7325c..8dbdc96fe011 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-opsgenie.md index 727f213bdfd0..b4fc01aa158c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-opsgenie.md @@ -179,7 +179,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-pagerduty-events.md index 79c22026cda4..d08c853f5763 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/event-management/sc-pagerduty-events.md @@ -296,4 +296,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-bmc-remedy.md index 95aaaf7944fd..dcc196ae6331 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-mail.md index 193de09442c3..af6e12a19a74 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-serena.md index 0b3dff0fdc64..e918149875a8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/notifications/plugin-telegram.md index 8ae3357e067d..8e07e79147e0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-3-4.md index 003d1bd37a63..3e5548fba182 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-3-4.md @@ -52,15 +52,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -82,8 +82,8 @@ Centreon. 22.10 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 22.10, supprimer les bases de @@ -131,7 +131,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-debian.md index 4f39c11e1ea1..a738f2417b0d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-debian.md @@ -48,10 +48,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -94,8 +94,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-el.md index 54c4b9f05c15..02c58db59cdf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/migrate-from-el-to-el.md @@ -48,10 +48,10 @@ dnf update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -81,8 +81,8 @@ dnf update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/poller-display-to-remote-server.md index 89809ae6fd47..50e0d51807d9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/migrate/poller-display-to-remote-server.md @@ -62,12 +62,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -144,19 +144,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/communications.md index c398b6194ea7..2138e23bfdf3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/releases/centreon-commercial-extensions.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/releases/centreon-commercial-extensions.md index 72ef43f00499..906b22af345c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/releases/centreon-commercial-extensions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/releases/centreon-commercial-extensions.md @@ -651,7 +651,7 @@ Release date: `July 4, 2024` #### Bug fixes - [Packaging] Added missing dependencies on anomaly detection. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**. ### 22.10.5 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/service-mapping/ba-management.md index 2f0789ec3bb9..f975101eec5d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-18-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-18-10.md index b30b40a0d624..fefa249ea291 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-18-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-18-10.md @@ -2,6 +2,8 @@ id: upgrade-from-18-10 title: Montée de version depuis Centreon 18.10 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme Centreon depuis la version 18.10 vers la version 22.10. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-04.md index 09e24ed633e2..41ac38fdd2cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-04.md @@ -2,6 +2,8 @@ id: upgrade-from-19-04 title: Montée de version depuis Centreon 19.04 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme Centreon depuis la version 19.04 vers la version 22.10. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-10.md index e2dc1bef9a3b..3714f9e24e3d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-19-10.md @@ -2,6 +2,8 @@ id: upgrade-from-19-10 title: Montée de version depuis Centreon 19.10 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme Centreon depuis la version 19.10 vers la version 22.10. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-20-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-20-04.md index 7a3e437dcbe4..80cb19beaa8d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-20-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-20-04.md @@ -2,6 +2,8 @@ id: upgrade-from-20-04 title: Montée de version depuis Centreon 20.04 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme Centreon depuis la version 20.04 vers la version 22.10. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-3-4.md index 032fd89f81ea..3cc88526c544 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-22.10/upgrade/upgrade-from-3-4.md @@ -2,6 +2,8 @@ id: upgrade-from-3-4 title: Montée de version depuis Centreon 3.4 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme Centreon depuis la version 3.4 (Centreon Web 2.8) vers la version 22.10. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

            Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

            + +

            Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

            • Ajouté : Indique que l'objet a été ajouté
            • Modifié : Indique que l'objet a été modifié
              • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

              La dernière colonne décrit la modification en elle-même :

              + +

              La dernière colonne décrit la modification en elle-même :

              • Nom du champ : Décrit le champ du formulaire modifié
              • Avant : Indique l'ancienne valeur
                • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/parameters/ldap.md index ef7da8bf952f..e900ea2e8e45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/parameters/ldap.md @@ -106,6 +106,6 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/secure-platform.md index de469941b003..a4595baa3925 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/administration/secure-platform.md @@ -768,17 +768,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1287,7 +1287,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/notif-config-for-teams.md index 5553d4d18996..14c73fbeb0a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/resources-status.md index 3d2ae7536796..6e9fddcae478 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/resources-status.md @@ -298,7 +298,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/ticketing.md index f40063645a43..e2189dc74110 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/alerts-notifications/ticketing.md @@ -147,9 +147,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/clapi.md index 081537551e3a..9aac45762aee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/clapi.md @@ -997,23 +997,35 @@ ipv4: -

                buffering_timeout

                -

                Buffering timeout

                -

                Time in seconds to wait before launching failover.

                + +

                buffering_timeout

                + + +

                Buffering timeout

                + + +

                Time in seconds to wait before launching failover.

                +
                -

                compression

                + +

                compression

                compression_buffer

                -

                compression_level

                -

                Compression (zlib)

                +

                compression_level

                + + +

                Compression (zlib)

                Compression buffer size

                -

                Compression level

                -

                Enable or not data stream compression.

                +

                Compression level

                + + +

                Enable or not data stream compression.

                The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                -

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +
                • @@ -1021,71 +1033,121 @@ ipv4:
                -

                retry_interval

                -

                Retry interval

                -

                Time in seconds to wait between each connection attempt.

                + +

                retry_interval

                + + +

                Retry interval

                + + +

                Time in seconds to wait between each connection attempt.

                +
                -

                category

                -

                Filter category

                -

                Category filter for flux in input

                + +

                category

                + + +

                Filter category

                + + +

                Category filter for flux in input

                +
                -

                ca_certificate

                -

                host

                -

                Trusted CA's certificate

                -

                Host to connect to

                -

                Trusted CA's certificate.

                -

                IP address or hostname of the host to connect to (leave blank for listening mode).

                + +

                ca_certificate

                +

                host

                + + +

                Trusted CA's certificate

                +

                Host to connect to

                + + +

                Trusted CA's certificate.

                +

                IP address or hostname of the host to connect to (leave blank for listening mode).

                +
                -

                one_peer_retention_mode

                -

                port

                -

                One peer retention

                -

                Connection port

                -

                This allows the retention to work even if the socket is listening

                -

                Port to listen on (empty host) or to connect to (with host filled).

                + +

                one_peer_retention_mode

                +

                port

                + + +

                One peer retention

                +

                Connection port

                + + +

                This allows the retention to work even if the socket is listening

                +

                Port to listen on (empty host) or to connect to (with host filled).

                +
                -

                private_key

                -

                Private key file.

                -

                Private key file path when TLS encryption is used.

                + +

                private_key

                + + +

                Private key file.

                + + +

                Private key file path when TLS encryption is used.

                +
                -

                protocol

                -

                Serialization protocol

                -

                Serialization protocol.

                -

                ndo

                + +

                protocol

                + + +

                Serialization protocol

                + + +

                Serialization protocol.

                + + +

                ndo

                + -

                public_cert

                -

                Public certificate

                -

                Public certificate file path when TLS encryption is used.

                + +

                public_cert

                + + +

                Public certificate

                + + +

                Public certificate file path when TLS encryption is used.

                +
                -

                tls

                -

                Enable TLS encryption

                -

                Enable TLS encryption.

                + +

                tls

                + + +

                Enable TLS encryption

                + + +

                Enable TLS encryption.

                +
                @@ -1106,23 +1168,35 @@ ipv6: -

                buffering_timeout

                -

                Buffering timeout

                -

                Time in seconds to wait before launching failover.

                + +

                buffering_timeout

                + + +

                Buffering timeout

                + + +

                Time in seconds to wait before launching failover.

                +
                -

                compression

                + +

                compression

                compression_buffer

                -

                compression_level

                -

                Compression (zlib)

                +

                compression_level

                + + +

                Compression (zlib)

                Compression buffer size

                -

                Compression level

                -

                Enable or not data stream compression.

                +

                Compression level

                + + +

                Enable or not data stream compression.

                The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                -

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +
                • @@ -1130,71 +1204,121 @@ ipv6:
                -

                retry_interval

                -

                Retry interval

                -

                Time in seconds to wait between each connection attempt.

                + +

                retry_interval

                + + +

                Retry interval

                + + +

                Time in seconds to wait between each connection attempt.

                +
                -

                category

                -

                Filter category

                -

                Category filter for flux in input

                + +

                category

                + + +

                Filter category

                + + +

                Category filter for flux in input

                +
                -

                ca_certificate

                -

                host

                -

                Trusted CA's certificate

                -

                Host to connect to

                -

                Trusted CA's certificate.

                -

                IP address or hostname of the host to connect to (leave blank for listening mode).

                + +

                ca_certificate

                +

                host

                + + +

                Trusted CA's certificate

                +

                Host to connect to

                + + +

                Trusted CA's certificate.

                +

                IP address or hostname of the host to connect to (leave blank for listening mode).

                +
                -

                one_peer_retention_mode

                -

                port

                -

                One peer retention

                -

                Connection port

                -

                This allows the retention to work even if the socket is listening

                -

                Port to listen on (empty host) or to connect to (with host filled).

                + +

                one_peer_retention_mode

                +

                port

                + + +

                One peer retention

                +

                Connection port

                + + +

                This allows the retention to work even if the socket is listening

                +

                Port to listen on (empty host) or to connect to (with host filled).

                +
                -

                private_key

                -

                Private key file.

                -

                Private key file path when TLS encryption is used.

                + +

                private_key

                + + +

                Private key file.

                + + +

                Private key file path when TLS encryption is used.

                +
                -

                protocol

                -

                Serialization protocol

                -

                Serialization protocol.

                -

                ndo

                + +

                protocol

                + + +

                Serialization protocol

                + + +

                Serialization protocol.

                + + +

                ndo

                + -

                public_cert

                -

                Public certificate

                -

                Public certificate file path when TLS encryption is used.

                + +

                public_cert

                + + +

                Public certificate

                + + +

                Public certificate file path when TLS encryption is used.

                +
                -

                tls

                -

                Enable TLS encryption

                -

                Enable TLS encryption.

                + +

                tls

                + + +

                Enable TLS encryption

                + + +

                Enable TLS encryption.

                +
                @@ -1215,23 +1339,35 @@ file: -

                buffering_timeout

                -

                Buffering timeout

                -

                Time in seconds to wait before launching failover.

                + +

                buffering_timeout

                + + +

                Buffering timeout

                + + +

                Time in seconds to wait before launching failover.

                +
                -

                compression

                + +

                compression

                compression_buffer

                -

                compression_level

                -

                Compression (zlib)

                +

                compression_level

                + + +

                Compression (zlib)

                Compression buffer size

                -

                Compression level

                -

                Enable or not data stream compression.

                +

                Compression level

                + + +

                Enable or not data stream compression.

                The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                -

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +

                Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                +
                • @@ -1239,34 +1375,60 @@ file:
                -

                retry_interval

                -

                Retry interval

                -

                Time in seconds to wait between each connection attempt.

                + +

                retry_interval

                + + +

                Retry interval

                + + +

                Time in seconds to wait between each connection attempt.

                +
                -

                max_size

                -

                Maximum size of file

                -

                Maximum size in bytes.

                + +

                max_size

                + + +

                Maximum size of file

                + + +

                Maximum size in bytes.

                +
                -

                path

                -

                File path

                -

                Path to the file.

                + +

                path

                + + +

                File path

                + + +

                Path to the file.

                +
                -

                protocol

                -

                Serialization protocol

                -

                Serialization protocol.

                -

                ndo

                + +

                protocol

                + + +

                Serialization protocol

                + + +

                Serialization protocol.

                + + +

                ndo

                + @@ -1286,50 +1448,88 @@ file: -

                config

                -

                Configuration messages

                -

                Enable or not configuration messages logging.

                + +

                config

                + + +

                Configuration messages

                + + +

                Enable or not configuration messages logging.

                +
                -

                debug

                -

                Debug messages

                -

                Enable or not debug messages logging.

                + +

                debug

                + + +

                Debug messages

                + + +

                Enable or not debug messages logging.

                +
                -

                error

                -

                Error messages

                -

                Enable or not error messages logging.

                + +

                error

                + + +

                Error messages

                + + +

                Enable or not error messages logging.

                +
                -

                info

                -

                Informational messages

                -

                Enable or not informational messages logging.

                + +

                info

                + + +

                Informational messages

                + + +

                Enable or not informational messages logging.

                +
                -

                level

                -

                Logging level

                -

                How much messages must be logged.

                -

                high,low,medium

                + +

                level

                + + +

                Logging level

                + + +

                How much messages must be logged.

                + + +

                high,low,medium

                + -

                max_size

                -

                name

                -

                Max file size in bytes

                -

                Name of the logger

                -

                The maximum size of log file.

                -

                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                + +

                max_size

                +

                name

                + + +

                Max file size in bytes

                +

                Name of the logger

                + + +

                The maximum size of log file.

                +

                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                +
                • @@ -1351,45 +1551,76 @@ standard: -

                  config

                  -

                  Configuration messages

                  -

                  Enable or not configuration messages logging.

                  + +

                  config

                  + + +

                  Configuration messages

                  + + +

                  Enable or not configuration messages logging.

                  +
                  -

                  debug

                  -

                  Debug messages

                  -

                  Enable or not debug messages logging.

                  + +

                  debug

                  + + +

                  Debug messages

                  + + +

                  Enable or not debug messages logging.

                  +
                  -

                  error

                  -

                  Error messages

                  -

                  Enable or not error messages logging.

                  + +

                  error

                  + + +

                  Error messages

                  + + +

                  Enable or not error messages logging.

                  +
                  -

                  info

                  -

                  Informational messages

                  -

                  Enable or not informational messages logging.

                  + +

                  info

                  + + +

                  Informational messages

                  + + +

                  Enable or not informational messages logging.

                  +
                  -

                  level

                  -

                  name

                  -

                  Logging level

                  -

                  Name of the logger

                  -

                  How much messages must be logged.

                  -

                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                  -

                  high,low,medium

                  + +

                  level

                  +

                  name

                  + + +

                  Logging level

                  +

                  Name of the logger

                  + + +

                  How much messages must be logged.

                  +

                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                  + + +

                  high,low,medium

                  @@ -1410,42 +1641,74 @@ syslog: -

                  config

                  -

                  Configuration messages

                  -

                  Enable or not configuration messages logging.

                  + +

                  config

                  + + +

                  Configuration messages

                  + + +

                  Enable or not configuration messages logging.

                  +
                  -

                  debug

                  -

                  Debug messages

                  -

                  Enable or not debug messages logging.

                  + +

                  debug

                  + + +

                  Debug messages

                  + + +

                  Enable or not debug messages logging.

                  +
                  -

                  error

                  -

                  Error messages

                  -

                  Enable or not error messages logging.

                  + +

                  error

                  + + +

                  Error messages

                  + + +

                  Enable or not error messages logging.

                  +
                  -

                  info

                  -

                  Informational messages

                  -

                  Enable or not informational messages logging.

                  + +

                  info

                  + + +

                  Informational messages

                  + + +

                  Enable or not informational messages logging.

                  +
                  -

                  level

                  -

                  Logging level

                  -

                  How much messages must be logged.

                  -

                  high,low,medium

                  + +

                  level

                  + + +

                  Logging level

                  + + +

                  How much messages must be logged.

                  + + +

                  high,low,medium

                  + @@ -1463,45 +1726,76 @@ monitoring: -

                  config

                  -

                  Configuration messages

                  -

                  Enable or not configuration messages logging.

                  + +

                  config

                  + + +

                  Configuration messages

                  + + +

                  Enable or not configuration messages logging.

                  +
                  -

                  debug

                  -

                  Debug messages

                  -

                  Enable or not debug messages logging.

                  + +

                  debug

                  + + +

                  Debug messages

                  + + +

                  Enable or not debug messages logging.

                  +
                  -

                  error

                  -

                  Error messages

                  -

                  Enable or not error messages logging.

                  + +

                  error

                  + + +

                  Error messages

                  + + +

                  Enable or not error messages logging.

                  +
                  -

                  info

                  -

                  Informational messages

                  -

                  Enable or not informational messages logging.

                  + +

                  info

                  + + +

                  Informational messages

                  + + +

                  Enable or not informational messages logging.

                  +
                  -

                  level

                  -

                  name

                  -

                  Logging level

                  -

                  Name of the logger

                  -

                  How much messages must be logged.

                  -

                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                  -

                  high,low,medium

                  + +

                  level

                  +

                  name

                  + + +

                  Logging level

                  +

                  Name of the logger

                  + + +

                  How much messages must be logged.

                  +

                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                  + + +

                  high,low,medium

                  @@ -1577,33 +1871,57 @@ rrd: -

                  buffering_timeout

                  -

                  Buffering timeout

                  -

                  Time in seconds to wait before launching failover.

                  + +

                  buffering_timeout

                  + + +

                  Buffering timeout

                  + + +

                  Time in seconds to wait before launching failover.

                  +
                  -

                  failover

                  -

                  Failover name

                  -

                  Name of the output which will act as failover

                  + +

                  failover

                  + + +

                  Failover name

                  + + +

                  Name of the output which will act as failover

                  +
                  -

                  retry_interval

                  -

                  Retry interval

                  -

                  Time in seconds to wait between each connection attempt.

                  + +

                  retry_interval

                  + + +

                  Retry interval

                  + + +

                  Time in seconds to wait between each connection attempt.

                  +
                  -

                  category

                  -

                  Filter category

                  -

                  Category filter for flux in output.

                  + +

                  category

                  + + +

                  Filter category

                  + + +

                  Category filter for flux in output.

                  +
                  • @@ -1611,15 +1929,21 @@ rrd:
                  -

                  metrics_path

                  + +

                  metrics_path

                  path

                  -

                  port

                  -

                  RRD file directory for metrics

                  +

                  port

                  + + +

                  RRD file directory for metrics

                  Unix socket

                  -

                  TCP port

                  -

                  RRD file directory, for example /var/lib/centreon/metrics

                  +

                  TCP port

                  + + +

                  RRD file directory, for example /var/lib/centreon/metrics

                  The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                  -

                  The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                  +

                  The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                  +
                  • @@ -1627,33 +1951,57 @@ rrd:
                  -

                  status_path

                  -

                  RRD file directory for statuses

                  -

                  RRD file directory, for example /var/lib/centreon/status

                  + +

                  status_path

                  + + +

                  RRD file directory for statuses

                  + + +

                  RRD file directory, for example /var/lib/centreon/status

                  +
                  -

                  write_metrics

                  -

                  Enable write_metrics

                  -

                  Enable or not write_metrics.

                  + +

                  write_metrics

                  + + +

                  Enable write_metrics

                  + + +

                  Enable or not write_metrics.

                  +
                  -

                  write_status

                  -

                  Enable write_status

                  -

                  Enable or not write_status.

                  + +

                  write_status

                  + + +

                  Enable write_status

                  + + +

                  Enable or not write_status.

                  +
                  -

                  store_in_data_bin

                  -

                  Enable store_in_data_bin

                  -

                  Enable or not store in performance data in data_bin.

                  + +

                  store_in_data_bin

                  + + +

                  Enable store_in_data_bin

                  + + +

                  Enable or not store in performance data in data_bin.

                  +
                  • @@ -1676,36 +2024,60 @@ storage: -

                    buffering_timeout

                    -

                    Buffering timeout

                    -

                    Time in seconds to wait before launching failover.

                    + +

                    buffering_timeout

                    + + +

                    Buffering timeout

                    + + +

                    Time in seconds to wait before launching failover.

                    +
                    -

                    failover

                    -

                    Failover name

                    -

                    Name of the output which will act as failover

                    + +

                    failover

                    + + +

                    Failover name

                    + + +

                    Name of the output which will act as failover

                    +
                    -

                    retry_interval

                    -

                    Retry interval

                    -

                    Time in seconds to wait between each connection attempt.

                    + +

                    retry_interval

                    + + +

                    Retry interval

                    + + +

                    Time in seconds to wait between each connection attempt.

                    +
                    -

                    category

                    -

                    check_replication

                    -

                    Filter category

                    -

                    Replication enabled

                    -

                    Category filter for flux in output.

                    -

                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                    + +

                    category

                    +

                    check_replication

                    + + +

                    Filter category

                    +

                    Replication enabled

                    + + +

                    Category filter for flux in output.

                    +

                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                    +
                    • @@ -1716,91 +2088,159 @@ storage:
                    -

                    db_host

                    -

                    DB host

                    -

                    IP address or hostname of the database server.

                    + +

                    db_host

                    + + +

                    DB host

                    + + +

                    IP address or hostname of the database server.

                    +
                    -

                    db_name

                    -

                    DB name

                    -

                    Database name.

                    + +

                    db_name

                    + + +

                    DB name

                    + + +

                    Database name.

                    +
                    -

                    db_password

                    -

                    DB password

                    -

                    Password of database user.

                    + +

                    db_password

                    + + +

                    DB password

                    + + +

                    Password of database user.

                    +
                    -

                    db_port

                    -

                    DB port

                    -

                    Port on which the DB server listens

                    + +

                    db_port

                    + + +

                    DB port

                    + + +

                    Port on which the DB server listens

                    +
                    -

                    db_type

                    -

                    DB type

                    -

                    Target DBMS.

                    -

                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                    + +

                    db_type

                    + + +

                    DB type

                    + + +

                    Target DBMS.

                    + + +

                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                    + -

                    db_user

                    -

                    DB user

                    -

                    Database user.

                    + +

                    db_user

                    + + +

                    DB user

                    + + +

                    Database user.

                    +
                    -

                    interval

                    -

                    Interval length

                    -

                    Interval length in seconds.

                    + +

                    interval

                    + + +

                    Interval length

                    + + +

                    Interval length in seconds.

                    +
                    -

                    length

                    -

                    RRD length

                    -

                    RRD storage duration in seconds.

                    + +

                    length

                    + + +

                    RRD length

                    + + +

                    RRD storage duration in seconds.

                    +
                    -

                    queries_per_transaction

                    -

                    Maximum queries per transaction

                    -

                    The maximum queries per transaction before commit.

                    + +

                    queries_per_transaction

                    + + +

                    Maximum queries per transaction

                    + + +

                    The maximum queries per transaction before commit.

                    +
                    -

                    read_timeout

                    -

                    rebuild_check_interval

                    -

                    Transaction commit timeout

                    -

                    Rebuild check interval in seconds

                    -

                    The transaction timeout before running commit.

                    -

                    The interval between check if some metrics must be rebuild. The default value is 300s

                    + +

                    read_timeout

                    +

                    rebuild_check_interval

                    + + +

                    Transaction commit timeout

                    +

                    Rebuild check interval in seconds

                    + + +

                    The transaction timeout before running commit.

                    +

                    The interval between check if some metrics must be rebuild. The default value is 300s

                    +
                    -

                    store_in_data_bin

                    -

                    Enable store_in_data_bin

                    -

                    Enable or not store in performance data in data_bin.

                    + +

                    store_in_data_bin

                    + + +

                    Enable store_in_data_bin

                    + + +

                    Enable or not store in performance data in data_bin.

                    +
                    • @@ -1823,36 +2263,60 @@ sql: -

                      buffering_timeout

                      -

                      Buffering timeout

                      -

                      Time in seconds to wait before launching failover.

                      + +

                      buffering_timeout

                      + + +

                      Buffering timeout

                      + + +

                      Time in seconds to wait before launching failover.

                      +
                      -

                      failover

                      -

                      Failover name

                      -

                      Name of the output which will act as failover

                      + +

                      failover

                      + + +

                      Failover name

                      + + +

                      Name of the output which will act as failover

                      +
                      -

                      retry_interval

                      -

                      Retry interval

                      -

                      Time in seconds to wait between each connection attempt.

                      + +

                      retry_interval

                      + + +

                      Retry interval

                      + + +

                      Time in seconds to wait between each connection attempt.

                      +
                      -

                      category

                      -

                      check_replication

                      -

                      Filter category

                      -

                      Replication enabled

                      -

                      Category filter for flux in output.

                      -

                      When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                      + +

                      category

                      +

                      check_replication

                      + + +

                      Filter category

                      +

                      Replication enabled

                      + + +

                      Category filter for flux in output.

                      +

                      When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                      +
                      • @@ -1863,63 +2327,113 @@ sql:
                      -

                      db_host

                      -

                      DB host

                      -

                      IP address or hostname of the database server.

                      + +

                      db_host

                      + + +

                      DB host

                      + + +

                      IP address or hostname of the database server.

                      +
                      -

                      db_name

                      -

                      DB name

                      -

                      Database name.

                      + +

                      db_name

                      + + +

                      DB name

                      + + +

                      Database name.

                      +
                      -

                      db_password

                      -

                      DB password

                      -

                      Password of database user.

                      + +

                      db_password

                      + + +

                      DB password

                      + + +

                      Password of database user.

                      +
                      -

                      db_port

                      -

                      DB port

                      -

                      Port on which the DB server listens

                      + +

                      db_port

                      + + +

                      DB port

                      + + +

                      Port on which the DB server listens

                      +
                      -

                      db_type

                      -

                      DB type

                      -

                      Target DBMS.

                      -

                      db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                      + +

                      db_type

                      + + +

                      DB type

                      + + +

                      Target DBMS.

                      + + +

                      db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                      + -

                      db_user

                      -

                      DB user

                      -

                      Database user.

                      + +

                      db_user

                      + + +

                      DB user

                      + + +

                      Database user.

                      +
                      -

                      queries_per_transaction

                      -

                      Maximum queries per transaction

                      -

                      The maximum queries per transaction before commit.

                      + +

                      queries_per_transaction

                      + + +

                      Maximum queries per transaction

                      + + +

                      The maximum queries per transaction before commit.

                      +
                      -

                      read_timeout

                      -

                      Transaction commit timeout

                      -

                      The transaction timeout before running commit.

                      + +

                      read_timeout

                      + + +

                      Transaction commit timeout

                      + + +

                      The transaction timeout before running commit.

                      +
                      diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-api.md index 684ae6ba257e..dadee7409257 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-api.md @@ -50,14 +50,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -71,7 +71,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -79,7 +79,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-map-api.md index 7fcd483b9236..df4586140f1c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 23.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 23.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v1.md index dda750d3cd2d..6139646d0eb5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v1.md @@ -2486,8 +2486,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v2.md index 4a9d04713f13..dc16c9df475c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/api/rest-api-v2.md @@ -71,12 +71,12 @@ environnements. > > Voici un exemple de résultat : > -> { +> \{ > "version": "23.04.6", > "major": "23", > "minor": "04", > "fix": "6" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/openid.md index 5ab325438718..f45e0200a313 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/openid.md @@ -241,8 +241,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -253,7 +253,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -261,8 +261,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -273,7 +273,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -281,8 +281,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -301,8 +301,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/saml.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/saml.md index d0bec3788518..7d5a08ea67e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/saml.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/connect/saml.md @@ -133,6 +133,6 @@ vos utilisateurs. Voici un exemple de champs que vous devrez peut-être remplir | Option fournisseur d'identité | Valeur Centreon | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https://\ | +| Assertion Consumer Service (ACS) URL | https://\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https://\/centreon/api/latest/saml/sls | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/install.md index 5cf29ed30187..ac4aef9fc5ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/install.md @@ -139,7 +139,7 @@ Pour optimiser le client lourd, vous devez lui allouer plus de mémoire que la v ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/troubleshooter.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/troubleshooter.md index 3ddceedfa8c1..7aef2f2b73df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/troubleshooter.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/graph-views/troubleshooter.md @@ -147,7 +147,7 @@ Pour ouvrir les ports appropriés : /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Remplacez par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). +> Remplacez \ par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). Pour désactiver votre pare-feu, exécutez : @@ -256,7 +256,7 @@ Pour ce faire, modifiez le fichier : ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -328,7 +328,7 @@ Si elle augmente et semble atteindre une limite alors que votre CPU travaille fo ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-central-server/using-packages.md index e73422c72e3a..93bc8ef88988 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-central-server/using-packages.md @@ -533,11 +533,11 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTIO FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. +> Remplacez **\** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. > -> Remplacez **** et **** par les identifiants de l'utilisateur. +> Remplacez **\** et **\** par les identifiants de l'utilisateur. -Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md/) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : +Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : ```SQL DROP USER ''@''; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-poller/using-packages.md index d194fb830b4b..49ca085a2eba 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-poller/using-packages.md @@ -384,10 +384,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -439,19 +439,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md index b5c8bf070821..6063d1fb0ec7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md @@ -517,10 +517,10 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP avec laquelle le serveur Centreon +> Remplacez **\** par l'adresse IP avec laquelle le serveur Centreon > Remote Server se connectera au serveur de base de données. > -> Remplacez **** et **** par les identifiants de +> Remplacez **\** et **\** par les identifiants de > l'utilisateur. Une fois l'installation terminée, supprimez cet utilisateur via la commande : @@ -760,9 +760,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -842,19 +842,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/prerequisites.md index 6c2719a7accf..d2b7b50c093b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain

                      | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain
                      | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain

                      | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain
                      | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -152,7 +152,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain

                      | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain
                      | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -216,7 +216,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain

                      | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain
                      | **Serveur de bases de données** @@ -297,7 +297,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain

                      | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                      Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                      • taille de la partition /var/lib/mysql * 0,6
                      • valable pour 1 sauvegarde complète et 6 partielles
                      • attention, cela reste une estimation et n'exclut pas un contrôle humain
                      | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-events.md index 7637d80740ec..34dd377d77f7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-events.md @@ -152,4 +152,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md index 3bc9b8febfe5..bf4bc957183e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md @@ -155,4 +155,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-logstash-events.md index d699f461980c..9c6471ec74ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-logstash-events.md @@ -153,4 +153,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *8080*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-events.md index e3627abeaa15..db8f7443cda9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md index 4058bed7325c..8dbdc96fe011 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-opsgenie.md index f15658eef774..f70c2f0ca595 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-opsgenie.md @@ -187,7 +187,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-pagerduty-events.md index dddaf884d79a..0be6f8aca30a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/event-management/sc-pagerduty-events.md @@ -202,4 +202,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-bmc-remedy.md index fd68064330d3..3eb8886aeb16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-mail.md index 9dd2755aef22..79ddfa181efd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-serena.md index 963006e1b735..6ab6ff9740ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/notifications/plugin-telegram.md index 8d3f8abc7084..ea1ed0e6641c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/metrology/grafana.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/metrology/grafana.md index 6a9dcebe3525..85ba2271badf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/metrology/grafana.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/metrology/grafana.md @@ -86,5 +86,5 @@ Utilisez des [variables](https://grafana.com/docs/grafana/latest/variables/) pou Vous pouvez personnaliser l'affichage des libellés des courbes : dans la section **Time Series > Standard options**, utilisez [le champ **Display name**](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* Par exemple, si vous entrez **${__field.labels}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). -* Si vous entrez **${__field.labels.host}: ${__field.labels.metric_name}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. +* Par exemple, si vous entrez **$\{__field.labels\}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). +* Si vous entrez **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-3-4.md index a6d5c7814bd1..304f886c1e9a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-3-4.md @@ -72,15 +72,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -102,8 +102,8 @@ Centreon. 23.04 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 23.04, supprimer les bases de @@ -151,7 +151,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-debian.md index 470cc7a6caa3..1950ed3296fd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-debian.md @@ -52,10 +52,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-el.md index 6923d55a960a..d8d28d6c73ff 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/migrate-from-el-to-el.md @@ -72,10 +72,10 @@ apt update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -105,8 +105,8 @@ apt update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/poller-display-to-remote-server.md index a73a33701b8f..4cc9adeacf20 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/migrate/poller-display-to-remote-server.md @@ -58,12 +58,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -140,19 +140,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/communications.md index c398b6194ea7..2138e23bfdf3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/releases/centreon-commercial-extensions.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/releases/centreon-commercial-extensions.mdx index 664627fcf708..5e5fda3e700d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/releases/centreon-commercial-extensions.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/releases/centreon-commercial-extensions.mdx @@ -265,8 +265,7 @@ Release date: `November 22, 2023` Release date: `October 10, 2023`
                      - Bug fixes - + Bug fixes - [Server] Updated dependencies. @@ -430,8 +429,7 @@ Release date: `July 29, 2024` Release date: `November 22, 2023`
                      - Bug fixes - + Bug fixes - [Server] Fixed an issue that caused server to crash on duplicated Centreon modules. - [Viewer] Fixed the redirection to monitoring pages from tooltips. @@ -443,8 +441,7 @@ Release date: `November 22, 2023` Release date: `October 10, 2023`
                      - Bug fixes - + Bug fixes - [Server] Updated dependencies. @@ -1000,7 +997,7 @@ Release date: `July 4, 2024` Bug fixes - [Packaging] Added missing dependencies on anomaly detection. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**.
                      diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/service-mapping/ba-management.md index 6b0a450cb6fc..3f413b9cf690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.04/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.04/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

                      Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                      + +

                      Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                      • Ajouté : Indique que l'objet a été ajouté
                      • Modifié : Indique que l'objet a été modifié
                        • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

                        La dernière colonne décrit la modification en elle-même :

                        + +

                        La dernière colonne décrit la modification en elle-même :

                        • Nom du champ : Décrit le champ du formulaire modifié
                        • Avant : Indique l'ancienne valeur
                          • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/parameters/ldap.md index 338e6b555352..7524d006e8e9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/parameters/ldap.md @@ -106,6 +106,6 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/secure-platform.md index a138e0129808..fcf85a9e7f13 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/administration/secure-platform.md @@ -768,17 +768,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1287,7 +1287,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/notif-config-for-teams.md index 5553d4d18996..14c73fbeb0a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/resources-status.md index bc63a22c53a3..80cb8390f7d6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/resources-status.md @@ -307,7 +307,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/ticketing.md index f40063645a43..e2189dc74110 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/alerts-notifications/ticketing.md @@ -147,9 +147,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/clapi.md index c94701c88af1..e8205ec9d99d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/clapi.md @@ -998,23 +998,35 @@ ipv4: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1022,71 +1034,121 @@ ipv4:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1107,23 +1169,35 @@ ipv6: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1131,71 +1205,121 @@ ipv6:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1216,23 +1340,35 @@ file: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1240,34 +1376,60 @@ file:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          max_size

                          -

                          Maximum size of file

                          -

                          Maximum size in bytes.

                          + +

                          max_size

                          + + +

                          Maximum size of file

                          + + +

                          Maximum size in bytes.

                          +
                          -

                          path

                          -

                          File path

                          -

                          Path to the file.

                          + +

                          path

                          + + +

                          File path

                          + + +

                          Path to the file.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + @@ -1287,50 +1449,88 @@ file: -

                          config

                          -

                          Configuration messages

                          -

                          Enable or not configuration messages logging.

                          + +

                          config

                          + + +

                          Configuration messages

                          + + +

                          Enable or not configuration messages logging.

                          +
                          -

                          debug

                          -

                          Debug messages

                          -

                          Enable or not debug messages logging.

                          + +

                          debug

                          + + +

                          Debug messages

                          + + +

                          Enable or not debug messages logging.

                          +
                          -

                          error

                          -

                          Error messages

                          -

                          Enable or not error messages logging.

                          + +

                          error

                          + + +

                          Error messages

                          + + +

                          Enable or not error messages logging.

                          +
                          -

                          info

                          -

                          Informational messages

                          -

                          Enable or not informational messages logging.

                          + +

                          info

                          + + +

                          Informational messages

                          + + +

                          Enable or not informational messages logging.

                          +
                          -

                          level

                          -

                          Logging level

                          -

                          How much messages must be logged.

                          -

                          high,low,medium

                          + +

                          level

                          + + +

                          Logging level

                          + + +

                          How much messages must be logged.

                          + + +

                          high,low,medium

                          + -

                          max_size

                          -

                          name

                          -

                          Max file size in bytes

                          -

                          Name of the logger

                          -

                          The maximum size of log file.

                          -

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          + +

                          max_size

                          +

                          name

                          + + +

                          Max file size in bytes

                          +

                          Name of the logger

                          + + +

                          The maximum size of log file.

                          +

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          +
                          • @@ -1352,45 +1552,76 @@ standard: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1411,42 +1642,74 @@ syslog: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            Logging level

                            -

                            How much messages must be logged.

                            -

                            high,low,medium

                            + +

                            level

                            + + +

                            Logging level

                            + + +

                            How much messages must be logged.

                            + + +

                            high,low,medium

                            + @@ -1464,45 +1727,76 @@ monitoring: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1578,33 +1872,57 @@ rrd: -

                            buffering_timeout

                            -

                            Buffering timeout

                            -

                            Time in seconds to wait before launching failover.

                            + +

                            buffering_timeout

                            + + +

                            Buffering timeout

                            + + +

                            Time in seconds to wait before launching failover.

                            +
                            -

                            failover

                            -

                            Failover name

                            -

                            Name of the output which will act as failover

                            + +

                            failover

                            + + +

                            Failover name

                            + + +

                            Name of the output which will act as failover

                            +
                            -

                            retry_interval

                            -

                            Retry interval

                            -

                            Time in seconds to wait between each connection attempt.

                            + +

                            retry_interval

                            + + +

                            Retry interval

                            + + +

                            Time in seconds to wait between each connection attempt.

                            +
                            -

                            category

                            -

                            Filter category

                            -

                            Category filter for flux in output.

                            + +

                            category

                            + + +

                            Filter category

                            + + +

                            Category filter for flux in output.

                            +
                            • @@ -1612,15 +1930,21 @@ rrd:
                            -

                            metrics_path

                            + +

                            metrics_path

                            path

                            -

                            port

                            -

                            RRD file directory for metrics

                            +

                            port

                            + + +

                            RRD file directory for metrics

                            Unix socket

                            -

                            TCP port

                            -

                            RRD file directory, for example /var/lib/centreon/metrics

                            +

                            TCP port

                            + + +

                            RRD file directory, for example /var/lib/centreon/metrics

                            The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            -

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +
                            • @@ -1628,33 +1952,57 @@ rrd:
                            -

                            status_path

                            -

                            RRD file directory for statuses

                            -

                            RRD file directory, for example /var/lib/centreon/status

                            + +

                            status_path

                            + + +

                            RRD file directory for statuses

                            + + +

                            RRD file directory, for example /var/lib/centreon/status

                            +
                            -

                            write_metrics

                            -

                            Enable write_metrics

                            -

                            Enable or not write_metrics.

                            + +

                            write_metrics

                            + + +

                            Enable write_metrics

                            + + +

                            Enable or not write_metrics.

                            +
                            -

                            write_status

                            -

                            Enable write_status

                            -

                            Enable or not write_status.

                            + +

                            write_status

                            + + +

                            Enable write_status

                            + + +

                            Enable or not write_status.

                            +
                            -

                            store_in_data_bin

                            -

                            Enable store_in_data_bin

                            -

                            Enable or not store in performance data in data_bin.

                            + +

                            store_in_data_bin

                            + + +

                            Enable store_in_data_bin

                            + + +

                            Enable or not store in performance data in data_bin.

                            +
                            • @@ -1677,36 +2025,60 @@ storage: -

                              buffering_timeout

                              -

                              Buffering timeout

                              -

                              Time in seconds to wait before launching failover.

                              + +

                              buffering_timeout

                              + + +

                              Buffering timeout

                              + + +

                              Time in seconds to wait before launching failover.

                              +
                              -

                              failover

                              -

                              Failover name

                              -

                              Name of the output which will act as failover

                              + +

                              failover

                              + + +

                              Failover name

                              + + +

                              Name of the output which will act as failover

                              +
                              -

                              retry_interval

                              -

                              Retry interval

                              -

                              Time in seconds to wait between each connection attempt.

                              + +

                              retry_interval

                              + + +

                              Retry interval

                              + + +

                              Time in seconds to wait between each connection attempt.

                              +
                              -

                              category

                              -

                              check_replication

                              -

                              Filter category

                              -

                              Replication enabled

                              -

                              Category filter for flux in output.

                              -

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              + +

                              category

                              +

                              check_replication

                              + + +

                              Filter category

                              +

                              Replication enabled

                              + + +

                              Category filter for flux in output.

                              +

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              +
                              • @@ -1717,91 +2089,159 @@ storage:
                              -

                              db_host

                              -

                              DB host

                              -

                              IP address or hostname of the database server.

                              + +

                              db_host

                              + + +

                              DB host

                              + + +

                              IP address or hostname of the database server.

                              +
                              -

                              db_name

                              -

                              DB name

                              -

                              Database name.

                              + +

                              db_name

                              + + +

                              DB name

                              + + +

                              Database name.

                              +
                              -

                              db_password

                              -

                              DB password

                              -

                              Password of database user.

                              + +

                              db_password

                              + + +

                              DB password

                              + + +

                              Password of database user.

                              +
                              -

                              db_port

                              -

                              DB port

                              -

                              Port on which the DB server listens

                              + +

                              db_port

                              + + +

                              DB port

                              + + +

                              Port on which the DB server listens

                              +
                              -

                              db_type

                              -

                              DB type

                              -

                              Target DBMS.

                              -

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + +

                              db_type

                              + + +

                              DB type

                              + + +

                              Target DBMS.

                              + + +

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + -

                              db_user

                              -

                              DB user

                              -

                              Database user.

                              + +

                              db_user

                              + + +

                              DB user

                              + + +

                              Database user.

                              +
                              -

                              interval

                              -

                              Interval length

                              -

                              Interval length in seconds.

                              + +

                              interval

                              + + +

                              Interval length

                              + + +

                              Interval length in seconds.

                              +
                              -

                              length

                              -

                              RRD length

                              -

                              RRD storage duration in seconds.

                              + +

                              length

                              + + +

                              RRD length

                              + + +

                              RRD storage duration in seconds.

                              +
                              -

                              queries_per_transaction

                              -

                              Maximum queries per transaction

                              -

                              The maximum queries per transaction before commit.

                              + +

                              queries_per_transaction

                              + + +

                              Maximum queries per transaction

                              + + +

                              The maximum queries per transaction before commit.

                              +
                              -

                              read_timeout

                              -

                              rebuild_check_interval

                              -

                              Transaction commit timeout

                              -

                              Rebuild check interval in seconds

                              -

                              The transaction timeout before running commit.

                              -

                              The interval between check if some metrics must be rebuild. The default value is 300s

                              + +

                              read_timeout

                              +

                              rebuild_check_interval

                              + + +

                              Transaction commit timeout

                              +

                              Rebuild check interval in seconds

                              + + +

                              The transaction timeout before running commit.

                              +

                              The interval between check if some metrics must be rebuild. The default value is 300s

                              +
                              -

                              store_in_data_bin

                              -

                              Enable store_in_data_bin

                              -

                              Enable or not store in performance data in data_bin.

                              + +

                              store_in_data_bin

                              + + +

                              Enable store_in_data_bin

                              + + +

                              Enable or not store in performance data in data_bin.

                              +
                              • @@ -1824,36 +2264,60 @@ sql: -

                                buffering_timeout

                                -

                                Buffering timeout

                                -

                                Time in seconds to wait before launching failover.

                                + +

                                buffering_timeout

                                + + +

                                Buffering timeout

                                + + +

                                Time in seconds to wait before launching failover.

                                +
                                -

                                failover

                                -

                                Failover name

                                -

                                Name of the output which will act as failover

                                + +

                                failover

                                + + +

                                Failover name

                                + + +

                                Name of the output which will act as failover

                                +
                                -

                                retry_interval

                                -

                                Retry interval

                                -

                                Time in seconds to wait between each connection attempt.

                                + +

                                retry_interval

                                + + +

                                Retry interval

                                + + +

                                Time in seconds to wait between each connection attempt.

                                +
                                -

                                category

                                -

                                check_replication

                                -

                                Filter category

                                -

                                Replication enabled

                                -

                                Category filter for flux in output.

                                -

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                + +

                                category

                                +

                                check_replication

                                + + +

                                Filter category

                                +

                                Replication enabled

                                + + +

                                Category filter for flux in output.

                                +

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                +
                                • @@ -1864,63 +2328,113 @@ sql:
                                -

                                db_host

                                -

                                DB host

                                -

                                IP address or hostname of the database server.

                                + +

                                db_host

                                + + +

                                DB host

                                + + +

                                IP address or hostname of the database server.

                                +
                                -

                                db_name

                                -

                                DB name

                                -

                                Database name.

                                + +

                                db_name

                                + + +

                                DB name

                                + + +

                                Database name.

                                +
                                -

                                db_password

                                -

                                DB password

                                -

                                Password of database user.

                                + +

                                db_password

                                + + +

                                DB password

                                + + +

                                Password of database user.

                                +
                                -

                                db_port

                                -

                                DB port

                                -

                                Port on which the DB server listens

                                + +

                                db_port

                                + + +

                                DB port

                                + + +

                                Port on which the DB server listens

                                +
                                -

                                db_type

                                -

                                DB type

                                -

                                Target DBMS.

                                -

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + +

                                db_type

                                + + +

                                DB type

                                + + +

                                Target DBMS.

                                + + +

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + -

                                db_user

                                -

                                DB user

                                -

                                Database user.

                                + +

                                db_user

                                + + +

                                DB user

                                + + +

                                Database user.

                                +
                                -

                                queries_per_transaction

                                -

                                Maximum queries per transaction

                                -

                                The maximum queries per transaction before commit.

                                + +

                                queries_per_transaction

                                + + +

                                Maximum queries per transaction

                                + + +

                                The maximum queries per transaction before commit.

                                +
                                -

                                read_timeout

                                -

                                Transaction commit timeout

                                -

                                The transaction timeout before running commit.

                                + +

                                read_timeout

                                + + +

                                Transaction commit timeout

                                + + +

                                The transaction timeout before running commit.

                                +
                                diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-api.md index fbed288daf9c..3c69f785f28f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-api.md @@ -50,14 +50,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -71,7 +71,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -79,7 +79,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-map-api.md index e294230cb95e..759ff565ad4a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 23.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 23.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v1.md index dda750d3cd2d..6139646d0eb5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v1.md @@ -2486,8 +2486,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v2.md index cb774645ef3e..59aa3bc812c9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/api/rest-api-v2.md @@ -71,12 +71,12 @@ environnements. > > Voici un exemple de résultat : > -> { +> \{ > "version": "23.10.6", > "major": "23", > "minor": "10", > "fix": "6" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/openid.md index 5de0473e0070..7fcb60c5b71b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/openid.md @@ -241,8 +241,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -253,7 +253,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -261,8 +261,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -273,7 +273,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -281,8 +281,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -301,8 +301,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/saml.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/saml.md index d0bec3788518..7d5a08ea67e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/saml.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/connect/saml.md @@ -133,6 +133,6 @@ vos utilisateurs. Voici un exemple de champs que vous devrez peut-être remplir | Option fournisseur d'identité | Valeur Centreon | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https://\ | +| Assertion Consumer Service (ACS) URL | https://\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https://\/centreon/api/latest/saml/sls | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/install.md index e8aaec64677f..cc3868d93dcf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/install.md @@ -139,7 +139,7 @@ Pour optimiser le client lourd, vous devez lui allouer plus de mémoire que la v ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/troubleshooter.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/troubleshooter.md index 3ddceedfa8c1..7aef2f2b73df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/troubleshooter.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/graph-views/troubleshooter.md @@ -147,7 +147,7 @@ Pour ouvrir les ports appropriés : /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Remplacez par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). +> Remplacez \ par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). Pour désactiver votre pare-feu, exécutez : @@ -256,7 +256,7 @@ Pour ce faire, modifiez le fichier : ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -328,7 +328,7 @@ Si elle augmente et semble atteindre une limite alors que votre CPU travaille fo ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-central-server/using-packages.md index 942a9b7385d3..4b43780f3687 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-central-server/using-packages.md @@ -535,11 +535,11 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTIO FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. +> Remplacez **\** par l'adresse IP du serveur central qui se connectera au serveur de bases de données. > -> Remplacez **** et **** par les identifiants de l'utilisateur. +> Remplacez **\** et **\** par les identifiants de l'utilisateur. -Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md/) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : +Cet utilisateur ne sera utilisé que pour le processus d'installation. Une fois [l'installation web](../web-and-post-installation.md) terminée, vous pouvez supprimer cet utilisateur via la commande suivante : ```SQL DROP USER ''@''; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-poller/using-packages.md index 5a235768ca70..937086dabbdd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-poller/using-packages.md @@ -385,10 +385,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -440,19 +440,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md index b1769a7fcab7..4b1df8a03690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md @@ -519,10 +519,10 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Remplacez **** par l'adresse IP avec laquelle le serveur Centreon +> Remplacez **\** par l'adresse IP avec laquelle le serveur Centreon > Remote Server se connectera au serveur de base de données. > -> Remplacez **** et **** par les identifiants de +> Remplacez **\** et **\** par les identifiants de > l'utilisateur. Une fois l'installation terminée, supprimez cet utilisateur via la commande : @@ -762,9 +762,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -844,19 +844,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/prerequisites.md index 6c2719a7accf..d2b7b50c093b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -152,7 +152,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -216,7 +216,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | **Serveur de bases de données** @@ -297,7 +297,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-events.md index 7637d80740ec..34dd377d77f7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-events.md @@ -152,4 +152,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md index 3bc9b8febfe5..bf4bc957183e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md @@ -155,4 +155,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-logstash-events.md index 6e54bfcb7e6f..b2086696b480 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-logstash-events.md @@ -178,6 +178,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Logstas curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -> Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. ** pourra devenir *8080*. +> Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. *\* pourra devenir *8080*. 3. Vérifiez que les données ont été reçues par Logstash. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-events.md index e3627abeaa15..db8f7443cda9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md index 4058bed7325c..8dbdc96fe011 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-mip.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-mip.md index 9f0cd0487dc0..badc1be43613 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-mip.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-mip.md @@ -2,9 +2,9 @@ id: monitoring-dem-mip title: Maltem Insight Performances Rest API --- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + ## Vue d'ensemble @@ -29,7 +29,7 @@ Afin de pouvoir interroger l'API, il est nécessaire d'avoir à disposition une ### Centreon - 1. Installer le Plugin Sur chaque collecteur se connectant à une instance MIP: @@ -41,8 +41,8 @@ yum install -y centreon-plugin-Applications-Monitoring-Mip-Restapi` ![install\_epp](../../assets/integrations/external/mip-epp-install.png) - - + + 1. Installer le Plugin Sur chaque collecteur se connectant à une instance MIP: @@ -60,7 +60,7 @@ yum install -y centreon-pack-applications-monitoring-mip-restapi` ![install\_epp](../../assets/integrations/external/mip-epp-install.png) - + ## Configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 6099d18a2253..f2323c603921 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-opsgenie.md index c03fa60b100b..f5cfd9bb77de 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-opsgenie.md @@ -187,7 +187,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-pagerduty-events.md index dddaf884d79a..0be6f8aca30a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/event-management/sc-pagerduty-events.md @@ -202,4 +202,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-bmc-remedy.md index fd68064330d3..3eb8886aeb16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-mail.md index 9dd2755aef22..79ddfa181efd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-serena.md index 963006e1b735..6ab6ff9740ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/notifications/plugin-telegram.md index 8d3f8abc7084..ea1ed0e6641c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/metrology/grafana.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/metrology/grafana.md index 6a9dcebe3525..85ba2271badf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/metrology/grafana.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/metrology/grafana.md @@ -86,5 +86,5 @@ Utilisez des [variables](https://grafana.com/docs/grafana/latest/variables/) pou Vous pouvez personnaliser l'affichage des libellés des courbes : dans la section **Time Series > Standard options**, utilisez [le champ **Display name**](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* Par exemple, si vous entrez **${__field.labels}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). -* Si vous entrez **${__field.labels.host}: ${__field.labels.metric_name}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. +* Par exemple, si vous entrez **$\{__field.labels\}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). +* Si vous entrez **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-3-4.md index 514690d7aa9c..2985bc31ce32 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-3-4.md @@ -73,15 +73,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -103,8 +103,8 @@ Centreon. 23.10 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 23.10, supprimer les bases de @@ -152,7 +152,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-debian.md index be525a847af5..9a1cf7058b72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-debian.md @@ -52,10 +52,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-el.md index 6ece3f26e1fd..5c6a35fda5de 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/migrate-from-el-to-el.md @@ -72,10 +72,10 @@ apt update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -105,8 +105,8 @@ apt update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/poller-display-to-remote-server.md index 667c70937dac..0a7ba559766e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/migrate/poller-display-to-remote-server.md @@ -58,12 +58,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -140,19 +140,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/communications.md index f2bbff14f88e..baa4536fb01a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/releases/centreon-commercial-extensions.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/releases/centreon-commercial-extensions.mdx index 9da6579e2753..dae4a854e536 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/releases/centreon-commercial-extensions.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/releases/centreon-commercial-extensions.mdx @@ -771,7 +771,7 @@ Release date: `July 4, 2024` - [Anomaly Detection] Improved ergonomics by displaying the entire window with a default screen resolution, making all buttons visible. - [Packaging] Added missing dependencies on anomaly detection. - [Packaging] Anomaly_detection perl script is now correctly deployed on Debian. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**.
                      diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/service-mapping/ba-management.md index 6b0a450cb6fc..3f413b9cf690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-23.10/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-23.10/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

                      Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                      + +

                      Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                      • Ajouté : Indique que l'objet a été ajouté
                      • Modifié : Indique que l'objet a été modifié
                        • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

                        La dernière colonne décrit la modification en elle-même :

                        + +

                        La dernière colonne décrit la modification en elle-même :

                        • Nom du champ : Décrit le champ du formulaire modifié
                        • Avant : Indique l'ancienne valeur
                          • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/parameters/ldap.md index ef7da8bf952f..e900ea2e8e45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/parameters/ldap.md @@ -106,6 +106,6 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/secure-platform.md index 78fe71af390a..b90c2b211b33 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/administration/secure-platform.md @@ -780,17 +780,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1299,7 +1299,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/notif-config-for-teams.md index cf5f94f57549..614870195836 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/resources-status.md index 5444ddb3109c..79a1df2e9332 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/resources-status.md @@ -308,7 +308,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/ticketing.md index f40063645a43..e2189dc74110 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/alerts-notifications/ticketing.md @@ -147,9 +147,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/clapi.md index c94701c88af1..e8205ec9d99d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/clapi.md @@ -998,23 +998,35 @@ ipv4: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1022,71 +1034,121 @@ ipv4:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1107,23 +1169,35 @@ ipv6: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1131,71 +1205,121 @@ ipv6:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1216,23 +1340,35 @@ file: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1240,34 +1376,60 @@ file:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          max_size

                          -

                          Maximum size of file

                          -

                          Maximum size in bytes.

                          + +

                          max_size

                          + + +

                          Maximum size of file

                          + + +

                          Maximum size in bytes.

                          +
                          -

                          path

                          -

                          File path

                          -

                          Path to the file.

                          + +

                          path

                          + + +

                          File path

                          + + +

                          Path to the file.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + @@ -1287,50 +1449,88 @@ file: -

                          config

                          -

                          Configuration messages

                          -

                          Enable or not configuration messages logging.

                          + +

                          config

                          + + +

                          Configuration messages

                          + + +

                          Enable or not configuration messages logging.

                          +
                          -

                          debug

                          -

                          Debug messages

                          -

                          Enable or not debug messages logging.

                          + +

                          debug

                          + + +

                          Debug messages

                          + + +

                          Enable or not debug messages logging.

                          +
                          -

                          error

                          -

                          Error messages

                          -

                          Enable or not error messages logging.

                          + +

                          error

                          + + +

                          Error messages

                          + + +

                          Enable or not error messages logging.

                          +
                          -

                          info

                          -

                          Informational messages

                          -

                          Enable or not informational messages logging.

                          + +

                          info

                          + + +

                          Informational messages

                          + + +

                          Enable or not informational messages logging.

                          +
                          -

                          level

                          -

                          Logging level

                          -

                          How much messages must be logged.

                          -

                          high,low,medium

                          + +

                          level

                          + + +

                          Logging level

                          + + +

                          How much messages must be logged.

                          + + +

                          high,low,medium

                          + -

                          max_size

                          -

                          name

                          -

                          Max file size in bytes

                          -

                          Name of the logger

                          -

                          The maximum size of log file.

                          -

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          + +

                          max_size

                          +

                          name

                          + + +

                          Max file size in bytes

                          +

                          Name of the logger

                          + + +

                          The maximum size of log file.

                          +

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          +
                          • @@ -1352,45 +1552,76 @@ standard: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1411,42 +1642,74 @@ syslog: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            Logging level

                            -

                            How much messages must be logged.

                            -

                            high,low,medium

                            + +

                            level

                            + + +

                            Logging level

                            + + +

                            How much messages must be logged.

                            + + +

                            high,low,medium

                            + @@ -1464,45 +1727,76 @@ monitoring: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1578,33 +1872,57 @@ rrd: -

                            buffering_timeout

                            -

                            Buffering timeout

                            -

                            Time in seconds to wait before launching failover.

                            + +

                            buffering_timeout

                            + + +

                            Buffering timeout

                            + + +

                            Time in seconds to wait before launching failover.

                            +
                            -

                            failover

                            -

                            Failover name

                            -

                            Name of the output which will act as failover

                            + +

                            failover

                            + + +

                            Failover name

                            + + +

                            Name of the output which will act as failover

                            +
                            -

                            retry_interval

                            -

                            Retry interval

                            -

                            Time in seconds to wait between each connection attempt.

                            + +

                            retry_interval

                            + + +

                            Retry interval

                            + + +

                            Time in seconds to wait between each connection attempt.

                            +
                            -

                            category

                            -

                            Filter category

                            -

                            Category filter for flux in output.

                            + +

                            category

                            + + +

                            Filter category

                            + + +

                            Category filter for flux in output.

                            +
                            • @@ -1612,15 +1930,21 @@ rrd:
                            -

                            metrics_path

                            + +

                            metrics_path

                            path

                            -

                            port

                            -

                            RRD file directory for metrics

                            +

                            port

                            + + +

                            RRD file directory for metrics

                            Unix socket

                            -

                            TCP port

                            -

                            RRD file directory, for example /var/lib/centreon/metrics

                            +

                            TCP port

                            + + +

                            RRD file directory, for example /var/lib/centreon/metrics

                            The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            -

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +
                            • @@ -1628,33 +1952,57 @@ rrd:
                            -

                            status_path

                            -

                            RRD file directory for statuses

                            -

                            RRD file directory, for example /var/lib/centreon/status

                            + +

                            status_path

                            + + +

                            RRD file directory for statuses

                            + + +

                            RRD file directory, for example /var/lib/centreon/status

                            +
                            -

                            write_metrics

                            -

                            Enable write_metrics

                            -

                            Enable or not write_metrics.

                            + +

                            write_metrics

                            + + +

                            Enable write_metrics

                            + + +

                            Enable or not write_metrics.

                            +
                            -

                            write_status

                            -

                            Enable write_status

                            -

                            Enable or not write_status.

                            + +

                            write_status

                            + + +

                            Enable write_status

                            + + +

                            Enable or not write_status.

                            +
                            -

                            store_in_data_bin

                            -

                            Enable store_in_data_bin

                            -

                            Enable or not store in performance data in data_bin.

                            + +

                            store_in_data_bin

                            + + +

                            Enable store_in_data_bin

                            + + +

                            Enable or not store in performance data in data_bin.

                            +
                            • @@ -1677,36 +2025,60 @@ storage: -

                              buffering_timeout

                              -

                              Buffering timeout

                              -

                              Time in seconds to wait before launching failover.

                              + +

                              buffering_timeout

                              + + +

                              Buffering timeout

                              + + +

                              Time in seconds to wait before launching failover.

                              +
                              -

                              failover

                              -

                              Failover name

                              -

                              Name of the output which will act as failover

                              + +

                              failover

                              + + +

                              Failover name

                              + + +

                              Name of the output which will act as failover

                              +
                              -

                              retry_interval

                              -

                              Retry interval

                              -

                              Time in seconds to wait between each connection attempt.

                              + +

                              retry_interval

                              + + +

                              Retry interval

                              + + +

                              Time in seconds to wait between each connection attempt.

                              +
                              -

                              category

                              -

                              check_replication

                              -

                              Filter category

                              -

                              Replication enabled

                              -

                              Category filter for flux in output.

                              -

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              + +

                              category

                              +

                              check_replication

                              + + +

                              Filter category

                              +

                              Replication enabled

                              + + +

                              Category filter for flux in output.

                              +

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              +
                              • @@ -1717,91 +2089,159 @@ storage:
                              -

                              db_host

                              -

                              DB host

                              -

                              IP address or hostname of the database server.

                              + +

                              db_host

                              + + +

                              DB host

                              + + +

                              IP address or hostname of the database server.

                              +
                              -

                              db_name

                              -

                              DB name

                              -

                              Database name.

                              + +

                              db_name

                              + + +

                              DB name

                              + + +

                              Database name.

                              +
                              -

                              db_password

                              -

                              DB password

                              -

                              Password of database user.

                              + +

                              db_password

                              + + +

                              DB password

                              + + +

                              Password of database user.

                              +
                              -

                              db_port

                              -

                              DB port

                              -

                              Port on which the DB server listens

                              + +

                              db_port

                              + + +

                              DB port

                              + + +

                              Port on which the DB server listens

                              +
                              -

                              db_type

                              -

                              DB type

                              -

                              Target DBMS.

                              -

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + +

                              db_type

                              + + +

                              DB type

                              + + +

                              Target DBMS.

                              + + +

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + -

                              db_user

                              -

                              DB user

                              -

                              Database user.

                              + +

                              db_user

                              + + +

                              DB user

                              + + +

                              Database user.

                              +
                              -

                              interval

                              -

                              Interval length

                              -

                              Interval length in seconds.

                              + +

                              interval

                              + + +

                              Interval length

                              + + +

                              Interval length in seconds.

                              +
                              -

                              length

                              -

                              RRD length

                              -

                              RRD storage duration in seconds.

                              + +

                              length

                              + + +

                              RRD length

                              + + +

                              RRD storage duration in seconds.

                              +
                              -

                              queries_per_transaction

                              -

                              Maximum queries per transaction

                              -

                              The maximum queries per transaction before commit.

                              + +

                              queries_per_transaction

                              + + +

                              Maximum queries per transaction

                              + + +

                              The maximum queries per transaction before commit.

                              +
                              -

                              read_timeout

                              -

                              rebuild_check_interval

                              -

                              Transaction commit timeout

                              -

                              Rebuild check interval in seconds

                              -

                              The transaction timeout before running commit.

                              -

                              The interval between check if some metrics must be rebuild. The default value is 300s

                              + +

                              read_timeout

                              +

                              rebuild_check_interval

                              + + +

                              Transaction commit timeout

                              +

                              Rebuild check interval in seconds

                              + + +

                              The transaction timeout before running commit.

                              +

                              The interval between check if some metrics must be rebuild. The default value is 300s

                              +
                              -

                              store_in_data_bin

                              -

                              Enable store_in_data_bin

                              -

                              Enable or not store in performance data in data_bin.

                              + +

                              store_in_data_bin

                              + + +

                              Enable store_in_data_bin

                              + + +

                              Enable or not store in performance data in data_bin.

                              +
                              • @@ -1824,36 +2264,60 @@ sql: -

                                buffering_timeout

                                -

                                Buffering timeout

                                -

                                Time in seconds to wait before launching failover.

                                + +

                                buffering_timeout

                                + + +

                                Buffering timeout

                                + + +

                                Time in seconds to wait before launching failover.

                                +
                                -

                                failover

                                -

                                Failover name

                                -

                                Name of the output which will act as failover

                                + +

                                failover

                                + + +

                                Failover name

                                + + +

                                Name of the output which will act as failover

                                +
                                -

                                retry_interval

                                -

                                Retry interval

                                -

                                Time in seconds to wait between each connection attempt.

                                + +

                                retry_interval

                                + + +

                                Retry interval

                                + + +

                                Time in seconds to wait between each connection attempt.

                                +
                                -

                                category

                                -

                                check_replication

                                -

                                Filter category

                                -

                                Replication enabled

                                -

                                Category filter for flux in output.

                                -

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                + +

                                category

                                +

                                check_replication

                                + + +

                                Filter category

                                +

                                Replication enabled

                                + + +

                                Category filter for flux in output.

                                +

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                +
                                • @@ -1864,63 +2328,113 @@ sql:
                                -

                                db_host

                                -

                                DB host

                                -

                                IP address or hostname of the database server.

                                + +

                                db_host

                                + + +

                                DB host

                                + + +

                                IP address or hostname of the database server.

                                +
                                -

                                db_name

                                -

                                DB name

                                -

                                Database name.

                                + +

                                db_name

                                + + +

                                DB name

                                + + +

                                Database name.

                                +
                                -

                                db_password

                                -

                                DB password

                                -

                                Password of database user.

                                + +

                                db_password

                                + + +

                                DB password

                                + + +

                                Password of database user.

                                +
                                -

                                db_port

                                -

                                DB port

                                -

                                Port on which the DB server listens

                                + +

                                db_port

                                + + +

                                DB port

                                + + +

                                Port on which the DB server listens

                                +
                                -

                                db_type

                                -

                                DB type

                                -

                                Target DBMS.

                                -

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + +

                                db_type

                                + + +

                                DB type

                                + + +

                                Target DBMS.

                                + + +

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + -

                                db_user

                                -

                                DB user

                                -

                                Database user.

                                + +

                                db_user

                                + + +

                                DB user

                                + + +

                                Database user.

                                +
                                -

                                queries_per_transaction

                                -

                                Maximum queries per transaction

                                -

                                The maximum queries per transaction before commit.

                                + +

                                queries_per_transaction

                                + + +

                                Maximum queries per transaction

                                + + +

                                The maximum queries per transaction before commit.

                                +
                                -

                                read_timeout

                                -

                                Transaction commit timeout

                                -

                                The transaction timeout before running commit.

                                + +

                                read_timeout

                                + + +

                                Transaction commit timeout

                                + + +

                                The transaction timeout before running commit.

                                +
                                diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-api.md index 58521efbe772..a44ae1c5a8c2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-api.md @@ -50,14 +50,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -71,7 +71,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -79,7 +79,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-map-api.md index 6577a73043b3..0b59b29e7553 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 24.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v1.md index 45886a15efb9..4818c3f23aae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v1.md @@ -2631,8 +2631,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v2.md index e001e3dd7174..e841715f65dc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/api/rest-api-v2.md @@ -71,12 +71,12 @@ environnements. > > Voici un exemple de résultat : > -> { +> \{ > "version": "24.04.0", > "major": "24", > "minor": "04", > "fix": "0" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/openid.md index 5de0473e0070..7fcb60c5b71b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/openid.md @@ -241,8 +241,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -253,7 +253,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -261,8 +261,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -273,7 +273,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -281,8 +281,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -301,8 +301,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/saml.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/saml.md index d0bec3788518..7d5a08ea67e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/saml.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/connect/saml.md @@ -133,6 +133,6 @@ vos utilisateurs. Voici un exemple de champs que vous devrez peut-être remplir | Option fournisseur d'identité | Valeur Centreon | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https://\ | +| Assertion Consumer Service (ACS) URL | https://\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https://\/centreon/api/latest/saml/sls | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/install.md index 2eaadd76ed26..81c539a33103 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/install.md @@ -139,7 +139,7 @@ Pour optimiser le client lourd, vous devez lui allouer plus de mémoire que la v ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/troubleshooter.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/troubleshooter.md index 3ddceedfa8c1..7aef2f2b73df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/troubleshooter.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/graph-views/troubleshooter.md @@ -147,7 +147,7 @@ Pour ouvrir les ports appropriés : /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Remplacez par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). +> Remplacez \ par le port que votre serveur Centreon MAP utilise (le plus souvent 8080, ou 8443 si vous l'avez configuré en SSL). Pour désactiver votre pare-feu, exécutez : @@ -256,7 +256,7 @@ Pour ce faire, modifiez le fichier : ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -328,7 +328,7 @@ Si elle augmente et semble atteindre une limite alors que votre CPU travaille fo ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-poller/using-packages.md index a0e75629d285..5deb8a12620f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-poller/using-packages.md @@ -384,10 +384,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -439,19 +439,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md index 8a711f72b0ac..ecd06ab6bf9f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md @@ -594,9 +594,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -676,19 +676,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/prerequisites.md index 6c2719a7accf..d2b7b50c093b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -152,7 +152,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -216,7 +216,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | **Serveur de bases de données** @@ -297,7 +297,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                • taille de la partition /var/lib/mysql * 0,6
                                • valable pour 1 sauvegarde complète et 6 partielles
                                • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-events.md index 7637d80740ec..34dd377d77f7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-events.md @@ -152,4 +152,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md index 3bc9b8febfe5..bf4bc957183e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md @@ -155,4 +155,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-logstash-events.md index d699f461980c..9c6471ec74ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-logstash-events.md @@ -153,4 +153,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *8080*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-events.md index e3627abeaa15..db8f7443cda9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md index 4058bed7325c..8dbdc96fe011 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-mip.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-mip.md index 02720c465866..ea7cebd968f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-mip.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-mip.md @@ -29,7 +29,7 @@ Afin de pouvoir interroger l'API, il est nécessaire d'avoir à disposition une ### Centreon - 1. Installer le Plugin Sur chaque collecteur se connectant à une instance MIP: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-opsgenie.md index f15658eef774..f70c2f0ca595 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-opsgenie.md @@ -187,7 +187,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-pagerduty-events.md index dddaf884d79a..0be6f8aca30a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/event-management/sc-pagerduty-events.md @@ -202,4 +202,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-bmc-remedy.md index fd68064330d3..3eb8886aeb16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-mail.md index 9dd2755aef22..79ddfa181efd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-serena.md index 963006e1b735..6ab6ff9740ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/notifications/plugin-telegram.md index 8d3f8abc7084..ea1ed0e6641c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/metrology/grafana.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/metrology/grafana.md index 6a9dcebe3525..85ba2271badf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/metrology/grafana.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/metrology/grafana.md @@ -86,5 +86,5 @@ Utilisez des [variables](https://grafana.com/docs/grafana/latest/variables/) pou Vous pouvez personnaliser l'affichage des libellés des courbes : dans la section **Time Series > Standard options**, utilisez [le champ **Display name**](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* Par exemple, si vous entrez **${__field.labels}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). -* Si vous entrez **${__field.labels.host}: ${__field.labels.metric_name}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. +* Par exemple, si vous entrez **$\{__field.labels\}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). +* Si vous entrez **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-3-4.md index f845777fa514..51df86713312 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-3-4.md @@ -72,15 +72,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -102,8 +102,8 @@ Centreon. 24.04 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 24.04, supprimer les bases de @@ -151,7 +151,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-debian.md index a29e3abf38a5..9f001850f066 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-debian.md @@ -52,10 +52,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-el.md index bf129237675a..fe9b5b5fd9e2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/migrate-from-el-to-el.md @@ -65,10 +65,10 @@ dnf update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ dnf update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/poller-display-to-remote-server.md index 03a118aef374..ffe4f213efcb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/migrate/poller-display-to-remote-server.md @@ -58,12 +58,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -140,19 +140,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/communications.md index c398b6194ea7..2138e23bfdf3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/service-mapping/ba-management.md index 6b0a450cb6fc..3f413b9cf690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.04/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.04/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

                                Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                                + +

                                Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                                • Ajouté : Indique que l'objet a été ajouté
                                • Modifié : Indique que l'objet a été modifié
                                  • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

                                  La dernière colonne décrit la modification en elle-même :

                                  + +

                                  La dernière colonne décrit la modification en elle-même :

                                  • Nom du champ : Décrit le champ du formulaire modifié
                                  • Avant : Indique l'ancienne valeur
                                    • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/parameters/ldap.md index ef7da8bf952f..e900ea2e8e45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/parameters/ldap.md @@ -106,6 +106,6 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md index 810397a51dc5..d5c5f0576c3d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md @@ -780,17 +780,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1299,7 +1299,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/notif-config-for-teams.md index bb62827f1d53..783affd78852 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/resources-status.md index 5444ddb3109c..79a1df2e9332 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/resources-status.md @@ -308,7 +308,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/ticketing.md index b258658f5586..05caed179ca9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/alerts-notifications/ticketing.md @@ -154,9 +154,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/clapi.md index c94701c88af1..e8205ec9d99d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/clapi.md @@ -998,23 +998,35 @@ ipv4: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1022,71 +1034,121 @@ ipv4:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    category

                                    -

                                    Filter category

                                    -

                                    Category filter for flux in input

                                    + +

                                    category

                                    + + +

                                    Filter category

                                    + + +

                                    Category filter for flux in input

                                    +
                                    -

                                    ca_certificate

                                    -

                                    host

                                    -

                                    Trusted CA's certificate

                                    -

                                    Host to connect to

                                    -

                                    Trusted CA's certificate.

                                    -

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    + +

                                    ca_certificate

                                    +

                                    host

                                    + + +

                                    Trusted CA's certificate

                                    +

                                    Host to connect to

                                    + + +

                                    Trusted CA's certificate.

                                    +

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    +
                                    -

                                    one_peer_retention_mode

                                    -

                                    port

                                    -

                                    One peer retention

                                    -

                                    Connection port

                                    -

                                    This allows the retention to work even if the socket is listening

                                    -

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    + +

                                    one_peer_retention_mode

                                    +

                                    port

                                    + + +

                                    One peer retention

                                    +

                                    Connection port

                                    + + +

                                    This allows the retention to work even if the socket is listening

                                    +

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    +
                                    -

                                    private_key

                                    -

                                    Private key file.

                                    -

                                    Private key file path when TLS encryption is used.

                                    + +

                                    private_key

                                    + + +

                                    Private key file.

                                    + + +

                                    Private key file path when TLS encryption is used.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + -

                                    public_cert

                                    -

                                    Public certificate

                                    -

                                    Public certificate file path when TLS encryption is used.

                                    + +

                                    public_cert

                                    + + +

                                    Public certificate

                                    + + +

                                    Public certificate file path when TLS encryption is used.

                                    +
                                    -

                                    tls

                                    -

                                    Enable TLS encryption

                                    -

                                    Enable TLS encryption.

                                    + +

                                    tls

                                    + + +

                                    Enable TLS encryption

                                    + + +

                                    Enable TLS encryption.

                                    +
                                    @@ -1107,23 +1169,35 @@ ipv6: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1131,71 +1205,121 @@ ipv6:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    category

                                    -

                                    Filter category

                                    -

                                    Category filter for flux in input

                                    + +

                                    category

                                    + + +

                                    Filter category

                                    + + +

                                    Category filter for flux in input

                                    +
                                    -

                                    ca_certificate

                                    -

                                    host

                                    -

                                    Trusted CA's certificate

                                    -

                                    Host to connect to

                                    -

                                    Trusted CA's certificate.

                                    -

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    + +

                                    ca_certificate

                                    +

                                    host

                                    + + +

                                    Trusted CA's certificate

                                    +

                                    Host to connect to

                                    + + +

                                    Trusted CA's certificate.

                                    +

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    +
                                    -

                                    one_peer_retention_mode

                                    -

                                    port

                                    -

                                    One peer retention

                                    -

                                    Connection port

                                    -

                                    This allows the retention to work even if the socket is listening

                                    -

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    + +

                                    one_peer_retention_mode

                                    +

                                    port

                                    + + +

                                    One peer retention

                                    +

                                    Connection port

                                    + + +

                                    This allows the retention to work even if the socket is listening

                                    +

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    +
                                    -

                                    private_key

                                    -

                                    Private key file.

                                    -

                                    Private key file path when TLS encryption is used.

                                    + +

                                    private_key

                                    + + +

                                    Private key file.

                                    + + +

                                    Private key file path when TLS encryption is used.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + -

                                    public_cert

                                    -

                                    Public certificate

                                    -

                                    Public certificate file path when TLS encryption is used.

                                    + +

                                    public_cert

                                    + + +

                                    Public certificate

                                    + + +

                                    Public certificate file path when TLS encryption is used.

                                    +
                                    -

                                    tls

                                    -

                                    Enable TLS encryption

                                    -

                                    Enable TLS encryption.

                                    + +

                                    tls

                                    + + +

                                    Enable TLS encryption

                                    + + +

                                    Enable TLS encryption.

                                    +
                                    @@ -1216,23 +1340,35 @@ file: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1240,34 +1376,60 @@ file:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    max_size

                                    -

                                    Maximum size of file

                                    -

                                    Maximum size in bytes.

                                    + +

                                    max_size

                                    + + +

                                    Maximum size of file

                                    + + +

                                    Maximum size in bytes.

                                    +
                                    -

                                    path

                                    -

                                    File path

                                    -

                                    Path to the file.

                                    + +

                                    path

                                    + + +

                                    File path

                                    + + +

                                    Path to the file.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + @@ -1287,50 +1449,88 @@ file: -

                                    config

                                    -

                                    Configuration messages

                                    -

                                    Enable or not configuration messages logging.

                                    + +

                                    config

                                    + + +

                                    Configuration messages

                                    + + +

                                    Enable or not configuration messages logging.

                                    +
                                    -

                                    debug

                                    -

                                    Debug messages

                                    -

                                    Enable or not debug messages logging.

                                    + +

                                    debug

                                    + + +

                                    Debug messages

                                    + + +

                                    Enable or not debug messages logging.

                                    +
                                    -

                                    error

                                    -

                                    Error messages

                                    -

                                    Enable or not error messages logging.

                                    + +

                                    error

                                    + + +

                                    Error messages

                                    + + +

                                    Enable or not error messages logging.

                                    +
                                    -

                                    info

                                    -

                                    Informational messages

                                    -

                                    Enable or not informational messages logging.

                                    + +

                                    info

                                    + + +

                                    Informational messages

                                    + + +

                                    Enable or not informational messages logging.

                                    +
                                    -

                                    level

                                    -

                                    Logging level

                                    -

                                    How much messages must be logged.

                                    -

                                    high,low,medium

                                    + +

                                    level

                                    + + +

                                    Logging level

                                    + + +

                                    How much messages must be logged.

                                    + + +

                                    high,low,medium

                                    + -

                                    max_size

                                    -

                                    name

                                    -

                                    Max file size in bytes

                                    -

                                    Name of the logger

                                    -

                                    The maximum size of log file.

                                    -

                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                    + +

                                    max_size

                                    +

                                    name

                                    + + +

                                    Max file size in bytes

                                    +

                                    Name of the logger

                                    + + +

                                    The maximum size of log file.

                                    +

                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                    +
                                    • @@ -1352,45 +1552,76 @@ standard: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      name

                                      -

                                      Logging level

                                      -

                                      Name of the logger

                                      -

                                      How much messages must be logged.

                                      -

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      +

                                      name

                                      + + +

                                      Logging level

                                      +

                                      Name of the logger

                                      + + +

                                      How much messages must be logged.

                                      +

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      + + +

                                      high,low,medium

                                      @@ -1411,42 +1642,74 @@ syslog: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      Logging level

                                      -

                                      How much messages must be logged.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      + + +

                                      Logging level

                                      + + +

                                      How much messages must be logged.

                                      + + +

                                      high,low,medium

                                      + @@ -1464,45 +1727,76 @@ monitoring: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      name

                                      -

                                      Logging level

                                      -

                                      Name of the logger

                                      -

                                      How much messages must be logged.

                                      -

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      +

                                      name

                                      + + +

                                      Logging level

                                      +

                                      Name of the logger

                                      + + +

                                      How much messages must be logged.

                                      +

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      + + +

                                      high,low,medium

                                      @@ -1578,33 +1872,57 @@ rrd: -

                                      buffering_timeout

                                      -

                                      Buffering timeout

                                      -

                                      Time in seconds to wait before launching failover.

                                      + +

                                      buffering_timeout

                                      + + +

                                      Buffering timeout

                                      + + +

                                      Time in seconds to wait before launching failover.

                                      +
                                      -

                                      failover

                                      -

                                      Failover name

                                      -

                                      Name of the output which will act as failover

                                      + +

                                      failover

                                      + + +

                                      Failover name

                                      + + +

                                      Name of the output which will act as failover

                                      +
                                      -

                                      retry_interval

                                      -

                                      Retry interval

                                      -

                                      Time in seconds to wait between each connection attempt.

                                      + +

                                      retry_interval

                                      + + +

                                      Retry interval

                                      + + +

                                      Time in seconds to wait between each connection attempt.

                                      +
                                      -

                                      category

                                      -

                                      Filter category

                                      -

                                      Category filter for flux in output.

                                      + +

                                      category

                                      + + +

                                      Filter category

                                      + + +

                                      Category filter for flux in output.

                                      +
                                      • @@ -1612,15 +1930,21 @@ rrd:
                                      -

                                      metrics_path

                                      + +

                                      metrics_path

                                      path

                                      -

                                      port

                                      -

                                      RRD file directory for metrics

                                      +

                                      port

                                      + + +

                                      RRD file directory for metrics

                                      Unix socket

                                      -

                                      TCP port

                                      -

                                      RRD file directory, for example /var/lib/centreon/metrics

                                      +

                                      TCP port

                                      + + +

                                      RRD file directory, for example /var/lib/centreon/metrics

                                      The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      -

                                      The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      +

                                      The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      +
                                      • @@ -1628,33 +1952,57 @@ rrd:
                                      -

                                      status_path

                                      -

                                      RRD file directory for statuses

                                      -

                                      RRD file directory, for example /var/lib/centreon/status

                                      + +

                                      status_path

                                      + + +

                                      RRD file directory for statuses

                                      + + +

                                      RRD file directory, for example /var/lib/centreon/status

                                      +
                                      -

                                      write_metrics

                                      -

                                      Enable write_metrics

                                      -

                                      Enable or not write_metrics.

                                      + +

                                      write_metrics

                                      + + +

                                      Enable write_metrics

                                      + + +

                                      Enable or not write_metrics.

                                      +
                                      -

                                      write_status

                                      -

                                      Enable write_status

                                      -

                                      Enable or not write_status.

                                      + +

                                      write_status

                                      + + +

                                      Enable write_status

                                      + + +

                                      Enable or not write_status.

                                      +
                                      -

                                      store_in_data_bin

                                      -

                                      Enable store_in_data_bin

                                      -

                                      Enable or not store in performance data in data_bin.

                                      + +

                                      store_in_data_bin

                                      + + +

                                      Enable store_in_data_bin

                                      + + +

                                      Enable or not store in performance data in data_bin.

                                      +
                                      • @@ -1677,36 +2025,60 @@ storage: -

                                        buffering_timeout

                                        -

                                        Buffering timeout

                                        -

                                        Time in seconds to wait before launching failover.

                                        + +

                                        buffering_timeout

                                        + + +

                                        Buffering timeout

                                        + + +

                                        Time in seconds to wait before launching failover.

                                        +
                                        -

                                        failover

                                        -

                                        Failover name

                                        -

                                        Name of the output which will act as failover

                                        + +

                                        failover

                                        + + +

                                        Failover name

                                        + + +

                                        Name of the output which will act as failover

                                        +
                                        -

                                        retry_interval

                                        -

                                        Retry interval

                                        -

                                        Time in seconds to wait between each connection attempt.

                                        + +

                                        retry_interval

                                        + + +

                                        Retry interval

                                        + + +

                                        Time in seconds to wait between each connection attempt.

                                        +
                                        -

                                        category

                                        -

                                        check_replication

                                        -

                                        Filter category

                                        -

                                        Replication enabled

                                        -

                                        Category filter for flux in output.

                                        -

                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                        + +

                                        category

                                        +

                                        check_replication

                                        + + +

                                        Filter category

                                        +

                                        Replication enabled

                                        + + +

                                        Category filter for flux in output.

                                        +

                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                        +
                                        • @@ -1717,91 +2089,159 @@ storage:
                                        -

                                        db_host

                                        -

                                        DB host

                                        -

                                        IP address or hostname of the database server.

                                        + +

                                        db_host

                                        + + +

                                        DB host

                                        + + +

                                        IP address or hostname of the database server.

                                        +
                                        -

                                        db_name

                                        -

                                        DB name

                                        -

                                        Database name.

                                        + +

                                        db_name

                                        + + +

                                        DB name

                                        + + +

                                        Database name.

                                        +
                                        -

                                        db_password

                                        -

                                        DB password

                                        -

                                        Password of database user.

                                        + +

                                        db_password

                                        + + +

                                        DB password

                                        + + +

                                        Password of database user.

                                        +
                                        -

                                        db_port

                                        -

                                        DB port

                                        -

                                        Port on which the DB server listens

                                        + +

                                        db_port

                                        + + +

                                        DB port

                                        + + +

                                        Port on which the DB server listens

                                        +
                                        -

                                        db_type

                                        -

                                        DB type

                                        -

                                        Target DBMS.

                                        -

                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                        + +

                                        db_type

                                        + + +

                                        DB type

                                        + + +

                                        Target DBMS.

                                        + + +

                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                        + -

                                        db_user

                                        -

                                        DB user

                                        -

                                        Database user.

                                        + +

                                        db_user

                                        + + +

                                        DB user

                                        + + +

                                        Database user.

                                        +
                                        -

                                        interval

                                        -

                                        Interval length

                                        -

                                        Interval length in seconds.

                                        + +

                                        interval

                                        + + +

                                        Interval length

                                        + + +

                                        Interval length in seconds.

                                        +
                                        -

                                        length

                                        -

                                        RRD length

                                        -

                                        RRD storage duration in seconds.

                                        + +

                                        length

                                        + + +

                                        RRD length

                                        + + +

                                        RRD storage duration in seconds.

                                        +
                                        -

                                        queries_per_transaction

                                        -

                                        Maximum queries per transaction

                                        -

                                        The maximum queries per transaction before commit.

                                        + +

                                        queries_per_transaction

                                        + + +

                                        Maximum queries per transaction

                                        + + +

                                        The maximum queries per transaction before commit.

                                        +
                                        -

                                        read_timeout

                                        -

                                        rebuild_check_interval

                                        -

                                        Transaction commit timeout

                                        -

                                        Rebuild check interval in seconds

                                        -

                                        The transaction timeout before running commit.

                                        -

                                        The interval between check if some metrics must be rebuild. The default value is 300s

                                        + +

                                        read_timeout

                                        +

                                        rebuild_check_interval

                                        + + +

                                        Transaction commit timeout

                                        +

                                        Rebuild check interval in seconds

                                        + + +

                                        The transaction timeout before running commit.

                                        +

                                        The interval between check if some metrics must be rebuild. The default value is 300s

                                        +
                                        -

                                        store_in_data_bin

                                        -

                                        Enable store_in_data_bin

                                        -

                                        Enable or not store in performance data in data_bin.

                                        + +

                                        store_in_data_bin

                                        + + +

                                        Enable store_in_data_bin

                                        + + +

                                        Enable or not store in performance data in data_bin.

                                        +
                                        • @@ -1824,36 +2264,60 @@ sql: -

                                          buffering_timeout

                                          -

                                          Buffering timeout

                                          -

                                          Time in seconds to wait before launching failover.

                                          + +

                                          buffering_timeout

                                          + + +

                                          Buffering timeout

                                          + + +

                                          Time in seconds to wait before launching failover.

                                          +
                                          -

                                          failover

                                          -

                                          Failover name

                                          -

                                          Name of the output which will act as failover

                                          + +

                                          failover

                                          + + +

                                          Failover name

                                          + + +

                                          Name of the output which will act as failover

                                          +
                                          -

                                          retry_interval

                                          -

                                          Retry interval

                                          -

                                          Time in seconds to wait between each connection attempt.

                                          + +

                                          retry_interval

                                          + + +

                                          Retry interval

                                          + + +

                                          Time in seconds to wait between each connection attempt.

                                          +
                                          -

                                          category

                                          -

                                          check_replication

                                          -

                                          Filter category

                                          -

                                          Replication enabled

                                          -

                                          Category filter for flux in output.

                                          -

                                          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                          + +

                                          category

                                          +

                                          check_replication

                                          + + +

                                          Filter category

                                          +

                                          Replication enabled

                                          + + +

                                          Category filter for flux in output.

                                          +

                                          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                          +
                                          • @@ -1864,63 +2328,113 @@ sql:
                                          -

                                          db_host

                                          -

                                          DB host

                                          -

                                          IP address or hostname of the database server.

                                          + +

                                          db_host

                                          + + +

                                          DB host

                                          + + +

                                          IP address or hostname of the database server.

                                          +
                                          -

                                          db_name

                                          -

                                          DB name

                                          -

                                          Database name.

                                          + +

                                          db_name

                                          + + +

                                          DB name

                                          + + +

                                          Database name.

                                          +
                                          -

                                          db_password

                                          -

                                          DB password

                                          -

                                          Password of database user.

                                          + +

                                          db_password

                                          + + +

                                          DB password

                                          + + +

                                          Password of database user.

                                          +
                                          -

                                          db_port

                                          -

                                          DB port

                                          -

                                          Port on which the DB server listens

                                          + +

                                          db_port

                                          + + +

                                          DB port

                                          + + +

                                          Port on which the DB server listens

                                          +
                                          -

                                          db_type

                                          -

                                          DB type

                                          -

                                          Target DBMS.

                                          -

                                          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                          + +

                                          db_type

                                          + + +

                                          DB type

                                          + + +

                                          Target DBMS.

                                          + + +

                                          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                          + -

                                          db_user

                                          -

                                          DB user

                                          -

                                          Database user.

                                          + +

                                          db_user

                                          + + +

                                          DB user

                                          + + +

                                          Database user.

                                          +
                                          -

                                          queries_per_transaction

                                          -

                                          Maximum queries per transaction

                                          -

                                          The maximum queries per transaction before commit.

                                          + +

                                          queries_per_transaction

                                          + + +

                                          Maximum queries per transaction

                                          + + +

                                          The maximum queries per transaction before commit.

                                          +
                                          -

                                          read_timeout

                                          -

                                          Transaction commit timeout

                                          -

                                          The transaction timeout before running commit.

                                          + +

                                          read_timeout

                                          + + +

                                          Transaction commit timeout

                                          + + +

                                          The transaction timeout before running commit.

                                          +
                                          diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/graph-views-map-api.md index bda484f71a6c..1d591c0f568a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v1.md index 45886a15efb9..4818c3f23aae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v1.md @@ -2631,8 +2631,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v2.md index 11e97acfea57..496b986ebf26 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/api/rest-api-v2.md @@ -71,12 +71,12 @@ environnements. > > Voici un exemple de résultat : > -> { +> \{ > "version": "24.10.0", > "major": "24", > "minor": "10", > "fix": "0" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/openid.md index 5de0473e0070..7fcb60c5b71b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/openid.md @@ -241,8 +241,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -253,7 +253,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -261,8 +261,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -273,7 +273,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -281,8 +281,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -301,8 +301,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/saml.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/saml.md index d0bec3788518..7d5a08ea67e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/saml.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/connect/saml.md @@ -133,6 +133,6 @@ vos utilisateurs. Voici un exemple de champs que vous devrez peut-être remplir | Option fournisseur d'identité | Valeur Centreon | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https://\ | +| Assertion Consumer Service (ACS) URL | https://\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https://\/centreon/api/latest/saml/sls | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-poller/using-packages.md index 5c4971bfc393..7aed23c79c0c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-poller/using-packages.md @@ -382,10 +382,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -437,19 +437,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md index 3fb4fb5cfeaa..b6d4409b774a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md @@ -530,9 +530,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -612,19 +612,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/prerequisites.md index 6c2719a7accf..d2b7b50c093b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                          | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                          | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                          | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                          | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -152,7 +152,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                          | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                          | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -216,7 +216,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                          | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                          | **Serveur de bases de données** @@ -297,7 +297,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                          | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                          Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                          • taille de la partition /var/lib/mysql * 0,6
                                          • valable pour 1 sauvegarde complète et 6 partielles
                                          • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                          | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-events.md index b5a0e93bdaa1..3edeb3647925 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-events.md @@ -152,4 +152,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md index f30f9e1fb6d3..d891e91ae8fd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md @@ -155,4 +155,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-logstash-events.md index 75509508ec78..9a617c8b6eda 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-logstash-events.md @@ -153,4 +153,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *8080*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-events.md index 2dd271583232..95715174b324 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md index e207fb601b24..056984190ca4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-mip.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-mip.md index 02720c465866..ea7cebd968f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-mip.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-mip.md @@ -29,7 +29,7 @@ Afin de pouvoir interroger l'API, il est nécessaire d'avoir à disposition une ### Centreon - 1. Installer le Plugin Sur chaque collecteur se connectant à une instance MIP: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-opsgenie.md index a272dbfbf6b4..f097ab244428 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-opsgenie.md @@ -187,7 +187,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-pagerduty-events.md index c1642ff2163f..fbad49212e1d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/event-management/sc-pagerduty-events.md @@ -202,4 +202,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-bmc-remedy.md index fd68064330d3..3eb8886aeb16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-mail.md index 9dd2755aef22..79ddfa181efd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-serena.md index 963006e1b735..6ab6ff9740ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/notifications/plugin-telegram.md index 8d3f8abc7084..ea1ed0e6641c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/metrology/grafana.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/metrology/grafana.md index 6a9dcebe3525..85ba2271badf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/metrology/grafana.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/metrology/grafana.md @@ -86,5 +86,5 @@ Utilisez des [variables](https://grafana.com/docs/grafana/latest/variables/) pou Vous pouvez personnaliser l'affichage des libellés des courbes : dans la section **Time Series > Standard options**, utilisez [le champ **Display name**](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* Par exemple, si vous entrez **${__field.labels}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). -* Si vous entrez **${__field.labels.host}: ${__field.labels.metric_name}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. +* Par exemple, si vous entrez **$\{__field.labels\}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). +* Si vous entrez **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-3-4.md index 03f91ef8b155..dbaea26eff34 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-3-4.md @@ -72,15 +72,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -102,8 +102,8 @@ Centreon. 24.10 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 24.10, supprimer les bases de @@ -151,7 +151,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md index 95e0cf9a1470..e3a25a1745f9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md @@ -48,10 +48,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -94,8 +94,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md index 717989a8649f..b59437b1d6e3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md @@ -52,10 +52,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md index 889ef7d8cda8..1ce0dc19324f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md @@ -65,10 +65,10 @@ dnf update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ dnf update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/poller-display-to-remote-server.md index a72669ed1bf2..53c948ce85fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/poller-display-to-remote-server.md @@ -58,12 +58,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -140,19 +140,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/communications.md index c398b6194ea7..2138e23bfdf3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/service-mapping/ba-management.md index 6b0a450cb6fc..3f413b9cf690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/logging-configuration-changes.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/logging-configuration-changes.md index 5240361b50b2..1f71f56fe80c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/logging-configuration-changes.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/logging-configuration-changes.md @@ -45,7 +45,8 @@ Le tableau ci-dessous définit les colonnes du tableau de résultats : Type de modification -

                                          Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                                          + +

                                          Contient le type d'action effectuée. Il existe plusieurs types d'actions possibles :

                                          • Ajouté : Indique que l'objet a été ajouté
                                          • Modifié : Indique que l'objet a été modifié
                                            • @@ -103,7 +104,8 @@ Le tableau ci-dessous définit les colonnes du tableau des modifications : -

                                            La dernière colonne décrit la modification en elle-même :

                                            + +

                                            La dernière colonne décrit la modification en elle-même :

                                            • Nom du champ : Décrit le champ du formulaire modifié
                                            • Avant : Indique l'ancienne valeur
                                              • diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/parameters/ldap.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/parameters/ldap.md index ef7da8bf952f..e900ea2e8e45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/parameters/ldap.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/parameters/ldap.md @@ -106,6 +106,6 @@ de type Posix. > SWA](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm) : > > - le champ **Utilisateur du domaine** est du type -> **uid=,dc=,dc=okta,dc=com** +> **uid=\,dc=\,dc=okta,dc=com** > - et le champ **Base de recherche de groupe DN** du type -> **ou=,dc=,dc=okta,dc=com** +> **ou=\,dc=\,dc=okta,dc=com** diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md index 810397a51dc5..d5c5f0576c3d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md @@ -780,17 +780,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section ****. +Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. @@ -1299,7 +1299,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md/#configure-httpstls-on-the-map-server). +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez le configurer en mode HTTPS également. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). 9. Configuration API de Gorgone diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/notif-config-for-teams.md index bb62827f1d53..783affd78852 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ Pour bénéficier des fonctionnalités du plugin, vous devez créer les objets C 1. Pour faciliter la création de ces objets, vous pouvez copier le contenu suivant issu d'un fichier CLAPI et le coller dans un fichier du répertoire /tmp de votre serveur central (par exemple /tmp/clapi-teams.import). > Avant de charger le fichier, remplacez ces valeurs par les vôtres : - - **** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. - - **** avec l'URL de Teams pour le workflow, obtenu précédemment. - - **** avec le mot de passe que vous souhaitez pour le nouveau contact. + - **\** avec l'URL que vous utilisez pour accéder à l'interface web de Centreon. + - **\** avec l'URL de Teams pour le workflow, obtenu précédemment. + - **\** avec le mot de passe que vous souhaitez pour le nouveau contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' @@ -90,7 +90,7 @@ CONTACT;setparam;notify_teams_consulting_channel;svcnotifperiod;24x7 CONTACT;setparam;notify_teams_consulting_channel;hostnotifopt;d,u CONTACT;setparam;notify_teams_consulting_channel;servicenotifopt;w,u,c CONTACT;setparam;notify_teams_consulting_channel;contact_pager; -CONTACT;setparam;notify_teams_consulting_channel;contact_address1; +CONTACT;setparam;notify_teams_consulting_channel;contact_address1;\ CONTACT;setparam;notify_teams_consulting_channel;contact_js_effects;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api;0 CONTACT;setparam;notify_teams_consulting_channel;reach_api_rt;0 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/resources-status.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/resources-status.md index 5444ddb3109c..79a1df2e9332 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/resources-status.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/resources-status.md @@ -308,7 +308,7 @@ Les graphiques affichent l'évolution des métriques sur une période donnée. L - Des sélecteurs de date et d'heure sont disponibles pour les points de début et de fin. Ils sont mis à jour lorsque la période affichée change. -- Utilisez les boutons [<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. +- Utilisez les boutons [\<] et [>] qui apparaissent sur les côtés au survol du bord du graphique pour avancer ou reculer dans le temps de la moitié de la période de temps affichée. - Sélectionnez une période dans le graphique pour zoomer sur cette période. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/ticketing.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/ticketing.md index b258658f5586..05caed179ca9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/ticketing.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/alerts-notifications/ticketing.md @@ -154,9 +154,9 @@ Le module stocke la sélection de la liste d'utilisateurs dans un tableau `mapping ticket arguments`). Il y a 3 champs (**LIST\_ID** doit être remplacé): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Règles de chaînage diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/clapi.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/clapi.md index c94701c88af1..e8205ec9d99d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/clapi.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/clapi.md @@ -998,23 +998,35 @@ ipv4: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1022,71 +1034,121 @@ ipv4:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              category

                                              -

                                              Filter category

                                              -

                                              Category filter for flux in input

                                              + +

                                              category

                                              + + +

                                              Filter category

                                              + + +

                                              Category filter for flux in input

                                              +
                                              -

                                              ca_certificate

                                              -

                                              host

                                              -

                                              Trusted CA's certificate

                                              -

                                              Host to connect to

                                              -

                                              Trusted CA's certificate.

                                              -

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              + +

                                              ca_certificate

                                              +

                                              host

                                              + + +

                                              Trusted CA's certificate

                                              +

                                              Host to connect to

                                              + + +

                                              Trusted CA's certificate.

                                              +

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              +
                                              -

                                              one_peer_retention_mode

                                              -

                                              port

                                              -

                                              One peer retention

                                              -

                                              Connection port

                                              -

                                              This allows the retention to work even if the socket is listening

                                              -

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              + +

                                              one_peer_retention_mode

                                              +

                                              port

                                              + + +

                                              One peer retention

                                              +

                                              Connection port

                                              + + +

                                              This allows the retention to work even if the socket is listening

                                              +

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              +
                                              -

                                              private_key

                                              -

                                              Private key file.

                                              -

                                              Private key file path when TLS encryption is used.

                                              + +

                                              private_key

                                              + + +

                                              Private key file.

                                              + + +

                                              Private key file path when TLS encryption is used.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + -

                                              public_cert

                                              -

                                              Public certificate

                                              -

                                              Public certificate file path when TLS encryption is used.

                                              + +

                                              public_cert

                                              + + +

                                              Public certificate

                                              + + +

                                              Public certificate file path when TLS encryption is used.

                                              +
                                              -

                                              tls

                                              -

                                              Enable TLS encryption

                                              -

                                              Enable TLS encryption.

                                              + +

                                              tls

                                              + + +

                                              Enable TLS encryption

                                              + + +

                                              Enable TLS encryption.

                                              +
                                              @@ -1107,23 +1169,35 @@ ipv6: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1131,71 +1205,121 @@ ipv6:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              category

                                              -

                                              Filter category

                                              -

                                              Category filter for flux in input

                                              + +

                                              category

                                              + + +

                                              Filter category

                                              + + +

                                              Category filter for flux in input

                                              +
                                              -

                                              ca_certificate

                                              -

                                              host

                                              -

                                              Trusted CA's certificate

                                              -

                                              Host to connect to

                                              -

                                              Trusted CA's certificate.

                                              -

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              + +

                                              ca_certificate

                                              +

                                              host

                                              + + +

                                              Trusted CA's certificate

                                              +

                                              Host to connect to

                                              + + +

                                              Trusted CA's certificate.

                                              +

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              +
                                              -

                                              one_peer_retention_mode

                                              -

                                              port

                                              -

                                              One peer retention

                                              -

                                              Connection port

                                              -

                                              This allows the retention to work even if the socket is listening

                                              -

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              + +

                                              one_peer_retention_mode

                                              +

                                              port

                                              + + +

                                              One peer retention

                                              +

                                              Connection port

                                              + + +

                                              This allows the retention to work even if the socket is listening

                                              +

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              +
                                              -

                                              private_key

                                              -

                                              Private key file.

                                              -

                                              Private key file path when TLS encryption is used.

                                              + +

                                              private_key

                                              + + +

                                              Private key file.

                                              + + +

                                              Private key file path when TLS encryption is used.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + -

                                              public_cert

                                              -

                                              Public certificate

                                              -

                                              Public certificate file path when TLS encryption is used.

                                              + +

                                              public_cert

                                              + + +

                                              Public certificate

                                              + + +

                                              Public certificate file path when TLS encryption is used.

                                              +
                                              -

                                              tls

                                              -

                                              Enable TLS encryption

                                              -

                                              Enable TLS encryption.

                                              + +

                                              tls

                                              + + +

                                              Enable TLS encryption

                                              + + +

                                              Enable TLS encryption.

                                              +
                                              @@ -1216,23 +1340,35 @@ file: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1240,34 +1376,60 @@ file:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              max_size

                                              -

                                              Maximum size of file

                                              -

                                              Maximum size in bytes.

                                              + +

                                              max_size

                                              + + +

                                              Maximum size of file

                                              + + +

                                              Maximum size in bytes.

                                              +
                                              -

                                              path

                                              -

                                              File path

                                              -

                                              Path to the file.

                                              + +

                                              path

                                              + + +

                                              File path

                                              + + +

                                              Path to the file.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + @@ -1287,50 +1449,88 @@ file: -

                                              config

                                              -

                                              Configuration messages

                                              -

                                              Enable or not configuration messages logging.

                                              + +

                                              config

                                              + + +

                                              Configuration messages

                                              + + +

                                              Enable or not configuration messages logging.

                                              +
                                              -

                                              debug

                                              -

                                              Debug messages

                                              -

                                              Enable or not debug messages logging.

                                              + +

                                              debug

                                              + + +

                                              Debug messages

                                              + + +

                                              Enable or not debug messages logging.

                                              +
                                              -

                                              error

                                              -

                                              Error messages

                                              -

                                              Enable or not error messages logging.

                                              + +

                                              error

                                              + + +

                                              Error messages

                                              + + +

                                              Enable or not error messages logging.

                                              +
                                              -

                                              info

                                              -

                                              Informational messages

                                              -

                                              Enable or not informational messages logging.

                                              + +

                                              info

                                              + + +

                                              Informational messages

                                              + + +

                                              Enable or not informational messages logging.

                                              +
                                              -

                                              level

                                              -

                                              Logging level

                                              -

                                              How much messages must be logged.

                                              -

                                              high,low,medium

                                              + +

                                              level

                                              + + +

                                              Logging level

                                              + + +

                                              How much messages must be logged.

                                              + + +

                                              high,low,medium

                                              + -

                                              max_size

                                              -

                                              name

                                              -

                                              Max file size in bytes

                                              -

                                              Name of the logger

                                              -

                                              The maximum size of log file.

                                              -

                                              For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                              + +

                                              max_size

                                              +

                                              name

                                              + + +

                                              Max file size in bytes

                                              +

                                              Name of the logger

                                              + + +

                                              The maximum size of log file.

                                              +

                                              For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                              +
                                              • @@ -1352,45 +1552,76 @@ standard: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                name

                                                -

                                                Logging level

                                                -

                                                Name of the logger

                                                -

                                                How much messages must be logged.

                                                -

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                +

                                                name

                                                + + +

                                                Logging level

                                                +

                                                Name of the logger

                                                + + +

                                                How much messages must be logged.

                                                +

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                + + +

                                                high,low,medium

                                                @@ -1411,42 +1642,74 @@ syslog: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                Logging level

                                                -

                                                How much messages must be logged.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                + + +

                                                Logging level

                                                + + +

                                                How much messages must be logged.

                                                + + +

                                                high,low,medium

                                                + @@ -1464,45 +1727,76 @@ monitoring: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                name

                                                -

                                                Logging level

                                                -

                                                Name of the logger

                                                -

                                                How much messages must be logged.

                                                -

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                +

                                                name

                                                + + +

                                                Logging level

                                                +

                                                Name of the logger

                                                + + +

                                                How much messages must be logged.

                                                +

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                + + +

                                                high,low,medium

                                                @@ -1578,33 +1872,57 @@ rrd: -

                                                buffering_timeout

                                                -

                                                Buffering timeout

                                                -

                                                Time in seconds to wait before launching failover.

                                                + +

                                                buffering_timeout

                                                + + +

                                                Buffering timeout

                                                + + +

                                                Time in seconds to wait before launching failover.

                                                +
                                                -

                                                failover

                                                -

                                                Failover name

                                                -

                                                Name of the output which will act as failover

                                                + +

                                                failover

                                                + + +

                                                Failover name

                                                + + +

                                                Name of the output which will act as failover

                                                +
                                                -

                                                retry_interval

                                                -

                                                Retry interval

                                                -

                                                Time in seconds to wait between each connection attempt.

                                                + +

                                                retry_interval

                                                + + +

                                                Retry interval

                                                + + +

                                                Time in seconds to wait between each connection attempt.

                                                +
                                                -

                                                category

                                                -

                                                Filter category

                                                -

                                                Category filter for flux in output.

                                                + +

                                                category

                                                + + +

                                                Filter category

                                                + + +

                                                Category filter for flux in output.

                                                +
                                                • @@ -1612,15 +1930,21 @@ rrd:
                                                -

                                                metrics_path

                                                + +

                                                metrics_path

                                                path

                                                -

                                                port

                                                -

                                                RRD file directory for metrics

                                                +

                                                port

                                                + + +

                                                RRD file directory for metrics

                                                Unix socket

                                                -

                                                TCP port

                                                -

                                                RRD file directory, for example /var/lib/centreon/metrics

                                                +

                                                TCP port

                                                + + +

                                                RRD file directory, for example /var/lib/centreon/metrics

                                                The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                -

                                                The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                +

                                                The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                +
                                                • @@ -1628,33 +1952,57 @@ rrd:
                                                -

                                                status_path

                                                -

                                                RRD file directory for statuses

                                                -

                                                RRD file directory, for example /var/lib/centreon/status

                                                + +

                                                status_path

                                                + + +

                                                RRD file directory for statuses

                                                + + +

                                                RRD file directory, for example /var/lib/centreon/status

                                                +
                                                -

                                                write_metrics

                                                -

                                                Enable write_metrics

                                                -

                                                Enable or not write_metrics.

                                                + +

                                                write_metrics

                                                + + +

                                                Enable write_metrics

                                                + + +

                                                Enable or not write_metrics.

                                                +
                                                -

                                                write_status

                                                -

                                                Enable write_status

                                                -

                                                Enable or not write_status.

                                                + +

                                                write_status

                                                + + +

                                                Enable write_status

                                                + + +

                                                Enable or not write_status.

                                                +
                                                -

                                                store_in_data_bin

                                                -

                                                Enable store_in_data_bin

                                                -

                                                Enable or not store in performance data in data_bin.

                                                + +

                                                store_in_data_bin

                                                + + +

                                                Enable store_in_data_bin

                                                + + +

                                                Enable or not store in performance data in data_bin.

                                                +
                                                • @@ -1677,36 +2025,60 @@ storage: -

                                                  buffering_timeout

                                                  -

                                                  Buffering timeout

                                                  -

                                                  Time in seconds to wait before launching failover.

                                                  + +

                                                  buffering_timeout

                                                  + + +

                                                  Buffering timeout

                                                  + + +

                                                  Time in seconds to wait before launching failover.

                                                  +
                                                  -

                                                  failover

                                                  -

                                                  Failover name

                                                  -

                                                  Name of the output which will act as failover

                                                  + +

                                                  failover

                                                  + + +

                                                  Failover name

                                                  + + +

                                                  Name of the output which will act as failover

                                                  +
                                                  -

                                                  retry_interval

                                                  -

                                                  Retry interval

                                                  -

                                                  Time in seconds to wait between each connection attempt.

                                                  + +

                                                  retry_interval

                                                  + + +

                                                  Retry interval

                                                  + + +

                                                  Time in seconds to wait between each connection attempt.

                                                  +
                                                  -

                                                  category

                                                  -

                                                  check_replication

                                                  -

                                                  Filter category

                                                  -

                                                  Replication enabled

                                                  -

                                                  Category filter for flux in output.

                                                  -

                                                  When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                  + +

                                                  category

                                                  +

                                                  check_replication

                                                  + + +

                                                  Filter category

                                                  +

                                                  Replication enabled

                                                  + + +

                                                  Category filter for flux in output.

                                                  +

                                                  When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                  +
                                                  • @@ -1717,91 +2089,159 @@ storage:
                                                  -

                                                  db_host

                                                  -

                                                  DB host

                                                  -

                                                  IP address or hostname of the database server.

                                                  + +

                                                  db_host

                                                  + + +

                                                  DB host

                                                  + + +

                                                  IP address or hostname of the database server.

                                                  +
                                                  -

                                                  db_name

                                                  -

                                                  DB name

                                                  -

                                                  Database name.

                                                  + +

                                                  db_name

                                                  + + +

                                                  DB name

                                                  + + +

                                                  Database name.

                                                  +
                                                  -

                                                  db_password

                                                  -

                                                  DB password

                                                  -

                                                  Password of database user.

                                                  + +

                                                  db_password

                                                  + + +

                                                  DB password

                                                  + + +

                                                  Password of database user.

                                                  +
                                                  -

                                                  db_port

                                                  -

                                                  DB port

                                                  -

                                                  Port on which the DB server listens

                                                  + +

                                                  db_port

                                                  + + +

                                                  DB port

                                                  + + +

                                                  Port on which the DB server listens

                                                  +
                                                  -

                                                  db_type

                                                  -

                                                  DB type

                                                  -

                                                  Target DBMS.

                                                  -

                                                  db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                  + +

                                                  db_type

                                                  + + +

                                                  DB type

                                                  + + +

                                                  Target DBMS.

                                                  + + +

                                                  db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                  + -

                                                  db_user

                                                  -

                                                  DB user

                                                  -

                                                  Database user.

                                                  + +

                                                  db_user

                                                  + + +

                                                  DB user

                                                  + + +

                                                  Database user.

                                                  +
                                                  -

                                                  interval

                                                  -

                                                  Interval length

                                                  -

                                                  Interval length in seconds.

                                                  + +

                                                  interval

                                                  + + +

                                                  Interval length

                                                  + + +

                                                  Interval length in seconds.

                                                  +
                                                  -

                                                  length

                                                  -

                                                  RRD length

                                                  -

                                                  RRD storage duration in seconds.

                                                  + +

                                                  length

                                                  + + +

                                                  RRD length

                                                  + + +

                                                  RRD storage duration in seconds.

                                                  +
                                                  -

                                                  queries_per_transaction

                                                  -

                                                  Maximum queries per transaction

                                                  -

                                                  The maximum queries per transaction before commit.

                                                  + +

                                                  queries_per_transaction

                                                  + + +

                                                  Maximum queries per transaction

                                                  + + +

                                                  The maximum queries per transaction before commit.

                                                  +
                                                  -

                                                  read_timeout

                                                  -

                                                  rebuild_check_interval

                                                  -

                                                  Transaction commit timeout

                                                  -

                                                  Rebuild check interval in seconds

                                                  -

                                                  The transaction timeout before running commit.

                                                  -

                                                  The interval between check if some metrics must be rebuild. The default value is 300s

                                                  + +

                                                  read_timeout

                                                  +

                                                  rebuild_check_interval

                                                  + + +

                                                  Transaction commit timeout

                                                  +

                                                  Rebuild check interval in seconds

                                                  + + +

                                                  The transaction timeout before running commit.

                                                  +

                                                  The interval between check if some metrics must be rebuild. The default value is 300s

                                                  +
                                                  -

                                                  store_in_data_bin

                                                  -

                                                  Enable store_in_data_bin

                                                  -

                                                  Enable or not store in performance data in data_bin.

                                                  + +

                                                  store_in_data_bin

                                                  + + +

                                                  Enable store_in_data_bin

                                                  + + +

                                                  Enable or not store in performance data in data_bin.

                                                  +
                                                  • @@ -1824,36 +2264,60 @@ sql: -

                                                    buffering_timeout

                                                    -

                                                    Buffering timeout

                                                    -

                                                    Time in seconds to wait before launching failover.

                                                    + +

                                                    buffering_timeout

                                                    + + +

                                                    Buffering timeout

                                                    + + +

                                                    Time in seconds to wait before launching failover.

                                                    +
                                                    -

                                                    failover

                                                    -

                                                    Failover name

                                                    -

                                                    Name of the output which will act as failover

                                                    + +

                                                    failover

                                                    + + +

                                                    Failover name

                                                    + + +

                                                    Name of the output which will act as failover

                                                    +
                                                    -

                                                    retry_interval

                                                    -

                                                    Retry interval

                                                    -

                                                    Time in seconds to wait between each connection attempt.

                                                    + +

                                                    retry_interval

                                                    + + +

                                                    Retry interval

                                                    + + +

                                                    Time in seconds to wait between each connection attempt.

                                                    +
                                                    -

                                                    category

                                                    -

                                                    check_replication

                                                    -

                                                    Filter category

                                                    -

                                                    Replication enabled

                                                    -

                                                    Category filter for flux in output.

                                                    -

                                                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                    + +

                                                    category

                                                    +

                                                    check_replication

                                                    + + +

                                                    Filter category

                                                    +

                                                    Replication enabled

                                                    + + +

                                                    Category filter for flux in output.

                                                    +

                                                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                    +
                                                    • @@ -1864,63 +2328,113 @@ sql:
                                                    -

                                                    db_host

                                                    -

                                                    DB host

                                                    -

                                                    IP address or hostname of the database server.

                                                    + +

                                                    db_host

                                                    + + +

                                                    DB host

                                                    + + +

                                                    IP address or hostname of the database server.

                                                    +
                                                    -

                                                    db_name

                                                    -

                                                    DB name

                                                    -

                                                    Database name.

                                                    + +

                                                    db_name

                                                    + + +

                                                    DB name

                                                    + + +

                                                    Database name.

                                                    +
                                                    -

                                                    db_password

                                                    -

                                                    DB password

                                                    -

                                                    Password of database user.

                                                    + +

                                                    db_password

                                                    + + +

                                                    DB password

                                                    + + +

                                                    Password of database user.

                                                    +
                                                    -

                                                    db_port

                                                    -

                                                    DB port

                                                    -

                                                    Port on which the DB server listens

                                                    + +

                                                    db_port

                                                    + + +

                                                    DB port

                                                    + + +

                                                    Port on which the DB server listens

                                                    +
                                                    -

                                                    db_type

                                                    -

                                                    DB type

                                                    -

                                                    Target DBMS.

                                                    -

                                                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                    + +

                                                    db_type

                                                    + + +

                                                    DB type

                                                    + + +

                                                    Target DBMS.

                                                    + + +

                                                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                    + -

                                                    db_user

                                                    -

                                                    DB user

                                                    -

                                                    Database user.

                                                    + +

                                                    db_user

                                                    + + +

                                                    DB user

                                                    + + +

                                                    Database user.

                                                    +
                                                    -

                                                    queries_per_transaction

                                                    -

                                                    Maximum queries per transaction

                                                    -

                                                    The maximum queries per transaction before commit.

                                                    + +

                                                    queries_per_transaction

                                                    + + +

                                                    Maximum queries per transaction

                                                    + + +

                                                    The maximum queries per transaction before commit.

                                                    +
                                                    -

                                                    read_timeout

                                                    -

                                                    Transaction commit timeout

                                                    -

                                                    The transaction timeout before running commit.

                                                    + +

                                                    read_timeout

                                                    + + +

                                                    Transaction commit timeout

                                                    + + +

                                                    The transaction timeout before running commit.

                                                    +
                                                    diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/graph-views-map-api.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/graph-views-map-api.md index bda484f71a6c..1d591c0f568a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/graph-views-map-api.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/graph-views-map-api.md @@ -34,13 +34,13 @@ Body { } ``` -- Dans le résultat, récupérez le {jwtToken}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : +- Dans le résultat, récupérez le \{jwtToken\}. Vous devrez l'utiliser pour tous vos appels à l'API. Les headers ressembleront à ceci : ``` Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -54,7 +54,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -62,7 +62,7 @@ Body { } ``` -- Récupérez l'identifiant de la carte {mapId} et de la vue {viewId} renvoyés. +- Récupérez l'identifiant de la carte \{mapId\} et de la vue \{viewId\} renvoyés. ### Ouvrir la carte @@ -80,7 +80,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v1.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v1.md index 45886a15efb9..4818c3f23aae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v1.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v1.md @@ -2631,8 +2631,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v2.md index 11e97acfea57..496b986ebf26 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/api/rest-api-v2.md @@ -71,12 +71,12 @@ environnements. > > Voici un exemple de résultat : > -> { +> \{ > "version": "24.10.0", > "major": "24", > "minor": "10", > "fix": "0" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/openid.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/openid.md index 5de0473e0070..7fcb60c5b71b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/openid.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/openid.md @@ -241,8 +241,8 @@ Voici un exemple de configuration pour Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${tenantId}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -253,7 +253,7 @@ Voici un exemple de configuration pour Okta: | Champs | Valeurs | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -261,8 +261,8 @@ Voici un exemple de configuration pour Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -273,7 +273,7 @@ Voici un exemple de configuration pour Keycloak: | Champs | Valeurs | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -281,8 +281,8 @@ Voici un exemple de configuration pour Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `${theIdPdomain}`, `${clientId}` et `${clientSecret}` par vos propres valeurs. @@ -301,8 +301,8 @@ Voici un exemple de configuration pour LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | \{clientId\} | +| Client Secret | \{clientSecret\} | > Remplacez `auth.example.com`, `${clientId}` et `${clientSecret}` par vos propres valeurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/saml.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/saml.md index d0bec3788518..7d5a08ea67e5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/saml.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/connect/saml.md @@ -133,6 +133,6 @@ vos utilisateurs. Voici un exemple de champs que vous devrez peut-être remplir | Option fournisseur d'identité | Valeur Centreon | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https://\ | +| Assertion Consumer Service (ACS) URL | https://\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https://\/centreon/api/latest/saml/sls | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-gorgone-client-server-communication.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-gorgone-client-server-communication.md index a974e7fd2aff..e53bb325ff72 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-gorgone-client-server-communication.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-gorgone-client-server-communication.md @@ -31,7 +31,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/**). +Copiez la clé publique du serveur dans un répertoire spécifique côté client (par exemple **/var/spool/centreon/.gorgone/\**). ## Récupérer l'empreinte au format JWK diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-widget.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-widget.md index d0928c7d868e..2f4738735230 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-widget.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/developer/developer-widget.md @@ -18,7 +18,7 @@ Bien sûr, vous pourriez créer un widget qui ne fonctionnerait qu’avec un mod Les widgets fonctionnent à peu près comme les modules. Ils doivent être placés dans le répertoire suivant : ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Votre widget doit contenir un fichier obligatoire nommé **configs.xml** à sa racine. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/getting-started/model-it-services.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/getting-started/model-it-services.md index 70f7b3225903..b49bac89c5b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/getting-started/model-it-services.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/getting-started/model-it-services.md @@ -65,7 +65,7 @@ y a quatre méthodes de calcul disponible afin de rendre compte de l'état d'une - **Worst Status**: Lorsque vous souhaitez savoir dès qu'un indicateur ne fonctionne plus - **Ratio**: Lorsque vous souhaitez modéliser des concepts de **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez -- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (<=> sévérité) +- **Impact**: Lorsque vous souhaitez définir finement l'impact de chaque indicateur en fonction de leurs poids (\<=\> sévérité) Pour plus d'information sur les méthodes de calcul, consulter [ce chapitre](../service-mapping/ba-management.md#méthodes-de-calcul) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-poller/using-packages.md index 5c4971bfc393..7aed23c79c0c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-poller/using-packages.md @@ -382,10 +382,10 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Remplacez **** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le +> Remplacez **\** par l'adresse IP du serveur Central ou du serveur distant auquel vous voulez rattacher le collecteur (adresse IP vue par le > collecteur). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -437,19 +437,19 @@ Vous recevrez la validation du serveur Centreon central ou du serveur Remote Ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md index 3fb4fb5cfeaa..b6d4409b774a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md @@ -530,9 +530,9 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacez **** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). +> Remplacez **\** par l'adresse IP du serveur Central auquel vous voulez rattacher le serveur distant (adresse IP vue par le serveur distant). -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Pour changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : > `HTTPS://:PORT` @@ -612,19 +612,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/prerequisites.md index 6c2719a7accf..d2b7b50c093b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/installation/prerequisites.md @@ -54,7 +54,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 5 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 106 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                                    | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                                    | | vg_data || Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -88,7 +88,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 10 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 213 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                                    | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                                    | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -152,7 +152,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 25 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/lib/mysql (seulement si le SGBD est situé sur le serveur central) | base de données | 538 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                                    | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                                    | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. @@ -216,7 +216,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 339 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                                    | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                                    | **Serveur de bases de données** @@ -297,7 +297,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | -| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go

                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :

                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain

                                                    | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
                                                    Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
                                                    • taille de la partition /var/lib/mysql * 0,6
                                                    • valable pour 1 sauvegarde complète et 6 partielles
                                                    • attention, cela reste une estimation et n'exclut pas un contrôle humain
                                                    | > Votre système doit utiliser LVM pour gérer vos partitions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-events.md index b5a0e93bdaa1..3edeb3647925 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-events.md @@ -152,4 +152,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md index f30f9e1fb6d3..d891e91ae8fd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md @@ -155,4 +155,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *https://api.datadoghq.com*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md index eab94fd9809a..4c9fa888d78a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -175,6 +175,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à InfluxD curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *65f5f748e28c92f0*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *65f5f748e28c92f0*. 3. Vérifiez que l'évènement a bien été reçu par InfluxDB 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-logstash-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-logstash-events.md index 75509508ec78..9a617c8b6eda 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-logstash-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-logstash-events.md @@ -153,4 +153,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *8080*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-events.md index 2dd271583232..95715174b324 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-events.md @@ -196,6 +196,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md index e207fb601b24..056984190ca4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md @@ -194,6 +194,6 @@ Si vous voulez tester que les évènements sont envoyés correctement à Splunk curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, ** pourra être remplacé par *_json*. + > Remplacez tous les *``* dans la commande ci-dessus par la valeur correcte. Par exemple, *\* pourra être remplacé par *_json*. 3. Vérifiez que l'évènement a bien été reçu par Splunk. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-mip.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-mip.md index 02720c465866..ea7cebd968f1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-mip.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-mip.md @@ -29,7 +29,7 @@ Afin de pouvoir interroger l'API, il est nécessaire d'avoir à disposition une ### Centreon - 1. Installer le Plugin Sur chaque collecteur se connectant à une instance MIP: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/digital-experience-monitoring/connector-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-opsgenie.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-opsgenie.md index a272dbfbf6b4..f097ab244428 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-opsgenie.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-opsgenie.md @@ -187,7 +187,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : {hostname}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : {last_update} est une macro sous la forme d'un timestamp. Vous pouvez utiliser {last_update_date} pour la convertir) +Les macros sont un outil pour créer des messages dynamiques dépendant de l'évènement que vous envoyez. Elles doivent être mises entre {} (ex : \{hostname\}). Si une macro est une macro de type *time* alors vous pouvez utiliser le suffixe **\_date** pour le convertir en un format lisible pour l'Homme. Vous pouvez changer le format de la date avec le paramètre de type string `date_format`. (ex : \{last_update\} est une macro sous la forme d'un timestamp. Vous pouvez utiliser \{last_update_date\} pour la convertir) #### Host event macros diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-pagerduty-events.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-pagerduty-events.md index c1642ff2163f..fbad49212e1d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-pagerduty-events.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/event-management/sc-pagerduty-events.md @@ -202,4 +202,4 @@ Here is the list of all the curl commands that are used by the stream connector. curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. +You must replace all the *``* inside the above command with their appropriate value. *\* may become *linuxServerA*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-bmc-remedy.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-bmc-remedy.md index fd68064330d3..3eb8886aeb16 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-bmc-remedy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-mail.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-mail.md index 9dd2755aef22..79ddfa181efd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-mail.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-serena.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-serena.md index 963006e1b735..6ab6ff9740ea 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-serena.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/notifications/plugin-telegram.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/notifications/plugin-telegram.md index 8d3f8abc7084..ea1ed0e6641c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/notifications/plugin-telegram.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/stream-connectors.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/stream-connectors.md index 0dc174918a4b..241818206059 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/stream-connectors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Les stream connectors ont pour but de transmettre en temps réel le flux des données issu de la supervision par la plateforme Centreon vers un outil tiers. Ce flux peut porter sur les évènements comme sur les métriques. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/metrology/grafana.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/metrology/grafana.md index 6a9dcebe3525..85ba2271badf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/metrology/grafana.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/metrology/grafana.md @@ -86,5 +86,5 @@ Utilisez des [variables](https://grafana.com/docs/grafana/latest/variables/) pou Vous pouvez personnaliser l'affichage des libellés des courbes : dans la section **Time Series > Standard options**, utilisez [le champ **Display name**](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* Par exemple, si vous entrez **${__field.labels}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). -* Si vous entrez **${__field.labels.host}: ${__field.labels.metric_name}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. +* Par exemple, si vous entrez **$\{__field.labels\}**, le libellé inclura toutes les options de personnalisation possibles (host, service, metric_name). +* Si vous entrez **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, le libellé d'une courbe sera affiché de cette manière : **10.11.12.13: total_cpu_avg**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-3-4.md index 03f91ef8b155..dbaea26eff34 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-3-4.md @@ -72,15 +72,15 @@ Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires suivants : ```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon +rsync -avz /etc/centreon root@\:/etc +rsync -avz /etc/centreon-broker root@\:/etc +rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine +rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib +rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Récupération des bases de données @@ -102,8 +102,8 @@ Centreon. 24.10 : ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le serveur de base de données Centreon 24.10, supprimer les bases de @@ -151,7 +151,7 @@ données vierges et les recréer : systemctl start mariadb ``` -> Remplacez **** par l'adresse IP de votre nouveau serveur +> Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. ### Synchronisation des plugins diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md index 717989a8649f..b59437b1d6e3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md @@ -52,10 +52,10 @@ apt update && apt upgrade 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ apt update && apt upgrade 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md index 889ef7d8cda8..1ce0dc19324f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md @@ -65,10 +65,10 @@ dnf update 4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : ```shell - rsync -avz /etc/centreon root@:/etc - rsync -avz /etc/centreon-broker root@:/etc - rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` @@ -98,8 +98,8 @@ dnf update 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` 4. Sur le nouveau serveur de base de données, supprimez les bases de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/poller-display-to-remote-server.md index a72669ed1bf2..53c948ce85fc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/poller-display-to-remote-server.md @@ -58,12 +58,12 @@ Exemple: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Remplacer **** par l'adresse IP du serveur Centreon Central vue par votre collecteur. +> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. -> Le compte **** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. +> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. > Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://:PORT +> HTTPS://\:PORT Suivre ensuite les instructions @@ -140,19 +140,19 @@ Vous recevrez la validation du serveur Centreon Central : 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Vos informations d'identification sont incorrectes pour le compte ****. +> Vos informations d'identification sont incorrectes pour le compte **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> L'utilisateur **** n'a pas accès à l'API de configuration. +> L'utilisateur **\** n'a pas accès à l'API de configuration. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Impossible d'accéder à l'API. Contrôler les valeurs ****, méthode et port. +> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 8a4ca0ecba74..e54ab442af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -77,7 +77,7 @@ sélectionnez votre serveur, puis saisissez les informations demandées : systemctl restart cbd ``` - Si besoin, consultez **/var/log/centreon-broker/.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) + Si besoin, consultez **/var/log/centreon-broker/\.log** pour identifier des erreurs. (Dans l'exemple ci-dessus, il s'agit du fichier **/var/log/centreon-broker/remote-server.log**.) ## Étape 2 : Activer la communication diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/communications.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/communications.md index c398b6194ea7..2138e23bfdf3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/communications.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Les modes de communication sont listés ci-après : | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | -------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | @@ -52,28 +52,28 @@ exporter la configuration. | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker, Host Discovery | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Actions de supervision\*, collecte des statistiques Engine/Broker (seulement Remote), Host Discovery (seulement Remote) | | Communications | Actions autorisées | | ----------------------------------------------------------------- | ------------------------ | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Actions de supervision\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Actions de supervision\* | > Ce mode ne permet pas de récupérer l'empreinte du Remote et rend donc > impossible l'affichage de la configuration du Gorgone du Poller depuis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 127092203f33..19ff0aff5dfb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Rendez-vous dans le menu **Configuration > SNMP traps > SNMP traps** et cliquez > Il est possible de construire soit même le message de sortie. Pour cela, utilisez la MIB afin de connaitre les > arguments qui seront présents dans le corps de l’évènement et récupérer les arguments avec les variables **$n**. > Chaque argument étant identifié par un OID, il est possible d’utiliser directement cet OID afin de le placer dans le -> message de sortie sans connaitre sa position via la variable **@{OID}**.. +> message de sortie sans connaitre sa position via la variable **@\{OID\}**.. * Le champ **Default status** définit le statut "supervision" par défaut du service en cas de réception du trap. * Si la case **Submit result** est cochée alors le résultat est soumis au moteur de supervision. @@ -120,7 +120,7 @@ La commande suivante permet de récupérer cette valeur : snmpget -v 2c -Ovq -c ifAlias.$1 ``` -Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p{n} où ‘n’ +Pour utiliser le résultat de la commande PREEXEC dans le **Output message**, il faut utiliser la variable $p\{n\} où ‘n’ correspond à l’ordre de définition de la commande. Exemple : @@ -174,7 +174,7 @@ arguments aux champs **String** ou **Special command**. Ces arguments sont list | Nom de la variable | Description | |--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Récupération de la valeur d’un argument via son OID, exemple @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Récupération de la valeur d’un argument via son OID, exemple @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Récupération de la valeur d’un argument via son ordre d’apparition | | $p1, $p2,... | VValeur de la commande PREEXEC ($p1 = pour la première commande, $p2 pour la seconde, ...) | | $* | Tous les arguments séparés par un espace | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/reporting/reports_publication_rule.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/reporting/reports_publication_rule.md index 09703e08fa5f..0c78ca5b752e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/reporting/reports_publication_rule.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/reporting/reports_publication_rule.md @@ -1,4 +1,4 @@ -Règles de publication des rapports {#publication_rules} +Règles de publication des rapports \{#publication_rules\} ================================== Dans l\'interface Centreon, les règles définies dans la page "Reporting @@ -34,8 +34,8 @@ serveur de supervision : : > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -46,12 +46,12 @@ Transférez la clé sur le serveur **Centreon**.L\'utilisateur **centreonBI** sur le serveur Centreon doit être configuré avec un mot de passe): : - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Testez la connexion SSH depuis le serveur de reporting vers le serveur de supervision : : - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} Aucun mot de passe ne doit vous être demandé pour la connexion. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/service-mapping/ba-management.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/service-mapping/ba-management.md index 6b0a450cb6fc..3f413b9cf690 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/service-mapping/ba-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/service-mapping/ba-management.md @@ -37,7 +37,7 @@ disponibles afin de rendre compte de l'état d'une BA: **Cluster** en spécifiant un pourcentage ou un nombre de resources maximum en statut Critique que vous ne voulez pas dépassez - **Impact**: Lorsque vous souhaitez définir finement l'impact de - chaque indicateur en fonction de leurs poids (<=> sévérité) + chaque indicateur en fonction de leurs poids (\<=\> sévérité) Ci-dessous des explications et exemples pour chacune des méthodes diff --git a/i18n/fr/docusaurus-plugin-content-pages/index.js b/i18n/fr/docusaurus-plugin-content-pages/index.js index 48873871a3e3..c9a4bd8b1b0b 100644 --- a/i18n/fr/docusaurus-plugin-content-pages/index.js +++ b/i18n/fr/docusaurus-plugin-content-pages/index.js @@ -1,5 +1,5 @@ import React from 'react'; -import { Redirect } from 'react-router-dom'; +import { Redirect } from '@docusaurus/router'; import clsx from 'clsx'; import Layout from '@theme/Layout'; import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; diff --git a/package.json b/package.json index 4683689c3ff6..dcd183cc04f2 100644 --- a/package.json +++ b/package.json @@ -15,18 +15,17 @@ }, "dependencies": { "@cmfcmf/docusaurus-search-local": "^1.2.0", - "@docusaurus/core": "^2.4.3", - "@docusaurus/plugin-content-docs": "^2.4.3", - "@docusaurus/plugin-ideal-image": "^2.4.3", - "@docusaurus/preset-classic": "^2.4.3", - "@svgr/webpack": "^8.1.0", - "@swc/core": "^1.7.39", - "clsx": "^1.2.1", - "plugin-image-zoom": "https://github.com/flexanalytics/plugin-image-zoom.git", - "prism-react-renderer": "^1.3.5", - "react": "^17.0.2", - "react-dom": "^17.0.2", - "swc-loader": "^0.2.6", + "@docusaurus/core": "^3.6.3", + "@docusaurus/faster": "^3.6.3", + "@docusaurus/plugin-content-docs": "^3.6.3", + "@docusaurus/plugin-ideal-image": "^3.6.3", + "@docusaurus/preset-classic": "^3.6.3", + "@docusaurus/theme-common": "^3.6.3", + "clsx": "^2.1.1", + "docusaurus-plugin-image-zoom": "^2.0.0", + "prism-react-renderer": "^2.4.0", + "react": "^18.3.1", + "react-dom": "^18.3.1", "typeface-roboto": "^1.1.13" }, "browserslist": { diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml new file mode 100644 index 000000000000..13fe3b91f6ef --- /dev/null +++ b/pnpm-lock.yaml @@ -0,0 +1,12583 @@ +lockfileVersion: '9.0' + +settings: + autoInstallPeers: true + excludeLinksFromLockfile: false + +importers: + + .: + dependencies: + '@cmfcmf/docusaurus-search-local': + specifier: ^1.2.0 + version: 1.2.0(@docusaurus/core@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(search-insights@2.17.3) + '@docusaurus/core': + specifier: ^3.6.3 + version: 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/faster': + specifier: ^3.6.3 + version: 3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)) + '@docusaurus/plugin-content-docs': + specifier: ^3.6.3 + version: 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-ideal-image': + specifier: ^3.6.3 + version: 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(prop-types@15.8.1)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/preset-classic': + specifier: ^3.6.3 + version: 3.6.3(@algolia/client-search@4.24.0)(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)(typescript@5.7.2) + '@docusaurus/theme-common': + specifier: ^3.6.3 + version: 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + clsx: + specifier: ^2.1.1 + version: 2.1.1 + docusaurus-plugin-image-zoom: + specifier: ^2.0.0 + version: 2.0.0(@docusaurus/theme-classic@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)) + prism-react-renderer: + specifier: ^2.4.0 + version: 2.4.0(react@18.3.1) + react: + specifier: ^18.3.1 + version: 18.3.1 + react-dom: + specifier: ^18.3.1 + version: 18.3.1(react@18.3.1) + typeface-roboto: + specifier: ^1.1.13 + version: 1.1.13 + +packages: + + '@algolia/autocomplete-core@1.17.7': + resolution: {integrity: sha512-BjiPOW6ks90UKl7TwMv7oNQMnzU+t/wk9mgIDi6b1tXpUek7MW0lbNOUHpvam9pe3lVCf4xPFT+lK7s+e+fs7Q==} + + '@algolia/autocomplete-core@1.17.8': + resolution: {integrity: sha512-WKQS6+83DYB7bsCN7HUxPGzwR1ZtKy+E8WybnuxnsGzQG/zd4j96R4USqsjz0/tOQVAA4hnlqNn9LtcaOIjCyQ==} + + '@algolia/autocomplete-js@1.17.8': + resolution: {integrity: sha512-WQ5xZ5sY16UH6V0+ACpe2NoKPWs9L/m5uQQn8eNiM7jsHShonEhwV3/kB897k1TovfHqhtH0gPXXMN95taZAqA==} + peerDependencies: + '@algolia/client-search': '>= 4.5.1 < 6' + algoliasearch: '>= 4.9.1 < 6' + + '@algolia/autocomplete-plugin-algolia-insights@1.17.7': + resolution: {integrity: sha512-Jca5Ude6yUOuyzjnz57og7Et3aXjbwCSDf/8onLHSQgw1qW3ALl9mrMWaXb5FmPVkV3EtkD2F/+NkT6VHyPu9A==} + peerDependencies: + search-insights: '>= 1 < 3' + + '@algolia/autocomplete-plugin-algolia-insights@1.17.8': + resolution: {integrity: sha512-aNbLpDONZejsQKdozt0c6mFvUc8yINpv6WgHyJ9oZm4GFkwtbe0KWTlowyNIO/yRaoGC+Y0BkmSLMnGImy01eQ==} + peerDependencies: + search-insights: '>= 1 < 3' + + '@algolia/autocomplete-preset-algolia@1.17.7': + resolution: {integrity: sha512-ggOQ950+nwbWROq2MOCIL71RE0DdQZsceqrg32UqnhDz8FlO9rL8ONHNsI2R1MH0tkgVIDKI/D0sMiUchsFdWA==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' + + '@algolia/autocomplete-preset-algolia@1.17.8': + resolution: {integrity: sha512-EHGmvfV9Y6HzDlTSt/AAdOthVTH8zgr6A4h9ehheDsAjqsyXj9uNvMAd4lq5bOJs+MZCWTcxpK+Btr9Tcihr3g==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' + + '@algolia/autocomplete-shared@1.17.7': + resolution: {integrity: sha512-o/1Vurr42U/qskRSuhBH+VKxMvkkUVTLU6WZQr+L5lGZZLYWyhdzWjW0iGXY7EkwRTjBqvN2EsR81yCTGV/kmg==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' + + '@algolia/autocomplete-shared@1.17.8': + resolution: {integrity: sha512-2w26RGB9zlyrnPpT/TpB0pbtukmUVYrKVt9ydlHnpPU7FgoiblUBpzzQTVzqMqYASGGjURaKLu7FakmaTIkClg==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' + + '@algolia/autocomplete-theme-classic@1.17.8': + resolution: {integrity: sha512-70IJMktChk6mFTqegBYZk5MR0vquX+JEUG7rc4Jo75LTbe3BN4Lh6nUwaBXoLpx4v1zMID1vOsJ0Zv1M/3q3Jw==} + + '@algolia/cache-browser-local-storage@4.24.0': + resolution: {integrity: sha512-t63W9BnoXVrGy9iYHBgObNXqYXM3tYXCjDSHeNwnsc324r4o5UiVKUiAB4THQ5z9U5hTj6qUvwg/Ez43ZD85ww==} + + '@algolia/cache-common@4.24.0': + resolution: {integrity: sha512-emi+v+DmVLpMGhp0V9q9h5CdkURsNmFC+cOS6uK9ndeJm9J4TiqSvPYVu+THUP8P/S08rxf5x2P+p3CfID0Y4g==} + + '@algolia/cache-in-memory@4.24.0': + resolution: {integrity: sha512-gDrt2so19jW26jY3/MkFg5mEypFIPbPoXsQGQWAi6TrCPsNOSEYepBMPlucqWigsmEy/prp5ug2jy/N3PVG/8w==} + + '@algolia/client-abtesting@5.17.0': + resolution: {integrity: sha512-6+7hPdOEPfJqjWNYPRaVcttLLAtVqQyp1U7xBA1e1uSya1ivIr9FtS/GBr31mfvwk2N2yxV4W7itxuBtST8SWg==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-account@4.24.0': + resolution: {integrity: sha512-adcvyJ3KjPZFDybxlqnf+5KgxJtBjwTPTeyG2aOyoJvx0Y8dUQAEOEVOJ/GBxX0WWNbmaSrhDURMhc+QeevDsA==} + + '@algolia/client-analytics@4.24.0': + resolution: {integrity: sha512-y8jOZt1OjwWU4N2qr8G4AxXAzaa8DBvyHTWlHzX/7Me1LX8OayfgHexqrsL4vSBcoMmVw2XnVW9MhL+Y2ZDJXg==} + + '@algolia/client-analytics@5.17.0': + resolution: {integrity: sha512-nhJ+elL8h0Fts3xD9261zE2NvTs7nPMe9/SfAgMnWnbvxmuhJn7ZymnBsfm2VkTDb4Dy810ZAdBfzYEk7PjlAw==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-common@4.24.0': + resolution: {integrity: sha512-bc2ROsNL6w6rqpl5jj/UywlIYC21TwSSoFHKl01lYirGMW+9Eek6r02Tocg4gZ8HAw3iBvu6XQiM3BEbmEMoiA==} + + '@algolia/client-common@5.17.0': + resolution: {integrity: sha512-9eC8i41/4xcQ/wI6fVM4LwC/ZGcDl3mToqjM0wTZzePWhXgRrdzOzqy/XgP+L1yYCDfkMFBZZsruNL5U8aEOag==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-insights@5.17.0': + resolution: {integrity: sha512-JL/vWNPUIuScsJubyC4aPHkpMftlK2qGqMiR2gy0rGvrh8v0w+ec6Ebq+efoFgE8wO55HJPTxiKeerE1DaQgvA==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-personalization@4.24.0': + resolution: {integrity: sha512-l5FRFm/yngztweU0HdUzz1rC4yoWCFo3IF+dVIVTfEPg906eZg5BOd1k0K6rZx5JzyyoP4LdmOikfkfGsKVE9w==} + + '@algolia/client-personalization@5.17.0': + resolution: {integrity: sha512-PkMUfww8QiRpyLkW4kzmc7IJDcW90sfUpnTgUOVlug5zEE2iv1ruHrJxdcNRTXkA0fgVpHu3oxXmCQL/ie2p7A==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-query-suggestions@5.17.0': + resolution: {integrity: sha512-bokfgPN2whetLuiX9NB6C6d7Eke+dvHuASOPiB+jdI8Z6hacLHkcJjYeZY4Mppj0/oJ1KlyNivj+8WNpZeGhYA==} + engines: {node: '>= 14.0.0'} + + '@algolia/client-search@4.24.0': + resolution: {integrity: sha512-uRW6EpNapmLAD0mW47OXqTP8eiIx5F6qN9/x/7HHO6owL3N1IXqydGwW5nhDFBrV+ldouro2W1VX3XlcUXEFCA==} + + '@algolia/client-search@5.17.0': + resolution: {integrity: sha512-alY3U79fiEvlR/0optgt1LZp9MfthXFnuEA4GYS81svozDOF61gdvxgBjt6SYtmskmTQQZDWVgakvUvvHrDzMw==} + engines: {node: '>= 14.0.0'} + + '@algolia/events@4.0.1': + resolution: {integrity: sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ==} + + '@algolia/ingestion@1.17.0': + resolution: {integrity: sha512-9+mO+FbIpWz6izh1lXzON9BcenBKx4K3qVjSWiFFmL8nv+7b7zpGq++LXWr/Lxv/bZ9+D71Go6QVL6AZQhFOmg==} + engines: {node: '>= 14.0.0'} + + '@algolia/logger-common@4.24.0': + resolution: {integrity: sha512-LLUNjkahj9KtKYrQhFKCzMx0BY3RnNP4FEtO+sBybCjJ73E8jNdaKJ/Dd8A/VA4imVHP5tADZ8pn5B8Ga/wTMA==} + + '@algolia/logger-console@4.24.0': + resolution: {integrity: sha512-X4C8IoHgHfiUROfoRCV+lzSy+LHMgkoEEU1BbKcsfnV0i0S20zyy0NLww9dwVHUWNfPPxdMU+/wKmLGYf96yTg==} + + '@algolia/monitoring@1.17.0': + resolution: {integrity: sha512-Db7Qh51zVchmHa8d9nQFzTz2Ta6H2D4dpCnPj1giC/LE6UG/6e3iOnRxUzV+9ZR7etHKIrri2hbnkyNrvbqA9A==} + engines: {node: '>= 14.0.0'} + + '@algolia/recommend@4.24.0': + resolution: {integrity: sha512-P9kcgerfVBpfYHDfVZDvvdJv0lEoCvzNlOy2nykyt5bK8TyieYyiD0lguIJdRZZYGre03WIAFf14pgE+V+IBlw==} + + '@algolia/recommend@5.17.0': + resolution: {integrity: sha512-7vM4+mfuLYbslj8+RNsP/ISwY7izu5HcQqQhA0l+q3EZRHF+PBeRaJXc3S1N0fTRxj8ystvwXWZPmjssB/xMLw==} + engines: {node: '>= 14.0.0'} + + '@algolia/requester-browser-xhr@4.24.0': + resolution: {integrity: sha512-Z2NxZMb6+nVXSjF13YpjYTdvV3032YTBSGm2vnYvYPA6mMxzM3v5rsCiSspndn9rzIW4Qp1lPHBvuoKJV6jnAA==} + + '@algolia/requester-browser-xhr@5.17.0': + resolution: {integrity: sha512-bXSiPL2R08s4e9qvNZsJA0bXZeyWH2A5D4shS8kRT22b8GgjtnGTuoZmi6MxtKOEaN0lpHPbjvjXAO7UIOhDog==} + engines: {node: '>= 14.0.0'} + + '@algolia/requester-common@4.24.0': + resolution: {integrity: sha512-k3CXJ2OVnvgE3HMwcojpvY6d9kgKMPRxs/kVohrwF5WMr2fnqojnycZkxPoEg+bXm8fi5BBfFmOqgYztRtHsQA==} + + '@algolia/requester-fetch@5.17.0': + resolution: {integrity: sha512-mjJ6Xv7TlDDoZ6RLKrEzH1ved3g2GAq3YJjb94bA639INfxK1HM8A/wCAFSZ8ye+QM/jppwauDXe1PENkuareQ==} + engines: {node: '>= 14.0.0'} + + '@algolia/requester-node-http@4.24.0': + resolution: {integrity: sha512-JF18yTjNOVYvU/L3UosRcvbPMGT9B+/GQWNWnenIImglzNVGpyzChkXLnrSf6uxwVNO6ESGu6oN8MqcGQcjQJw==} + + '@algolia/requester-node-http@5.17.0': + resolution: {integrity: sha512-Z2BXTR7BctlGPNig21k2wf/5nlH+96lU2UElzXTKiptyn2iM8lDU8zdO+dRll0AxQUxUGWEnkBysst9xL3S2cg==} + engines: {node: '>= 14.0.0'} + + '@algolia/transporter@4.24.0': + resolution: {integrity: sha512-86nI7w6NzWxd1Zp9q3413dRshDqAzSbsQjhcDhPIatEFiZrL1/TjnHL8S7jVKFePlIMzDsZWXAXwXzcok9c5oA==} + + '@ampproject/remapping@2.3.0': + resolution: {integrity: sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==} + engines: {node: '>=6.0.0'} + + '@babel/code-frame@7.26.2': + resolution: {integrity: sha512-RJlIHRueQgwWitWgF8OdFYGZX328Ax5BCemNGlqHfplnRT9ESi8JkFlvaVYbS+UubVY6dpv87Fs2u5M29iNFVQ==} + engines: {node: '>=6.9.0'} + + '@babel/compat-data@7.26.3': + resolution: {integrity: sha512-nHIxvKPniQXpmQLb0vhY3VaFb3S0YrTAwpOWJZh1wn3oJPjJk9Asva204PsBdmAE8vpzfHudT8DB0scYvy9q0g==} + engines: {node: '>=6.9.0'} + + '@babel/core@7.26.0': + resolution: {integrity: sha512-i1SLeK+DzNnQ3LL/CswPCa/E5u4lh1k6IAEphON8F+cXt0t9euTshDru0q7/IqMa1PMPz5RnHuHscF8/ZJsStg==} + engines: {node: '>=6.9.0'} + + '@babel/generator@7.26.3': + resolution: {integrity: sha512-6FF/urZvD0sTeO7k6/B15pMLC4CHUv1426lzr3N01aHJTl046uCAh9LXW/fzeXXjPNCJ6iABW5XaWOsIZB93aQ==} + engines: {node: '>=6.9.0'} + + '@babel/helper-annotate-as-pure@7.25.9': + resolution: {integrity: sha512-gv7320KBUFJz1RnylIg5WWYPRXKZ884AGkYpgpWW02TH66Dl+HaC1t1CKd0z3R4b6hdYEcmrNZHUmfCP+1u3/g==} + engines: {node: '>=6.9.0'} + + '@babel/helper-compilation-targets@7.25.9': + resolution: {integrity: sha512-j9Db8Suy6yV/VHa4qzrj9yZfZxhLWQdVnRlXxmKLYlhWUVB1sB2G5sxuWYXk/whHD9iW76PmNzxZ4UCnTQTVEQ==} + engines: {node: '>=6.9.0'} + + '@babel/helper-create-class-features-plugin@7.25.9': + resolution: {integrity: sha512-UTZQMvt0d/rSz6KI+qdu7GQze5TIajwTS++GUozlw8VBJDEOAqSXwm1WvmYEZwqdqSGQshRocPDqrt4HBZB3fQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/helper-create-regexp-features-plugin@7.26.3': + resolution: {integrity: sha512-G7ZRb40uUgdKOQqPLjfD12ZmGA54PzqDFUv2BKImnC9QIfGhIHKvVML0oN8IUiDq4iRqpq74ABpvOaerfWdong==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/helper-define-polyfill-provider@0.6.3': + resolution: {integrity: sha512-HK7Bi+Hj6H+VTHA3ZvBis7V/6hu9QuTrnMXNybfUf2iiuU/N97I8VjB+KbhFF8Rld/Lx5MzoCwPCpPjfK+n8Cg==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 + + '@babel/helper-member-expression-to-functions@7.25.9': + resolution: {integrity: sha512-wbfdZ9w5vk0C0oyHqAJbc62+vet5prjj01jjJ8sKn3j9h3MQQlflEdXYvuqRWjHnM12coDEqiC1IRCi0U/EKwQ==} + engines: {node: '>=6.9.0'} + + '@babel/helper-module-imports@7.25.9': + resolution: {integrity: sha512-tnUA4RsrmflIM6W6RFTLFSXITtl0wKjgpnLgXyowocVPrbYrLUXSBXDgTs8BlbmIzIdlBySRQjINYs2BAkiLtw==} + engines: {node: '>=6.9.0'} + + '@babel/helper-module-transforms@7.26.0': + resolution: {integrity: sha512-xO+xu6B5K2czEnQye6BHA7DolFFmS3LB7stHZFaOLb1pAwO1HWLS8fXA+eh0A2yIvltPVmx3eNNDBJA2SLHXFw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/helper-optimise-call-expression@7.25.9': + resolution: {integrity: sha512-FIpuNaz5ow8VyrYcnXQTDRGvV6tTjkNtCK/RYNDXGSLlUD6cBuQTSw43CShGxjvfBTfcUA/r6UhUCbtYqkhcuQ==} + engines: {node: '>=6.9.0'} + + '@babel/helper-plugin-utils@7.25.9': + resolution: {integrity: sha512-kSMlyUVdWe25rEsRGviIgOWnoT/nfABVWlqt9N19/dIPWViAOW2s9wznP5tURbs/IDuNk4gPy3YdYRgH3uxhBw==} + engines: {node: '>=6.9.0'} + + '@babel/helper-remap-async-to-generator@7.25.9': + resolution: {integrity: sha512-IZtukuUeBbhgOcaW2s06OXTzVNJR0ybm4W5xC1opWFFJMZbwRj5LCk+ByYH7WdZPZTt8KnFwA8pvjN2yqcPlgw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/helper-replace-supers@7.25.9': + resolution: {integrity: sha512-IiDqTOTBQy0sWyeXyGSC5TBJpGFXBkRynjBeXsvbhQFKj2viwJC76Epz35YLU1fpe/Am6Vppb7W7zM4fPQzLsQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/helper-skip-transparent-expression-wrappers@7.25.9': + resolution: {integrity: sha512-K4Du3BFa3gvyhzgPcntrkDgZzQaq6uozzcpGbOO1OEJaI+EJdqWIMTLgFgQf6lrfiDFo5FU+BxKepI9RmZqahA==} + engines: {node: '>=6.9.0'} + + '@babel/helper-string-parser@7.25.9': + resolution: {integrity: sha512-4A/SCr/2KLd5jrtOMFzaKjVtAei3+2r/NChoBNoZ3EyP/+GlhoaEGoWOZUmFmoITP7zOJyHIMm+DYRd8o3PvHA==} + engines: {node: '>=6.9.0'} + + '@babel/helper-validator-identifier@7.25.9': + resolution: {integrity: sha512-Ed61U6XJc3CVRfkERJWDz4dJwKe7iLmmJsbOGu9wSloNSFttHV0I8g6UAgb7qnK5ly5bGLPd4oXZlxCdANBOWQ==} + engines: {node: '>=6.9.0'} + + '@babel/helper-validator-option@7.25.9': + resolution: {integrity: sha512-e/zv1co8pp55dNdEcCynfj9X7nyUKUXoUEwfXqaZt0omVOmDe9oOTdKStH4GmAw6zxMFs50ZayuMfHDKlO7Tfw==} + engines: {node: '>=6.9.0'} + + '@babel/helper-wrap-function@7.25.9': + resolution: {integrity: sha512-ETzz9UTjQSTmw39GboatdymDq4XIQbR8ySgVrylRhPOFpsd+JrKHIuF0de7GCWmem+T4uC5z7EZguod7Wj4A4g==} + engines: {node: '>=6.9.0'} + + '@babel/helpers@7.26.0': + resolution: {integrity: sha512-tbhNuIxNcVb21pInl3ZSjksLCvgdZy9KwJ8brv993QtIVKJBBkYXz4q4ZbAv31GdnC+R90np23L5FbEBlthAEw==} + engines: {node: '>=6.9.0'} + + '@babel/parser@7.26.3': + resolution: {integrity: sha512-WJ/CvmY8Mea8iDXo6a7RK2wbmJITT5fN3BEkRuFlxVyNx8jOKIIhmC4fSkTcPcf8JyavbBwIe6OpiCOBXt/IcA==} + engines: {node: '>=6.0.0'} + hasBin: true + + '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.25.9': + resolution: {integrity: sha512-ZkRyVkThtxQ/J6nv3JFYv1RYY+JT5BvU0y3k5bWrmuG4woXypRa4PXmm9RhOwodRkYFWqC0C0cqcJ4OqR7kW+g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.25.9': + resolution: {integrity: sha512-MrGRLZxLD/Zjj0gdU15dfs+HH/OXvnw/U4jJD8vpcP2CJQapPEv1IWwjc/qMg7ItBlPwSv1hRBbb7LeuANdcnw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.25.9': + resolution: {integrity: sha512-2qUwwfAFpJLZqxd02YW9btUCZHl+RFvdDkNfZwaIJrvB8Tesjsk8pEQkTvGwZXLqXUx/2oyY3ySRhm6HOXuCug==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.25.9': + resolution: {integrity: sha512-6xWgLZTJXwilVjlnV7ospI3xi+sl8lN8rXXbBD6vYn3UYDlGsag8wrZkKcSI8G6KgqKP7vNFaDgeDnfAABq61g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.13.0 + + '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.25.9': + resolution: {integrity: sha512-aLnMXYPnzwwqhYSCyXfKkIkYgJ8zv9RK+roo9DkTXz38ynIhd9XCbN08s3MGvqL2MYGVUGdRQLL/JqBIeJhJBg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2': + resolution: {integrity: sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-dynamic-import@7.8.3': + resolution: {integrity: sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-import-assertions@7.26.0': + resolution: {integrity: sha512-QCWT5Hh830hK5EQa7XzuqIkQU9tT/whqbDz7kuaZMHFl1inRRg7JnuAEOQ0Ur0QUl0NufCk1msK2BeY79Aj/eg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-import-attributes@7.26.0': + resolution: {integrity: sha512-e2dttdsJ1ZTpi3B9UYGLw41hifAubg19AtCu/2I/F1QNVclOBr1dYpTdmdyZ84Xiz43BS/tCUkMAZNLv12Pi+A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-jsx@7.25.9': + resolution: {integrity: sha512-ld6oezHQMZsZfp6pWtbjaNDF2tiiCYYDqQszHt5VV437lewP9aSi2Of99CK0D0XB21k7FLgnLcmQKyKzynfeAA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-typescript@7.25.9': + resolution: {integrity: sha512-hjMgRy5hb8uJJjUcdWunWVcoi9bGpJp8p5Ol1229PoN6aytsLwNMgmdftO23wnCLMfVmTwZDWMPNq/D1SY60JQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-syntax-unicode-sets-regex@7.18.6': + resolution: {integrity: sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-transform-arrow-functions@7.25.9': + resolution: {integrity: sha512-6jmooXYIwn9ca5/RylZADJ+EnSxVUS5sjeJ9UPk6RWRzXCmOJCy6dqItPJFpw2cuCangPK4OYr5uhGKcmrm5Qg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-async-generator-functions@7.25.9': + resolution: {integrity: sha512-RXV6QAzTBbhDMO9fWwOmwwTuYaiPbggWQ9INdZqAYeSHyG7FzQ+nOZaUUjNwKv9pV3aE4WFqFm1Hnbci5tBCAw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-async-to-generator@7.25.9': + resolution: {integrity: sha512-NT7Ejn7Z/LjUH0Gv5KsBCxh7BH3fbLTV0ptHvpeMvrt3cPThHfJfst9Wrb7S8EvJ7vRTFI7z+VAvFVEQn/m5zQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-block-scoped-functions@7.25.9': + resolution: {integrity: sha512-toHc9fzab0ZfenFpsyYinOX0J/5dgJVA2fm64xPewu7CoYHWEivIWKxkK2rMi4r3yQqLnVmheMXRdG+k239CgA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-block-scoping@7.25.9': + resolution: {integrity: sha512-1F05O7AYjymAtqbsFETboN1NvBdcnzMerO+zlMyJBEz6WkMdejvGWw9p05iTSjC85RLlBseHHQpYaM4gzJkBGg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-class-properties@7.25.9': + resolution: {integrity: sha512-bbMAII8GRSkcd0h0b4X+36GksxuheLFjP65ul9w6C3KgAamI3JqErNgSrosX6ZPj+Mpim5VvEbawXxJCyEUV3Q==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-class-static-block@7.26.0': + resolution: {integrity: sha512-6J2APTs7BDDm+UMqP1useWqhcRAXo0WIoVj26N7kPFB6S73Lgvyka4KTZYIxtgYXiN5HTyRObA72N2iu628iTQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.12.0 + + '@babel/plugin-transform-classes@7.25.9': + resolution: {integrity: sha512-mD8APIXmseE7oZvZgGABDyM34GUmK45Um2TXiBUt7PnuAxrgoSVf123qUzPxEr/+/BHrRn5NMZCdE2m/1F8DGg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-computed-properties@7.25.9': + resolution: {integrity: sha512-HnBegGqXZR12xbcTHlJ9HGxw1OniltT26J5YpfruGqtUHlz/xKf/G2ak9e+t0rVqrjXa9WOhvYPz1ERfMj23AA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-destructuring@7.25.9': + resolution: {integrity: sha512-WkCGb/3ZxXepmMiX101nnGiU+1CAdut8oHyEOHxkKuS1qKpU2SMXE2uSvfz8PBuLd49V6LEsbtyPhWC7fnkgvQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-dotall-regex@7.25.9': + resolution: {integrity: sha512-t7ZQ7g5trIgSRYhI9pIJtRl64KHotutUJsh4Eze5l7olJv+mRSg4/MmbZ0tv1eeqRbdvo/+trvJD/Oc5DmW2cA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-duplicate-keys@7.25.9': + resolution: {integrity: sha512-LZxhJ6dvBb/f3x8xwWIuyiAHy56nrRG3PeYTpBkkzkYRRQ6tJLu68lEF5VIqMUZiAV7a8+Tb78nEoMCMcqjXBw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.25.9': + resolution: {integrity: sha512-0UfuJS0EsXbRvKnwcLjFtJy/Sxc5J5jhLHnFhy7u4zih97Hz6tJkLU+O+FMMrNZrosUPxDi6sYxJ/EA8jDiAog==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-transform-dynamic-import@7.25.9': + resolution: {integrity: sha512-GCggjexbmSLaFhqsojeugBpeaRIgWNTcgKVq/0qIteFEqY2A+b9QidYadrWlnbWQUrW5fn+mCvf3tr7OeBFTyg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-exponentiation-operator@7.26.3': + resolution: {integrity: sha512-7CAHcQ58z2chuXPWblnn1K6rLDnDWieghSOEmqQsrBenH0P9InCUtOJYD89pvngljmZlJcz3fcmgYsXFNGa1ZQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-export-namespace-from@7.25.9': + resolution: {integrity: sha512-2NsEz+CxzJIVOPx2o9UsW1rXLqtChtLoVnwYHHiB04wS5sgn7mrV45fWMBX0Kk+ub9uXytVYfNP2HjbVbCB3Ww==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-for-of@7.25.9': + resolution: {integrity: sha512-LqHxduHoaGELJl2uhImHwRQudhCM50pT46rIBNvtT/Oql3nqiS3wOwP+5ten7NpYSXrrVLgtZU3DZmPtWZo16A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-function-name@7.25.9': + resolution: {integrity: sha512-8lP+Yxjv14Vc5MuWBpJsoUCd3hD6V9DgBon2FVYL4jJgbnVQ9fTgYmonchzZJOVNgzEgbxp4OwAf6xz6M/14XA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-json-strings@7.25.9': + resolution: {integrity: sha512-xoTMk0WXceiiIvsaquQQUaLLXSW1KJ159KP87VilruQm0LNNGxWzahxSS6T6i4Zg3ezp4vA4zuwiNUR53qmQAw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-literals@7.25.9': + resolution: {integrity: sha512-9N7+2lFziW8W9pBl2TzaNht3+pgMIRP74zizeCSrtnSKVdUl8mAjjOP2OOVQAfZ881P2cNjDj1uAMEdeD50nuQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-logical-assignment-operators@7.25.9': + resolution: {integrity: sha512-wI4wRAzGko551Y8eVf6iOY9EouIDTtPb0ByZx+ktDGHwv6bHFimrgJM/2T021txPZ2s4c7bqvHbd+vXG6K948Q==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-member-expression-literals@7.25.9': + resolution: {integrity: sha512-PYazBVfofCQkkMzh2P6IdIUaCEWni3iYEerAsRWuVd8+jlM1S9S9cz1dF9hIzyoZ8IA3+OwVYIp9v9e+GbgZhA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-modules-amd@7.25.9': + resolution: {integrity: sha512-g5T11tnI36jVClQlMlt4qKDLlWnG5pP9CSM4GhdRciTNMRgkfpo5cR6b4rGIOYPgRRuFAvwjPQ/Yk+ql4dyhbw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-modules-commonjs@7.26.3': + resolution: {integrity: sha512-MgR55l4q9KddUDITEzEFYn5ZsGDXMSsU9E+kh7fjRXTIC3RHqfCo8RPRbyReYJh44HQ/yomFkqbOFohXvDCiIQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-modules-systemjs@7.25.9': + resolution: {integrity: sha512-hyss7iIlH/zLHaehT+xwiymtPOpsiwIIRlCAOwBB04ta5Tt+lNItADdlXw3jAWZ96VJ2jlhl/c+PNIQPKNfvcA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-modules-umd@7.25.9': + resolution: {integrity: sha512-bS9MVObUgE7ww36HEfwe6g9WakQ0KF07mQF74uuXdkoziUPfKyu/nIm663kz//e5O1nPInPFx36z7WJmJ4yNEw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-named-capturing-groups-regex@7.25.9': + resolution: {integrity: sha512-oqB6WHdKTGl3q/ItQhpLSnWWOpjUJLsOCLVyeFgeTktkBSCiurvPOsyt93gibI9CmuKvTUEtWmG5VhZD+5T/KA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-transform-new-target@7.25.9': + resolution: {integrity: sha512-U/3p8X1yCSoKyUj2eOBIx3FOn6pElFOKvAAGf8HTtItuPyB+ZeOqfn+mvTtg9ZlOAjsPdK3ayQEjqHjU/yLeVQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-nullish-coalescing-operator@7.25.9': + resolution: {integrity: sha512-ENfftpLZw5EItALAD4WsY/KUWvhUlZndm5GC7G3evUsVeSJB6p0pBeLQUnRnBCBx7zV0RKQjR9kCuwrsIrjWog==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-numeric-separator@7.25.9': + resolution: {integrity: sha512-TlprrJ1GBZ3r6s96Yq8gEQv82s8/5HnCVHtEJScUj90thHQbwe+E5MLhi2bbNHBEJuzrvltXSru+BUxHDoog7Q==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-object-rest-spread@7.25.9': + resolution: {integrity: sha512-fSaXafEE9CVHPweLYw4J0emp1t8zYTXyzN3UuG+lylqkvYd7RMrsOQ8TYx5RF231be0vqtFC6jnx3UmpJmKBYg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-object-super@7.25.9': + resolution: {integrity: sha512-Kj/Gh+Rw2RNLbCK1VAWj2U48yxxqL2x0k10nPtSdRa0O2xnHXalD0s+o1A6a0W43gJ00ANo38jxkQreckOzv5A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-optional-catch-binding@7.25.9': + resolution: {integrity: sha512-qM/6m6hQZzDcZF3onzIhZeDHDO43bkNNlOX0i8n3lR6zLbu0GN2d8qfM/IERJZYauhAHSLHy39NF0Ctdvcid7g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-optional-chaining@7.25.9': + resolution: {integrity: sha512-6AvV0FsLULbpnXeBjrY4dmWF8F7gf8QnvTEoO/wX/5xm/xE1Xo8oPuD3MPS+KS9f9XBEAWN7X1aWr4z9HdOr7A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-parameters@7.25.9': + resolution: {integrity: sha512-wzz6MKwpnshBAiRmn4jR8LYz/g8Ksg0o80XmwZDlordjwEk9SxBzTWC7F5ef1jhbrbOW2DJ5J6ayRukrJmnr0g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-private-methods@7.25.9': + resolution: {integrity: sha512-D/JUozNpQLAPUVusvqMxyvjzllRaF8/nSrP1s2YGQT/W4LHK4xxsMcHjhOGTS01mp9Hda8nswb+FblLdJornQw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-private-property-in-object@7.25.9': + resolution: {integrity: sha512-Evf3kcMqzXA3xfYJmZ9Pg1OvKdtqsDMSWBDzZOPLvHiTt36E75jLDQo5w1gtRU95Q4E5PDttrTf25Fw8d/uWLw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-property-literals@7.25.9': + resolution: {integrity: sha512-IvIUeV5KrS/VPavfSM/Iu+RE6llrHrYIKY1yfCzyO/lMXHQ+p7uGhonmGVisv6tSBSVgWzMBohTcvkC9vQcQFA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-react-constant-elements@7.25.9': + resolution: {integrity: sha512-Ncw2JFsJVuvfRsa2lSHiC55kETQVLSnsYGQ1JDDwkUeWGTL/8Tom8aLTnlqgoeuopWrbbGndrc9AlLYrIosrow==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-react-display-name@7.25.9': + resolution: {integrity: sha512-KJfMlYIUxQB1CJfO3e0+h0ZHWOTLCPP115Awhaz8U0Zpq36Gl/cXlpoyMRnUWlhNUBAzldnCiAZNvCDj7CrKxQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-react-jsx-development@7.25.9': + resolution: {integrity: sha512-9mj6rm7XVYs4mdLIpbZnHOYdpW42uoiBCTVowg7sP1thUOiANgMb4UtpRivR0pp5iL+ocvUv7X4mZgFRpJEzGw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-react-jsx@7.25.9': + resolution: {integrity: sha512-s5XwpQYCqGerXl+Pu6VDL3x0j2d82eiV77UJ8a2mDHAW7j9SWRqQ2y1fNo1Z74CdcYipl5Z41zvjj4Nfzq36rw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-react-pure-annotations@7.25.9': + resolution: {integrity: sha512-KQ/Takk3T8Qzj5TppkS1be588lkbTp5uj7w6a0LeQaTMSckU/wK0oJ/pih+T690tkgI5jfmg2TqDJvd41Sj1Cg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-regenerator@7.25.9': + resolution: {integrity: sha512-vwDcDNsgMPDGP0nMqzahDWE5/MLcX8sv96+wfX7as7LoF/kr97Bo/7fI00lXY4wUXYfVmwIIyG80fGZ1uvt2qg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-regexp-modifiers@7.26.0': + resolution: {integrity: sha512-vN6saax7lrA2yA/Pak3sCxuD6F5InBjn9IcrIKQPjpsLvuHYLVroTxjdlVRHjjBWxKOqIwpTXDkOssYT4BFdRw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/plugin-transform-reserved-words@7.25.9': + resolution: {integrity: sha512-7DL7DKYjn5Su++4RXu8puKZm2XBPHyjWLUidaPEkCUBbE7IPcsrkRHggAOOKydH1dASWdcUBxrkOGNxUv5P3Jg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-runtime@7.25.9': + resolution: {integrity: sha512-nZp7GlEl+yULJrClz0SwHPqir3lc0zsPrDHQUcxGspSL7AKrexNSEfTbfqnDNJUO13bgKyfuOLMF8Xqtu8j3YQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-shorthand-properties@7.25.9': + resolution: {integrity: sha512-MUv6t0FhO5qHnS/W8XCbHmiRWOphNufpE1IVxhK5kuN3Td9FT1x4rx4K42s3RYdMXCXpfWkGSbCSd0Z64xA7Ng==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-spread@7.25.9': + resolution: {integrity: sha512-oNknIB0TbURU5pqJFVbOOFspVlrpVwo2H1+HUIsVDvp5VauGGDP1ZEvO8Nn5xyMEs3dakajOxlmkNW7kNgSm6A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-sticky-regex@7.25.9': + resolution: {integrity: sha512-WqBUSgeVwucYDP9U/xNRQam7xV8W5Zf+6Eo7T2SRVUFlhRiMNFdFz58u0KZmCVVqs2i7SHgpRnAhzRNmKfi2uA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-template-literals@7.25.9': + resolution: {integrity: sha512-o97AE4syN71M/lxrCtQByzphAdlYluKPDBzDVzMmfCobUjjhAryZV0AIpRPrxN0eAkxXO6ZLEScmt+PNhj2OTw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-typeof-symbol@7.25.9': + resolution: {integrity: sha512-v61XqUMiueJROUv66BVIOi0Fv/CUuZuZMl5NkRoCVxLAnMexZ0A3kMe7vvZ0nulxMuMp0Mk6S5hNh48yki08ZA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-typescript@7.26.3': + resolution: {integrity: sha512-6+5hpdr6mETwSKjmJUdYw0EIkATiQhnELWlE3kJFBwSg/BGIVwVaVbX+gOXBCdc7Ln1RXZxyWGecIXhUfnl7oA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-unicode-escapes@7.25.9': + resolution: {integrity: sha512-s5EDrE6bW97LtxOcGj1Khcx5AaXwiMmi4toFWRDP9/y0Woo6pXC+iyPu/KuhKtfSrNFd7jJB+/fkOtZy6aIC6Q==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-unicode-property-regex@7.25.9': + resolution: {integrity: sha512-Jt2d8Ga+QwRluxRQ307Vlxa6dMrYEMZCgGxoPR8V52rxPyldHu3hdlHspxaqYmE7oID5+kB+UKUB/eWS+DkkWg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-unicode-regex@7.25.9': + resolution: {integrity: sha512-yoxstj7Rg9dlNn9UQxzk4fcNivwv4nUYz7fYXBaKxvw/lnmPuOm/ikoELygbYq68Bls3D/D+NBPHiLwZdZZ4HA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/plugin-transform-unicode-sets-regex@7.25.9': + resolution: {integrity: sha512-8BYqO3GeVNHtx69fdPshN3fnzUNLrWdHhk/icSwigksJGczKSizZ+Z6SBCxTs723Fr5VSNorTIK7a+R2tISvwQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 + + '@babel/preset-env@7.26.0': + resolution: {integrity: sha512-H84Fxq0CQJNdPFT2DrfnylZ3cf5K43rGfWK4LJGPpjKHiZlk0/RzwEus3PDDZZg+/Er7lCA03MVacueUuXdzfw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/preset-modules@0.1.6-no-external-plugins': + resolution: {integrity: sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA==} + peerDependencies: + '@babel/core': ^7.0.0-0 || ^8.0.0-0 <8.0.0 + + '@babel/preset-react@7.26.3': + resolution: {integrity: sha512-Nl03d6T9ky516DGK2YMxrTqvnpUW63TnJMOMonj+Zae0JiPC5BC9xPMSL6L8fiSpA5vP88qfygavVQvnLp+6Cw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/preset-typescript@7.26.0': + resolution: {integrity: sha512-NMk1IGZ5I/oHhoXEElcm+xUnL/szL6xflkFZmoEU9xj1qSJXpiS7rsspYo92B4DRCDvZn2erT5LdsCeXAKNCkg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@babel/runtime-corejs3@7.26.0': + resolution: {integrity: sha512-YXHu5lN8kJCb1LOb9PgV6pvak43X2h4HvRApcN5SdWeaItQOzfn1hgP6jasD6KWQyJDBxrVmA9o9OivlnNJK/w==} + engines: {node: '>=6.9.0'} + + '@babel/runtime@7.26.0': + resolution: {integrity: sha512-FDSOghenHTiToteC/QRlv2q3DhPZ/oOXTBoirfWNx1Cx3TMVcGWQtMMmQcSvb/JjpNeGzx8Pq/b4fKEJuWm1sw==} + engines: {node: '>=6.9.0'} + + '@babel/template@7.25.9': + resolution: {integrity: sha512-9DGttpmPvIxBb/2uwpVo3dqJ+O6RooAFOS+lB+xDqoE2PVCE8nfoHMdZLpfCQRLwvohzXISPZcgxt80xLfsuwg==} + engines: {node: '>=6.9.0'} + + '@babel/traverse@7.26.4': + resolution: {integrity: sha512-fH+b7Y4p3yqvApJALCPJcwb0/XaOSgtK4pzV6WVjPR5GLFQBRI7pfoX2V2iM48NXvX07NUxxm1Vw98YjqTcU5w==} + engines: {node: '>=6.9.0'} + + '@babel/types@7.26.3': + resolution: {integrity: sha512-vN5p+1kl59GVKMvTHt55NzzmYVxprfJD+ql7U9NFIfKCBkYE55LYtS+WtPlaYOyzydrKI8Nezd+aZextrd+FMA==} + engines: {node: '>=6.9.0'} + + '@cmfcmf/docusaurus-search-local@1.2.0': + resolution: {integrity: sha512-Tc0GhRBsfZAiB+f6BoPB8YCQap6JzzcDyJ0dLSCSzWQ6wdWvDlTBrHc1YqR8q8AZ+STRszL5eZpZFi5dbTCdYg==} + peerDependencies: + '@docusaurus/core': ^2.0.0 + nodejieba: ^2.5.0 + peerDependenciesMeta: + nodejieba: + optional: true + + '@colors/colors@1.5.0': + resolution: {integrity: sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==} + engines: {node: '>=0.1.90'} + + '@csstools/cascade-layer-name-parser@2.0.4': + resolution: {integrity: sha512-7DFHlPuIxviKYZrOiwVU/PiHLm3lLUR23OMuEEtfEOQTOp9hzQ2JjdY6X5H18RVuUPJqSCI+qNnD5iOLMVE0bA==} + engines: {node: '>=18'} + peerDependencies: + '@csstools/css-parser-algorithms': ^3.0.4 + '@csstools/css-tokenizer': ^3.0.3 + + '@csstools/color-helpers@5.0.1': + resolution: {integrity: sha512-MKtmkA0BX87PKaO1NFRTFH+UnkgnmySQOvNxJubsadusqPEC2aJ9MOQiMceZJJ6oitUl/i0L6u0M1IrmAOmgBA==} + engines: {node: '>=18'} + + '@csstools/css-calc@2.1.0': + resolution: {integrity: sha512-X69PmFOrjTZfN5ijxtI8hZ9kRADFSLrmmQ6hgDJ272Il049WGKpDY64KhrFm/7rbWve0z81QepawzjkKlqkNGw==} + engines: {node: '>=18'} + peerDependencies: + '@csstools/css-parser-algorithms': ^3.0.4 + '@csstools/css-tokenizer': ^3.0.3 + + '@csstools/css-color-parser@3.0.6': + resolution: {integrity: sha512-S/IjXqTHdpI4EtzGoNCHfqraXF37x12ZZHA1Lk7zoT5pm2lMjFuqhX/89L7dqX4CcMacKK+6ZCs5TmEGb/+wKw==} + engines: {node: '>=18'} + peerDependencies: + '@csstools/css-parser-algorithms': ^3.0.4 + '@csstools/css-tokenizer': ^3.0.3 + + '@csstools/css-parser-algorithms@3.0.4': + resolution: {integrity: sha512-Up7rBoV77rv29d3uKHUIVubz1BTcgyUK72IvCQAbfbMv584xHcGKCKbWh7i8hPrRJ7qU4Y8IO3IY9m+iTB7P3A==} + engines: {node: '>=18'} + peerDependencies: + '@csstools/css-tokenizer': ^3.0.3 + + '@csstools/css-tokenizer@3.0.3': + resolution: {integrity: sha512-UJnjoFsmxfKUdNYdWgOB0mWUypuLvAfQPH1+pyvRJs6euowbFkFC6P13w1l8mJyi3vxYMxc9kld5jZEGRQs6bw==} + engines: {node: '>=18'} + + '@csstools/media-query-list-parser@4.0.2': + resolution: {integrity: sha512-EUos465uvVvMJehckATTlNqGj4UJWkTmdWuDMjqvSUkjGpmOyFZBVwb4knxCm/k2GMTXY+c/5RkdndzFYWeX5A==} + engines: {node: '>=18'} + peerDependencies: + '@csstools/css-parser-algorithms': ^3.0.4 + '@csstools/css-tokenizer': ^3.0.3 + + '@csstools/postcss-cascade-layers@5.0.1': + resolution: {integrity: sha512-XOfhI7GShVcKiKwmPAnWSqd2tBR0uxt+runAxttbSp/LY2U16yAVPmAf7e9q4JJ0d+xMNmpwNDLBXnmRCl3HMQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-color-function@4.0.6': + resolution: {integrity: sha512-EcvXfC60cTIumzpsxWuvVjb7rsJEHPvqn3jeMEBUaE3JSc4FRuP7mEQ+1eicxWmIrs3FtzMH9gR3sgA5TH+ebQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-color-mix-function@3.0.6': + resolution: {integrity: sha512-jVKdJn4+JkASYGhyPO+Wa5WXSx1+oUgaXb3JsjJn/BlrtFh5zjocCY7pwWi0nuP24V1fY7glQsxEYcYNy0dMFg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-content-alt-text@2.0.4': + resolution: {integrity: sha512-YItlZUOuZJCBlRaCf8Aucc1lgN41qYGALMly0qQllrxYJhiyzlI6RxOTMUvtWk+KhS8GphMDsDhKQ7KTPfEMSw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-exponential-functions@2.0.5': + resolution: {integrity: sha512-mi8R6dVfA2nDoKM3wcEi64I8vOYEgQVtVKCfmLHXupeLpACfGAided5ddMt5f+CnEodNu4DifuVwb0I6fQDGGQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-font-format-keywords@4.0.0': + resolution: {integrity: sha512-usBzw9aCRDvchpok6C+4TXC57btc4bJtmKQWOHQxOVKen1ZfVqBUuCZ/wuqdX5GHsD0NRSr9XTP+5ID1ZZQBXw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-gamut-mapping@2.0.6': + resolution: {integrity: sha512-0ke7fmXfc8H+kysZz246yjirAH6JFhyX9GTlyRnM0exHO80XcA9zeJpy5pOp5zo/AZiC/q5Pf+Hw7Pd6/uAoYA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-gradients-interpolation-method@5.0.6': + resolution: {integrity: sha512-Itrbx6SLUzsZ6Mz3VuOlxhbfuyLTogG5DwEF1V8dAi24iMuvQPIHd7Ti+pNDp7j6WixndJGZaoNR0f9VSzwuTg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-hwb-function@4.0.6': + resolution: {integrity: sha512-927Pqy3a1uBP7U8sTfaNdZVB0mNXzIrJO/GZ8us9219q9n06gOqCdfZ0E6d1P66Fm0fYHvxfDbfcUuwAn5UwhQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-ic-unit@4.0.0': + resolution: {integrity: sha512-9QT5TDGgx7wD3EEMN3BSUG6ckb6Eh5gSPT5kZoVtUuAonfPmLDJyPhqR4ntPpMYhUKAMVKAg3I/AgzqHMSeLhA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-initial@2.0.0': + resolution: {integrity: sha512-dv2lNUKR+JV+OOhZm9paWzYBXOCi+rJPqJ2cJuhh9xd8USVrd0cBEPczla81HNOyThMQWeCcdln3gZkQV2kYxA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-is-pseudo-class@5.0.1': + resolution: {integrity: sha512-JLp3POui4S1auhDR0n8wHd/zTOWmMsmK3nQd3hhL6FhWPaox5W7j1se6zXOG/aP07wV2ww0lxbKYGwbBszOtfQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-light-dark-function@2.0.7': + resolution: {integrity: sha512-ZZ0rwlanYKOHekyIPaU+sVm3BEHCe+Ha0/px+bmHe62n0Uc1lL34vbwrLYn6ote8PHlsqzKeTQdIejQCJ05tfw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-logical-float-and-clear@3.0.0': + resolution: {integrity: sha512-SEmaHMszwakI2rqKRJgE+8rpotFfne1ZS6bZqBoQIicFyV+xT1UF42eORPxJkVJVrH9C0ctUgwMSn3BLOIZldQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-logical-overflow@2.0.0': + resolution: {integrity: sha512-spzR1MInxPuXKEX2csMamshR4LRaSZ3UXVaRGjeQxl70ySxOhMpP2252RAFsg8QyyBXBzuVOOdx1+bVO5bPIzA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-logical-overscroll-behavior@2.0.0': + resolution: {integrity: sha512-e/webMjoGOSYfqLunyzByZj5KKe5oyVg/YSbie99VEaSDE2kimFm0q1f6t/6Jo+VVCQ/jbe2Xy+uX+C4xzWs4w==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-logical-resize@3.0.0': + resolution: {integrity: sha512-DFbHQOFW/+I+MY4Ycd/QN6Dg4Hcbb50elIJCfnwkRTCX05G11SwViI5BbBlg9iHRl4ytB7pmY5ieAFk3ws7yyg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-logical-viewport-units@3.0.3': + resolution: {integrity: sha512-OC1IlG/yoGJdi0Y+7duz/kU/beCwO+Gua01sD6GtOtLi7ByQUpcIqs7UE/xuRPay4cHgOMatWdnDdsIDjnWpPw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-media-minmax@2.0.5': + resolution: {integrity: sha512-sdh5i5GToZOIAiwhdntRWv77QDtsxP2r2gXW/WbLSCoLr00KTq/yiF1qlQ5XX2+lmiFa8rATKMcbwl3oXDMNew==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-media-queries-aspect-ratio-number-values@3.0.4': + resolution: {integrity: sha512-AnGjVslHMm5xw9keusQYvjVWvuS7KWK+OJagaG0+m9QnIjZsrysD2kJP/tr/UJIyYtMCtu8OkUd+Rajb4DqtIQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-nested-calc@4.0.0': + resolution: {integrity: sha512-jMYDdqrQQxE7k9+KjstC3NbsmC063n1FTPLCgCRS2/qHUbHM0mNy9pIn4QIiQGs9I/Bg98vMqw7mJXBxa0N88A==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-normalize-display-values@4.0.0': + resolution: {integrity: sha512-HlEoG0IDRoHXzXnkV4in47dzsxdsjdz6+j7MLjaACABX2NfvjFS6XVAnpaDyGesz9gK2SC7MbNwdCHusObKJ9Q==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-oklab-function@4.0.6': + resolution: {integrity: sha512-Hptoa0uX+XsNacFBCIQKTUBrFKDiplHan42X73EklG6XmQLG7/aIvxoNhvZ7PvOWMt67Pw3bIlUY2nD6p5vL8A==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-progressive-custom-properties@4.0.0': + resolution: {integrity: sha512-XQPtROaQjomnvLUSy/bALTR5VCtTVUFwYs1SblvYgLSeTo2a/bMNwUwo2piXw5rTv/FEYiy5yPSXBqg9OKUx7Q==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-random-function@1.0.1': + resolution: {integrity: sha512-Ab/tF8/RXktQlFwVhiC70UNfpFQRhtE5fQQoP2pO+KCPGLsLdWFiOuHgSRtBOqEshCVAzR4H6o38nhvRZq8deA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-relative-color-syntax@3.0.6': + resolution: {integrity: sha512-yxP618Xb+ji1I624jILaYM62uEmZcmbdmFoZHoaThw896sq0vU39kqTTF+ZNic9XyPtPMvq0vyvbgmHaszq8xg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-scope-pseudo-class@4.0.1': + resolution: {integrity: sha512-IMi9FwtH6LMNuLea1bjVMQAsUhFxJnyLSgOp/cpv5hrzWmrUYU5fm0EguNDIIOHUqzXode8F/1qkC/tEo/qN8Q==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-sign-functions@1.1.0': + resolution: {integrity: sha512-SLcc20Nujx/kqbSwDmj6oaXgpy3UjFhBy1sfcqPgDkHfOIfUtUVH7OXO+j7BU4v/At5s61N5ZX6shvgPwluhsA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-stepped-value-functions@4.0.5': + resolution: {integrity: sha512-G6SJ6hZJkhxo6UZojVlLo14MohH4J5J7z8CRBrxxUYy9JuZiIqUo5TBYyDGcE0PLdzpg63a7mHSJz3VD+gMwqw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-text-decoration-shorthand@4.0.1': + resolution: {integrity: sha512-xPZIikbx6jyzWvhms27uugIc0I4ykH4keRvoa3rxX5K7lEhkbd54rjj/dv60qOCTisoS+3bmwJTeyV1VNBrXaw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-trigonometric-functions@4.0.5': + resolution: {integrity: sha512-/YQThYkt5MLvAmVu7zxjhceCYlKrYddK6LEmK5I4ojlS6BmO9u2yO4+xjXzu2+NPYmHSTtP4NFSamBCMmJ1NJA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/postcss-unset-value@4.0.0': + resolution: {integrity: sha512-cBz3tOCI5Fw6NIFEwU3RiwK6mn3nKegjpJuzCndoGq3BZPkUjnsq7uQmIeMNeMbMk7YD2MfKcgCpZwX5jyXqCA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@csstools/selector-resolve-nested@3.0.0': + resolution: {integrity: sha512-ZoK24Yku6VJU1gS79a5PFmC8yn3wIapiKmPgun0hZgEI5AOqgH2kiPRsPz1qkGv4HL+wuDLH83yQyk6inMYrJQ==} + engines: {node: '>=18'} + peerDependencies: + postcss-selector-parser: ^7.0.0 + + '@csstools/selector-specificity@5.0.0': + resolution: {integrity: sha512-PCqQV3c4CoVm3kdPhyeZ07VmBRdH2EpMFA/pd9OASpOEC3aXNGoqPDAZ80D0cLpMBxnmk0+yNhGsEx31hq7Gtw==} + engines: {node: '>=18'} + peerDependencies: + postcss-selector-parser: ^7.0.0 + + '@csstools/utilities@2.0.0': + resolution: {integrity: sha512-5VdOr0Z71u+Yp3ozOx8T11N703wIFGVRgOWbOZMKgglPJsWA54MRIoMNVMa7shUToIhx5J8vX4sOZgD2XiihiQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + '@discoveryjs/json-ext@0.5.7': + resolution: {integrity: sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==} + engines: {node: '>=10.0.0'} + + '@docsearch/css@3.8.0': + resolution: {integrity: sha512-pieeipSOW4sQ0+bE5UFC51AOZp9NGxg89wAlZ1BAQFaiRAGK1IKUaPQ0UGZeNctJXyqZ1UvBtOQh2HH+U5GtmA==} + + '@docsearch/react@3.8.0': + resolution: {integrity: sha512-WnFK720+iwTVt94CxY3u+FgX6exb3BfN5kE9xUY6uuAH/9W/UFboBZFLlrw/zxFRHoHZCOXRtOylsXF+6LHI+Q==} + peerDependencies: + '@types/react': '>= 16.8.0 < 19.0.0' + react: '>= 16.8.0 < 19.0.0' + react-dom: '>= 16.8.0 < 19.0.0' + search-insights: '>= 1 < 3' + peerDependenciesMeta: + '@types/react': + optional: true + react: + optional: true + react-dom: + optional: true + search-insights: + optional: true + + '@docusaurus/babel@3.6.3': + resolution: {integrity: sha512-7dW9Hat9EHYCVicFXYA4hjxBY38+hPuCURL8oRF9fySRm7vzNWuEOghA1TXcykuXZp0HLG2td4RhDxCvGG7tNw==} + engines: {node: '>=18.0'} + + '@docusaurus/bundler@3.6.3': + resolution: {integrity: sha512-47JLuc8D4wA+6VOvmMd5fUC9rFppBQpQOnxDYiVXffm/DeV/wmm3sbpNd5Y+O+G2+nevLTRnvCm/qyancv0Y3A==} + engines: {node: '>=18.0'} + peerDependencies: + '@docusaurus/faster': '*' + peerDependenciesMeta: + '@docusaurus/faster': + optional: true + + '@docusaurus/core@3.6.3': + resolution: {integrity: sha512-xL7FRY9Jr5DWqB6pEnqgKqcMPJOX5V0pgWXi5lCiih11sUBmcFKM7c3+GyxcVeeWFxyYSDP3grLTWqJoP4P9Vw==} + engines: {node: '>=18.0'} + hasBin: true + peerDependencies: + '@mdx-js/react': ^3.0.0 + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/cssnano-preset@3.6.3': + resolution: {integrity: sha512-qP7SXrwZ+23GFJdPN4aIHQrZW+oH/7tzwEuc/RNL0+BdZdmIjYQqUxdXsjE4lFxLNZjj0eUrSNYIS6xwfij+5Q==} + engines: {node: '>=18.0'} + + '@docusaurus/faster@3.6.3': + resolution: {integrity: sha512-cHad4m/SPDEMRHJTLsGCe194NVYwD4D3ebCd1WvjJtbq7EJSkZ0u7WULY9pccQfHcv01tbrdUixzzJn0jVAWVg==} + engines: {node: '>=18.0'} + peerDependencies: + '@docusaurus/types': '*' + + '@docusaurus/logger@3.6.3': + resolution: {integrity: sha512-xSubJixcNyMV9wMV4q0s47CBz3Rlc5jbcCCuij8pfQP8qn/DIpt0ks8W6hQWzHAedg/J/EwxxUOUrnEoKzJo8g==} + engines: {node: '>=18.0'} + + '@docusaurus/lqip-loader@3.6.3': + resolution: {integrity: sha512-GlQIhVpskcD7T1Lm/eYR+T0ZurEly3291t/KIJCRZcl3ggVcpRlPDXVx3X2o6O5ESClEt5V5ev0i1J9UaCw8IQ==} + engines: {node: '>=18.0'} + + '@docusaurus/mdx-loader@3.6.3': + resolution: {integrity: sha512-3iJdiDz9540ppBseeI93tWTDtUGVkxzh59nMq4ignylxMuXBLK8dFqVeaEor23v1vx6TrGKZ2FuLaTB+U7C0QQ==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/module-type-aliases@3.6.3': + resolution: {integrity: sha512-MjaXX9PN/k5ugNvfRZdWyKWq4FsrhN4LEXaj0pEmMebJuBNlFeGyKQUa9DRhJHpadNaiMLrbo9m3U7Ig5YlsZg==} + peerDependencies: + react: '*' + react-dom: '*' + + '@docusaurus/plugin-content-blog@3.6.3': + resolution: {integrity: sha512-k0ogWwwJU3pFRFfvW1kRVHxzf2DutLGaaLjAnHVEU6ju+aRP0Z5ap/13DHyPOfHeE4WKpn/M0TqjdwZAcY3kAw==} + engines: {node: '>=18.0'} + peerDependencies: + '@docusaurus/plugin-content-docs': '*' + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-content-docs@3.6.3': + resolution: {integrity: sha512-r2wS8y/fsaDcxkm20W5bbYJFPzdWdEaTWVYjNxlHlcmX086eqQR1Fomlg9BHTJ0dLXPzAlbC8EN4XqMr3QzNCQ==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-content-pages@3.6.3': + resolution: {integrity: sha512-eHrmTgjgLZsuqfsYr5X2xEwyIcck0wseSofWrjTwT9FLOWp+KDmMAuVK+wRo7sFImWXZk3oV/xX/g9aZrhD7OA==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-debug@3.6.3': + resolution: {integrity: sha512-zB9GXfIZNPRfzKnNjU6xGVrqn9bPXuGhpjgsuc/YtcTDjnjhasg38NdYd5LEqXex5G/zIorQgWB3n6x/Ut62vQ==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-google-analytics@3.6.3': + resolution: {integrity: sha512-rCDNy1QW8Dag7nZq67pcum0bpFLrwvxJhYuVprhFh8BMBDxV0bY+bAkGHbSf68P3Bk9C3hNOAXX1srGLIDvcTA==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-google-gtag@3.6.3': + resolution: {integrity: sha512-+OyDvhM6rqVkQOmLVkQWVJAizEEfkPzVWtIHXlWPOCFGK9X4/AWeBSrU0WG4iMg9Z4zD4YDRrU+lvI4s6DSC+w==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-google-tag-manager@3.6.3': + resolution: {integrity: sha512-1M6UPB13gWUtN2UHX083/beTn85PlRI9ABItTl/JL1FJ5dJTWWFXXsHf9WW/6hrVwthwTeV/AGbGKvLKV+IlCA==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/plugin-ideal-image@3.6.3': + resolution: {integrity: sha512-y5Pi4UH8wsFUEFPzjzo1GEtb9vfi5VfWTH/ONifDW84ldYaZBPzVM4AIVWcuNPlYG+p4eYwHE4eTuJFe2iupKQ==} + engines: {node: '>=18.0'} + peerDependencies: + jimp: '*' + react: ^18.0.0 + react-dom: ^18.0.0 + peerDependenciesMeta: + jimp: + optional: true + + '@docusaurus/plugin-sitemap@3.6.3': + resolution: {integrity: sha512-94qOO4M9Fwv9KfVQJsgbe91k+fPJ4byf1L3Ez8TUa6TAFPo/BrLwQ80zclHkENlL1824TuxkcMKv33u6eydQCg==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/preset-classic@3.6.3': + resolution: {integrity: sha512-VHSYWROT3flvNNI1SrnMOtW1EsjeHNK9dhU6s9eY5hryZe79lUqnZJyze/ymDe2LXAqzyj6y5oYvyBoZZk6ErA==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/react-loadable@6.0.0': + resolution: {integrity: sha512-YMMxTUQV/QFSnbgrP3tjDzLHRg7vsbMn8e9HAa8o/1iXoiomo48b7sk/kkmWEuWNDPJVlKSJRB6Y2fHqdJk+SQ==} + peerDependencies: + react: '*' + + '@docusaurus/responsive-loader@1.7.0': + resolution: {integrity: sha512-N0cWuVqTRXRvkBxeMQcy/OF2l7GN8rmni5EzR3HpwR+iU2ckYPnziceojcxvvxQ5NqZg1QfEW0tycQgHp+e+Nw==} + engines: {node: '>=12'} + peerDependencies: + jimp: '*' + sharp: '*' + peerDependenciesMeta: + jimp: + optional: true + sharp: + optional: true + + '@docusaurus/theme-classic@3.6.3': + resolution: {integrity: sha512-1RRLK1tSArI2c00qugWYO3jRocjOZwGF1mBzPPylDVRwWCS/rnWWR91ChdbbaxIupRJ+hX8ZBYrwr5bbU0oztQ==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/theme-common@3.6.3': + resolution: {integrity: sha512-b8ZkhczXHDxWWyvz+YJy4t/PlPbEogTTbgnHoflYnH7rmRtyoodTsu8WVM12la5LmlMJBclBXFl29OH8kPE7gg==} + engines: {node: '>=18.0'} + peerDependencies: + '@docusaurus/plugin-content-docs': '*' + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/theme-search-algolia@3.6.3': + resolution: {integrity: sha512-rt+MGCCpYgPyWCGXtbxlwFbTSobu15jWBTPI2LHsHNa5B0zSmOISX6FWYAPt5X1rNDOqMGM0FATnh7TBHRohVA==} + engines: {node: '>=18.0'} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/theme-translations@3.6.3': + resolution: {integrity: sha512-Gb0regclToVlngSIIwUCtBMQBq48qVUaN1XQNKW4XwlsgUyk0vP01LULdqbem7czSwIeBAFXFoORJ0RPX7ht/w==} + engines: {node: '>=18.0'} + + '@docusaurus/types@3.6.3': + resolution: {integrity: sha512-xD9oTGDrouWzefkhe9ogB2fDV96/82cRpNGx2HIvI5L87JHNhQVIWimQ/3JIiiX/TEd5S9s+VO6FFguwKNRVow==} + peerDependencies: + react: ^18.0.0 + react-dom: ^18.0.0 + + '@docusaurus/utils-common@3.6.3': + resolution: {integrity: sha512-v4nKDaANLgT3pMBewHYEMAl/ufY0LkXao1QkFWzI5huWFOmNQ2UFzv2BiKeHX5Ownis0/w6cAyoxPhVdDonlSQ==} + engines: {node: '>=18.0'} + + '@docusaurus/utils-validation@3.6.3': + resolution: {integrity: sha512-bhEGGiN5BE38h21vjqD70Gxg++j+PfYVddDUE5UFvLDup68QOcpD33CLr+2knPorlxRbEaNfz6HQDUMQ3HuqKw==} + engines: {node: '>=18.0'} + + '@docusaurus/utils@3.6.3': + resolution: {integrity: sha512-0R/FR3bKVl4yl8QwbL4TYFfR+OXBRpVUaTJdENapBGR3YMwfM6/JnhGilWQO8AOwPJGtGoDK7ib8+8UF9f3OZQ==} + engines: {node: '>=18.0'} + + '@hapi/hoek@9.3.0': + resolution: {integrity: sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ==} + + '@hapi/topo@5.1.0': + resolution: {integrity: sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg==} + + '@jest/schemas@29.6.3': + resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} + + '@jest/types@29.6.3': + resolution: {integrity: sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} + + '@jridgewell/gen-mapping@0.3.5': + resolution: {integrity: sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==} + engines: {node: '>=6.0.0'} + + '@jridgewell/resolve-uri@3.1.2': + resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==} + engines: {node: '>=6.0.0'} + + '@jridgewell/set-array@1.2.1': + resolution: {integrity: sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==} + engines: {node: '>=6.0.0'} + + '@jridgewell/source-map@0.3.6': + resolution: {integrity: sha512-1ZJTZebgqllO79ue2bm3rIGud/bOe0pP5BjSRCRxxYkEZS8STV7zN84UBbiYu7jy+eCKSnVIUgoWWE/tt+shMQ==} + + '@jridgewell/sourcemap-codec@1.5.0': + resolution: {integrity: sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==} + + '@jridgewell/trace-mapping@0.3.25': + resolution: {integrity: sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==} + + '@leichtgewicht/ip-codec@2.0.5': + resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==} + + '@mdx-js/mdx@3.1.0': + resolution: {integrity: sha512-/QxEhPAvGwbQmy1Px8F899L5Uc2KZ6JtXwlCgJmjSTBedwOZkByYcBG4GceIGPXRDsmfxhHazuS+hlOShRLeDw==} + + '@mdx-js/react@3.1.0': + resolution: {integrity: sha512-QjHtSaoameoalGnKDT3FoIl4+9RwyTmo9ZJGBdLOks/YOiWHoRDI3PUwEzOE7kEmGcV3AFcp9K6dYu9rEuKLAQ==} + peerDependencies: + '@types/react': '>=16' + react: '>=16' + + '@module-federation/runtime-tools@0.5.1': + resolution: {integrity: sha512-nfBedkoZ3/SWyO0hnmaxuz0R0iGPSikHZOAZ0N/dVSQaIzlffUo35B5nlC2wgWIc0JdMZfkwkjZRrnuuDIJbzg==} + + '@module-federation/runtime@0.5.1': + resolution: {integrity: sha512-xgiMUWwGLWDrvZc9JibuEbXIbhXg6z2oUkemogSvQ4LKvrl/n0kbqP1Blk669mXzyWbqtSp6PpvNdwaE1aN5xQ==} + + '@module-federation/sdk@0.5.1': + resolution: {integrity: sha512-exvchtjNURJJkpqjQ3/opdbfeT2wPKvrbnGnyRkrwW5o3FH1LaST1tkiNviT6OXTexGaVc2DahbdniQHVtQ7pA==} + + '@module-federation/webpack-bundler-runtime@0.5.1': + resolution: {integrity: sha512-mMhRFH0k2VjwHt3Jol9JkUsmI/4XlrAoBG3E0o7HoyoPYv1UFOWyqAflfANcUPgbYpvqmyLzDcO+3IT36LXnrA==} + + '@nodelib/fs.scandir@2.1.5': + resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==} + engines: {node: '>= 8'} + + '@nodelib/fs.stat@2.0.5': + resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==} + engines: {node: '>= 8'} + + '@nodelib/fs.walk@1.2.8': + resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==} + engines: {node: '>= 8'} + + '@pnpm/config.env-replace@1.1.0': + resolution: {integrity: sha512-htyl8TWnKL7K/ESFa1oW2UB5lVDxuF5DpM7tBi6Hu2LNL3mWkIzNLG6N4zoCUP1lCKNxWy/3iu8mS8MvToGd6w==} + engines: {node: '>=12.22.0'} + + '@pnpm/network.ca-file@1.0.2': + resolution: {integrity: sha512-YcPQ8a0jwYU9bTdJDpXjMi7Brhkr1mXsXrUJvjqM2mQDgkRiz8jFaQGOdaLxgjtUfQgZhKy/O3cG/YwmgKaxLA==} + engines: {node: '>=12.22.0'} + + '@pnpm/npm-conf@2.3.1': + resolution: {integrity: sha512-c83qWb22rNRuB0UaVCI0uRPNRr8Z0FWnEIvT47jiHAmOIUHbBOg5XvV7pM5x+rKn9HRpjxquDbXYSXr3fAKFcw==} + engines: {node: '>=12'} + + '@polka/url@1.0.0-next.28': + resolution: {integrity: sha512-8LduaNlMZGwdZ6qWrKlfa+2M4gahzFkprZiAt2TF8uS0qQgBizKXpXURqvTJ4WtmupWxaLqjRb2UCTe72mu+Aw==} + + '@rspack/binding-darwin-arm64@1.1.6': + resolution: {integrity: sha512-x9dxm2yyiMuL1FBwvWNNMs2/mEUJmRoSRgYb8pblR7HDaTRORrjBFCqhaYlGyAqtQaeUy7o2VAQlE0BavIiFYA==} + cpu: [arm64] + os: [darwin] + + '@rspack/binding-darwin-x64@1.1.6': + resolution: {integrity: sha512-o0seilveftGiDjy3VPxug20HmAgYyQbNEuagR3i93/t/PT/eWXHnik+C1jjwqcivZL1Zllqvy4tbZw393aROEQ==} + cpu: [x64] + os: [darwin] + + '@rspack/binding-linux-arm64-gnu@1.1.6': + resolution: {integrity: sha512-4atnoknJx/c3KaQElsMIxHMpPf2jcRRdWsH/SdqJIRSrkWWakMK9Yv4TFwH680I4HDTMf1XLboMVScHzW8e+Mg==} + cpu: [arm64] + os: [linux] + + '@rspack/binding-linux-arm64-musl@1.1.6': + resolution: {integrity: sha512-7QMtwUtgFpt3/Y3/X18fSyN+kk4H8ZnZ8tDzQskVWc/j2AQYShZq56XQYqrhClzwujcCVAHauIQ2eiuJ2ASGag==} + cpu: [arm64] + os: [linux] + + '@rspack/binding-linux-x64-gnu@1.1.6': + resolution: {integrity: sha512-MTjDEfPn4TwHoqs5d5Fck06kmXiTHZctGIcRVfrpg0RK0r1NLEHN+oosavRZ9c9H70f34+NmcHk+/qvV4c8lWg==} + cpu: [x64] + os: [linux] + + '@rspack/binding-linux-x64-musl@1.1.6': + resolution: {integrity: sha512-LqDw7PTVr/4ZuGA0izgDQfamfr72USFHltR1Qhy2YVC3JmDmhG/pQi13LHcOLVaGH1xoeyCmEPNJpVizzDxSjg==} + cpu: [x64] + os: [linux] + + '@rspack/binding-win32-arm64-msvc@1.1.6': + resolution: {integrity: sha512-RHApLM93YN0WdHpS35u2cm7VCqZ8Yg3CrNRL16VJtyT9e6MBqeScoe4XIgIWKPm7edFyedYAjLX0wQOApwfjkg==} + cpu: [arm64] + os: [win32] + + '@rspack/binding-win32-ia32-msvc@1.1.6': + resolution: {integrity: sha512-Y6lx4q0eJawRfMPBo/AclTJAPTZ325DSPFBQJB3TnWh9Z2X7P7pQcYc8PHDmfDuYRIdg5WRsQRvVxihSvF7v8w==} + cpu: [ia32] + os: [win32] + + '@rspack/binding-win32-x64-msvc@1.1.6': + resolution: {integrity: sha512-UuCsfhC/yNuU7xLASOxNXcmsXi2ZvBX14GkxvcdChw6q7IIGNYUKXo1zgR8C1PE/6qDSxmLxbRMS+71d0H3HQg==} + cpu: [x64] + os: [win32] + + '@rspack/binding@1.1.6': + resolution: {integrity: sha512-vfeBEgGOYVwqj5cQjGyvdfrr/BEihAHlyIsobL98FZjTF0uig+bj2yJUH5Ib5F0BpIUKVG3Pw0IjlUBqcVpZsQ==} + + '@rspack/core@1.1.6': + resolution: {integrity: sha512-q0VLphOF5VW2FEG7Vbdq3Ke4I74FbELE/8xmKghSalFtULLZ44SoSz8lyotfMim9GXIRFhDokAaH8WICmPxG+g==} + engines: {node: '>=16.0.0'} + peerDependencies: + '@swc/helpers': '>=0.5.1' + peerDependenciesMeta: + '@swc/helpers': + optional: true + + '@rspack/lite-tapable@1.0.1': + resolution: {integrity: sha512-VynGOEsVw2s8TAlLf/uESfrgfrq2+rcXB1muPJYBWbsm1Oa6r5qVQhjA5ggM6z/coYPrsVMgovl3Ff7Q7OCp1w==} + engines: {node: '>=16.0.0'} + + '@sideway/address@4.1.5': + resolution: {integrity: sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q==} + + '@sideway/formula@3.0.1': + resolution: {integrity: sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg==} + + '@sideway/pinpoint@2.0.0': + resolution: {integrity: sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==} + + '@sinclair/typebox@0.27.8': + resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==} + + '@sindresorhus/is@4.6.0': + resolution: {integrity: sha512-t09vSN3MdfsyCHoFcTRCH/iUtG7OJ0CsjzB8cjAmKc/va/kIgeDI/TxsigdncE/4be734m0cvIYwNaV4i2XqAw==} + engines: {node: '>=10'} + + '@sindresorhus/is@5.6.0': + resolution: {integrity: sha512-TV7t8GKYaJWsn00tFDqBw8+Uqmr8A0fRU1tvTQhyZzGv0sJCGRQL3JGMI3ucuKo3XIZdUP+Lx7/gh2t3lewy7g==} + engines: {node: '>=14.16'} + + '@slorber/react-ideal-image@0.0.12': + resolution: {integrity: sha512-u8KiDTEkMA7/KAeA5ywg/P7YG4zuKhWtswfVZDH8R8HXgQsFcHIYU2WaQnGuK/Du7Wdj90I+SdFmajSGFRvoKA==} + engines: {node: '>= 8.9.0', npm: '> 3'} + peerDependencies: + prop-types: '>=15' + react: '>=0.14.x' + react-waypoint: '>=9.0.2' + + '@slorber/remark-comment@1.0.0': + resolution: {integrity: sha512-RCE24n7jsOj1M0UPvIQCHTe7fI0sFL4S2nwKVWwHyVr/wI/H8GosgsJGyhnsZoGFnD/P2hLf1mSbrrgSLN93NA==} + + '@svgr/babel-plugin-add-jsx-attribute@8.0.0': + resolution: {integrity: sha512-b9MIk7yhdS1pMCZM8VeNfUlSKVRhsHZNMl5O9SfaX0l0t5wjdgu4IDzGB8bpnGBBOjGST3rRFVsaaEtI4W6f7g==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-remove-jsx-attribute@8.0.0': + resolution: {integrity: sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0': + resolution: {integrity: sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0': + resolution: {integrity: sha512-KVQ+PtIjb1BuYT3ht8M5KbzWBhdAjjUPdlMtpuw/VjT8coTrItWX6Qafl9+ji831JaJcu6PJNKCV0bp01lBNzQ==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-svg-dynamic-title@8.0.0': + resolution: {integrity: sha512-omNiKqwjNmOQJ2v6ge4SErBbkooV2aAWwaPFs2vUY7p7GhVkzRkJ00kILXQvRhA6miHnNpXv7MRnnSjdRjK8og==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-svg-em-dimensions@8.0.0': + resolution: {integrity: sha512-mURHYnu6Iw3UBTbhGwE/vsngtCIbHE43xCRK7kCw4t01xyGqb2Pd+WXekRRoFOBIY29ZoOhUCTEweDMdrjfi9g==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-transform-react-native-svg@8.1.0': + resolution: {integrity: sha512-Tx8T58CHo+7nwJ+EhUwx3LfdNSG9R2OKfaIXXs5soiy5HtgoAEkDay9LIimLOcG8dJQH1wPZp/cnAv6S9CrR1Q==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-plugin-transform-svg-component@8.0.0': + resolution: {integrity: sha512-DFx8xa3cZXTdb/k3kfPeaixecQLgKh5NVBMwD0AQxOzcZawK4oo1Jh9LbrcACUivsCA7TLG8eeWgrDXjTMhRmw==} + engines: {node: '>=12'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/babel-preset@8.1.0': + resolution: {integrity: sha512-7EYDbHE7MxHpv4sxvnVPngw5fuR6pw79SkcrILHJ/iMpuKySNCl5W1qcwPEpU+LgyRXOaAFgH0KhwD18wwg6ug==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 + + '@svgr/core@8.1.0': + resolution: {integrity: sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA==} + engines: {node: '>=14'} + + '@svgr/hast-util-to-babel-ast@8.0.0': + resolution: {integrity: sha512-EbDKwO9GpfWP4jN9sGdYwPBU0kdomaPIL2Eu4YwmgP+sJeXT+L7bMwJUBnhzfH8Q2qMBqZ4fJwpCyYsAN3mt2Q==} + engines: {node: '>=14'} + + '@svgr/plugin-jsx@8.1.0': + resolution: {integrity: sha512-0xiIyBsLlr8quN+WyuxooNW9RJ0Dpr8uOnH/xrCVO8GLUcwHISwj1AG0k+LFzteTkAA0GbX0kj9q6Dk70PTiPA==} + engines: {node: '>=14'} + peerDependencies: + '@svgr/core': '*' + + '@svgr/plugin-svgo@8.1.0': + resolution: {integrity: sha512-Ywtl837OGO9pTLIN/onoWLmDQ4zFUycI1g76vuKGEz6evR/ZTJlJuz3G/fIkb6OVBJ2g0o6CGJzaEjfmEo3AHA==} + engines: {node: '>=14'} + peerDependencies: + '@svgr/core': '*' + + '@svgr/webpack@8.1.0': + resolution: {integrity: sha512-LnhVjMWyMQV9ZmeEy26maJk+8HTIbd59cH4F2MJ439k9DqejRisfFNGAPvRYlKETuh9LrImlS8aKsBgKjMA8WA==} + engines: {node: '>=14'} + + '@swc/core-darwin-arm64@1.10.1': + resolution: {integrity: sha512-NyELPp8EsVZtxH/mEqvzSyWpfPJ1lugpTQcSlMduZLj1EASLO4sC8wt8hmL1aizRlsbjCX+r0PyL+l0xQ64/6Q==} + engines: {node: '>=10'} + cpu: [arm64] + os: [darwin] + + '@swc/core-darwin-x64@1.10.1': + resolution: {integrity: sha512-L4BNt1fdQ5ZZhAk5qoDfUnXRabDOXKnXBxMDJ+PWLSxOGBbWE6aJTnu4zbGjJvtot0KM46m2LPAPY8ttknqaZA==} + engines: {node: '>=10'} + cpu: [x64] + os: [darwin] + + '@swc/core-linux-arm-gnueabihf@1.10.1': + resolution: {integrity: sha512-Y1u9OqCHgvVp2tYQAJ7hcU9qO5brDMIrA5R31rwWQIAKDkJKtv3IlTHF0hrbWk1wPR0ZdngkQSJZple7G+Grvw==} + engines: {node: '>=10'} + cpu: [arm] + os: [linux] + + '@swc/core-linux-arm64-gnu@1.10.1': + resolution: {integrity: sha512-tNQHO/UKdtnqjc7o04iRXng1wTUXPgVd8Y6LI4qIbHVoVPwksZydISjMcilKNLKIwOoUQAkxyJ16SlOAeADzhQ==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + + '@swc/core-linux-arm64-musl@1.10.1': + resolution: {integrity: sha512-x0L2Pd9weQ6n8dI1z1Isq00VHFvpBClwQJvrt3NHzmR+1wCT/gcYl1tp9P5xHh3ldM8Cn4UjWCw+7PaUgg8FcQ==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + + '@swc/core-linux-x64-gnu@1.10.1': + resolution: {integrity: sha512-yyYEwQcObV3AUsC79rSzN9z6kiWxKAVJ6Ntwq2N9YoZqSPYph+4/Am5fM1xEQYf/kb99csj0FgOelomJSobxQA==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + + '@swc/core-linux-x64-musl@1.10.1': + resolution: {integrity: sha512-tcaS43Ydd7Fk7sW5ROpaf2Kq1zR+sI5K0RM+0qYLYYurvsJruj3GhBCaiN3gkzd8m/8wkqNqtVklWaQYSDsyqA==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + + '@swc/core-win32-arm64-msvc@1.10.1': + resolution: {integrity: sha512-D3Qo1voA7AkbOzQ2UGuKNHfYGKL6eejN8VWOoQYtGHHQi1p5KK/Q7V1ku55oxXBsj79Ny5FRMqiRJpVGad7bjQ==} + engines: {node: '>=10'} + cpu: [arm64] + os: [win32] + + '@swc/core-win32-ia32-msvc@1.10.1': + resolution: {integrity: sha512-WalYdFoU3454Og+sDKHM1MrjvxUGwA2oralknXkXL8S0I/8RkWZOB++p3pLaGbTvOO++T+6znFbQdR8KRaa7DA==} + engines: {node: '>=10'} + cpu: [ia32] + os: [win32] + + '@swc/core-win32-x64-msvc@1.10.1': + resolution: {integrity: sha512-JWobfQDbTnoqaIwPKQ3DVSywihVXlQMbDuwik/dDWlj33A8oEHcjPOGs4OqcA3RHv24i+lfCQpM3Mn4FAMfacA==} + engines: {node: '>=10'} + cpu: [x64] + os: [win32] + + '@swc/core@1.10.1': + resolution: {integrity: sha512-rQ4dS6GAdmtzKiCRt3LFVxl37FaY1cgL9kSUTnhQ2xc3fmHOd7jdJK/V4pSZMG1ruGTd0bsi34O2R0Olg9Zo/w==} + engines: {node: '>=10'} + peerDependencies: + '@swc/helpers': '*' + peerDependenciesMeta: + '@swc/helpers': + optional: true + + '@swc/counter@0.1.3': + resolution: {integrity: sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ==} + + '@swc/html-darwin-arm64@1.10.1': + resolution: {integrity: sha512-Cp9yco2soX+RPbKRVn190CmMWghhX5c0SWabqvYRl6AjGzFH/2fDFeib4QRjWDdvJfiInFOMAu5WryVAZm8C6g==} + engines: {node: '>=10'} + cpu: [arm64] + os: [darwin] + + '@swc/html-darwin-x64@1.10.1': + resolution: {integrity: sha512-G3QzvPMzUHTkU9kJ6lt6lGPNXLvaPSb2YaAL6XQo0O5K+tXavvEgiaFZ0fkTYgvddd6FKPyt2eLemdXVwKGIdg==} + engines: {node: '>=10'} + cpu: [x64] + os: [darwin] + + '@swc/html-linux-arm-gnueabihf@1.10.1': + resolution: {integrity: sha512-aj3eYvH0VBfBmuW/BtVrhjdFAlQGSaKGTNXC1iUM5KA4S53I3FaBtMC8GG6fk5N6AeAoCtSbNmMXOQrPR0JkoQ==} + engines: {node: '>=10'} + cpu: [arm] + os: [linux] + + '@swc/html-linux-arm64-gnu@1.10.1': + resolution: {integrity: sha512-K9/8klH+S38CVQgkIND/vS3WsOvBGWR/rQum9NP3IHzrD+EJJKy4GYBSbUiw+lRZqNeXAaxfw2DL+DUCIyDotQ==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + + '@swc/html-linux-arm64-musl@1.10.1': + resolution: {integrity: sha512-P84qACz2YTTl1B2JDCJQHOCxPwea7RthNa0XcPhU73qoOx852PZcLpPNUF0JJ3pq9I5XgcDj5R9Fav7AuZl1ig==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + + '@swc/html-linux-x64-gnu@1.10.1': + resolution: {integrity: sha512-wfiu2xYTKSpSh5bzTYw9uB9Bx+K4CBwF0GefdRfalOeQwOjmBhs00SqWdt707uFGJZkAw4nMkr62gxGSyLAxYQ==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + + '@swc/html-linux-x64-musl@1.10.1': + resolution: {integrity: sha512-NGgYjGSjTmkDn5RRMvA6HrZ1w6c/kNdFRBwLGFXpHvoDSwDRX6oAiOFdsWUzA5BSfGhNWuEVEx93tihlxT7zbA==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + + '@swc/html-win32-arm64-msvc@1.10.1': + resolution: {integrity: sha512-YxysgMhC54dK6kUzHQKfGPhmTcCi19Zcpjnr7jaqpg/mYhDPFX1bE2cQtBPFh4Q7A7iTdpAkDZS7Zi9mkzrHQA==} + engines: {node: '>=10'} + cpu: [arm64] + os: [win32] + + '@swc/html-win32-ia32-msvc@1.10.1': + resolution: {integrity: sha512-e1enhKE9xnHSJ3eMzyUf1yPCiTPMGjNrYi985geBiJEz5mXX39QpF7JgBFp3K5hZpZ9livuUd4LgqCPLue6wXQ==} + engines: {node: '>=10'} + cpu: [ia32] + os: [win32] + + '@swc/html-win32-x64-msvc@1.10.1': + resolution: {integrity: sha512-v/XgvVSf+6xesozDZGH3PsVc6x7wMZrwN+Tc+1yHM1DwWbxz0Pa7ymm66jhaGrL8nXk9fAOBLD0pxPLn/O4g8g==} + engines: {node: '>=10'} + cpu: [x64] + os: [win32] + + '@swc/html@1.10.1': + resolution: {integrity: sha512-9KGXAEMc0b+zpQzLoXsb6VSkeCjHfkaupuKpZqE4QjKJlb6j/tsAANlf8aFgaiwNuZealeKBE+hYouWt/bDCcw==} + engines: {node: '>=14'} + + '@swc/types@0.1.17': + resolution: {integrity: sha512-V5gRru+aD8YVyCOMAjMpWR1Ui577DD5KSJsHP8RAxopAH22jFz6GZd/qxqjO6MJHQhcsjvjOFXyDhyLQUnMveQ==} + + '@szmarczak/http-timer@5.0.1': + resolution: {integrity: sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw==} + engines: {node: '>=14.16'} + + '@trysound/sax@0.2.0': + resolution: {integrity: sha512-L7z9BgrNEcYyUYtF+HaEfiS5ebkh9jXqbszz7pC0hRBPaatV0XjSD3+eHrpqFemQfgwiFF0QPIarnIihIDn7OA==} + engines: {node: '>=10.13.0'} + + '@types/acorn@4.0.6': + resolution: {integrity: sha512-veQTnWP+1D/xbxVrPC3zHnCZRjSrKfhbMUlEA43iMZLu7EsnTtkJklIuwrCPbOi8YkvDQAiW05VQQFvvz9oieQ==} + + '@types/body-parser@1.19.5': + resolution: {integrity: sha512-fB3Zu92ucau0iQ0JMCFQE7b/dv8Ot07NI3KaZIkIUNXq82k4eBAqUaneXfleGY9JWskeS9y+u0nXMyspcuQrCg==} + + '@types/bonjour@3.5.13': + resolution: {integrity: sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ==} + + '@types/connect-history-api-fallback@1.5.4': + resolution: {integrity: sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw==} + + '@types/connect@3.4.38': + resolution: {integrity: sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug==} + + '@types/debug@4.1.12': + resolution: {integrity: sha512-vIChWdVG3LG1SMxEvI/AK+FWJthlrqlTu7fbrlywTkkaONwk/UAGaULXRlf8vkzFBLVm0zkMdCquhL5aOjhXPQ==} + + '@types/eslint-scope@3.7.7': + resolution: {integrity: sha512-MzMFlSLBqNF2gcHWO0G1vP/YQyfvrxZ0bF+u7mzUdZ1/xK4A4sru+nraZz5i3iEIk1l1uyicaDVTB4QbbEkAYg==} + + '@types/eslint@9.6.1': + resolution: {integrity: sha512-FXx2pKgId/WyYo2jXw63kk7/+TY7u7AziEJxJAnSFzHlqTAS3Ync6SvgYAN/k4/PQpnnVuzoMuVnByKK2qp0ag==} + + '@types/estree-jsx@1.0.5': + resolution: {integrity: sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==} + + '@types/estree@1.0.6': + resolution: {integrity: sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw==} + + '@types/express-serve-static-core@4.19.6': + resolution: {integrity: sha512-N4LZ2xG7DatVqhCZzOGb1Yi5lMbXSZcmdLDe9EzSndPV2HpWYWzRbaerl2n27irrm94EPpprqa8KpskPT085+A==} + + '@types/express-serve-static-core@5.0.2': + resolution: {integrity: sha512-vluaspfvWEtE4vcSDlKRNer52DvOGrB2xv6diXy6UKyKW0lqZiWHGNApSyxOv+8DE5Z27IzVvE7hNkxg7EXIcg==} + + '@types/express@4.17.21': + resolution: {integrity: sha512-ejlPM315qwLpaQlQDTjPdsUFSc6ZsP4AN6AlWnogPjQ7CVi7PYF3YVz+CY3jE2pwYf7E/7HlDAN0rV2GxTG0HQ==} + + '@types/gtag.js@0.0.12': + resolution: {integrity: sha512-YQV9bUsemkzG81Ea295/nF/5GijnD2Af7QhEofh7xu+kvCN6RdodgNwwGWXB5GMI3NoyvQo0odNctoH/qLMIpg==} + + '@types/hast@3.0.4': + resolution: {integrity: sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==} + + '@types/history@4.7.11': + resolution: {integrity: sha512-qjDJRrmvBMiTx+jyLxvLfJU7UznFuokDv4f3WRuriHKERccVpFU+8XMQUAbDzoiJCsmexxRExQeMwwCdamSKDA==} + + '@types/html-minifier-terser@6.1.0': + resolution: {integrity: sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg==} + + '@types/http-cache-semantics@4.0.4': + resolution: {integrity: sha512-1m0bIFVc7eJWyve9S0RnuRgcQqF/Xd5QsUZAZeQFr1Q3/p9JWoQQEqmVy+DPTNpGXwhgIetAoYF8JSc33q29QA==} + + '@types/http-errors@2.0.4': + resolution: {integrity: sha512-D0CFMMtydbJAegzOyHjtiKPLlvnm3iTZyZRSZoLq2mRhDdmLfIWOCYPfQJ4cu2erKghU++QvjcUjp/5h7hESpA==} + + '@types/http-proxy@1.17.15': + resolution: {integrity: sha512-25g5atgiVNTIv0LBDTg1H74Hvayx0ajtJPLLcYE3whFv75J0pWNtOBzaXJQgDTmrX1bx5U9YC2w/n65BN1HwRQ==} + + '@types/istanbul-lib-coverage@2.0.6': + resolution: {integrity: sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w==} + + '@types/istanbul-lib-report@3.0.3': + resolution: {integrity: sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA==} + + '@types/istanbul-reports@3.0.4': + resolution: {integrity: sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ==} + + '@types/json-schema@7.0.15': + resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==} + + '@types/mdast@4.0.4': + resolution: {integrity: sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==} + + '@types/mdx@2.0.13': + resolution: {integrity: sha512-+OWZQfAYyio6YkJb3HLxDrvnx6SWWDbC0zVPfBRzUk0/nqoDyf6dNxQi3eArPe8rJ473nobTMQ/8Zk+LxJ+Yuw==} + + '@types/mime@1.3.5': + resolution: {integrity: sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w==} + + '@types/ms@0.7.34': + resolution: {integrity: sha512-nG96G3Wp6acyAgJqGasjODb+acrI7KltPiRxzHPXnP3NgI28bpQDRv53olbqGXbfcgF5aiiHmO3xpwEpS5Ld9g==} + + '@types/node-forge@1.3.11': + resolution: {integrity: sha512-FQx220y22OKNTqaByeBGqHWYz4cl94tpcxeFdvBo3wjG6XPBuZ0BNgNZRV5J5TFmmcsJ4IzsLkmGRiQbnYsBEQ==} + + '@types/node@17.0.45': + resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==} + + '@types/node@22.10.1': + resolution: {integrity: sha512-qKgsUwfHZV2WCWLAnVP1JqnpE6Im6h3Y0+fYgMTasNQ7V++CBX5OT1as0g0f+OyubbFqhf6XVNIsmN4IIhEgGQ==} + + '@types/parse-json@4.0.2': + resolution: {integrity: sha512-dISoDXWWQwUquiKsyZ4Ng+HX2KsPL7LyHKHQwgGFEA3IaKac4Obd+h2a/a6waisAoepJlBcx9paWqjA8/HVjCw==} + + '@types/prismjs@1.26.5': + resolution: {integrity: sha512-AUZTa7hQ2KY5L7AmtSiqxlhWxb4ina0yd8hNbl4TWuqnv/pFP0nDMb3YrfSBf4hJVGLh2YEIBfKaBW/9UEl6IQ==} + + '@types/qs@6.9.17': + resolution: {integrity: sha512-rX4/bPcfmvxHDv0XjfJELTTr+iB+tn032nPILqHm5wbthUUUuVtNGGqzhya9XUxjTP8Fpr0qYgSZZKxGY++svQ==} + + '@types/range-parser@1.2.7': + resolution: {integrity: sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ==} + + '@types/react-router-config@5.0.11': + resolution: {integrity: sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw==} + + '@types/react-router-dom@5.3.3': + resolution: {integrity: sha512-kpqnYK4wcdm5UaWI3fLcELopqLrHgLqNsdpHauzlQktfkHL3npOSwtj1Uz9oKBAzs7lFtVkV8j83voAz2D8fhw==} + + '@types/react-router@5.1.20': + resolution: {integrity: sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q==} + + '@types/react@19.0.1': + resolution: {integrity: sha512-YW6614BDhqbpR5KtUYzTA+zlA7nayzJRA9ljz9CQoxthR0sDisYZLuvSMsil36t4EH/uAt8T52Xb4sVw17G+SQ==} + + '@types/retry@0.12.0': + resolution: {integrity: sha512-wWKOClTTiizcZhXnPY4wikVAwmdYHp8q6DmC+EJUzAMsycb7HB32Kh9RN4+0gExjmPmZSAQjgURXIGATPegAvA==} + + '@types/sax@1.2.7': + resolution: {integrity: sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==} + + '@types/send@0.17.4': + resolution: {integrity: sha512-x2EM6TJOybec7c52BX0ZspPodMsQUd5L6PRwOunVyVUhXiBSKf3AezDL8Dgvgt5o0UfKNfuA0eMLr2wLT4AiBA==} + + '@types/serve-index@1.9.4': + resolution: {integrity: sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug==} + + '@types/serve-static@1.15.7': + resolution: {integrity: sha512-W8Ym+h8nhuRwaKPaDw34QUkwsGi6Rc4yYqvKFo5rm2FUEhCFbzVWrxXUxuKK8TASjWsysJY0nsmNCGhCOIsrOw==} + + '@types/sockjs@0.3.36': + resolution: {integrity: sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q==} + + '@types/unist@2.0.11': + resolution: {integrity: sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==} + + '@types/unist@3.0.3': + resolution: {integrity: sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==} + + '@types/ws@8.5.13': + resolution: {integrity: sha512-osM/gWBTPKgHV8XkTunnegTRIsvF6owmf5w+JtAfOw472dptdm0dlGv4xCt6GwQRcC2XVOvvRE/0bAoQcL2QkA==} + + '@types/yargs-parser@21.0.3': + resolution: {integrity: sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==} + + '@types/yargs@17.0.33': + resolution: {integrity: sha512-WpxBCKWPLr4xSsHgz511rFJAM+wS28w2zEO1QDNY5zM/S8ok70NNfztH0xwhqKyaK0OHCbN98LDAZuy1ctxDkA==} + + '@ungap/structured-clone@1.2.1': + resolution: {integrity: sha512-fEzPV3hSkSMltkw152tJKNARhOupqbH96MZWyRjNaYZOMIzbrTeQDG+MTc6Mr2pgzFQzFxAfmhGDNP5QK++2ZA==} + + '@webassemblyjs/ast@1.14.1': + resolution: {integrity: sha512-nuBEDgQfm1ccRp/8bCQrx1frohyufl4JlbMMZ4P1wpeOfDhF6FQkxZJ1b/e+PLwr6X1Nhw6OLme5usuBWYBvuQ==} + + '@webassemblyjs/floating-point-hex-parser@1.13.2': + resolution: {integrity: sha512-6oXyTOzbKxGH4steLbLNOu71Oj+C8Lg34n6CqRvqfS2O71BxY6ByfMDRhBytzknj9yGUPVJ1qIKhRlAwO1AovA==} + + '@webassemblyjs/helper-api-error@1.13.2': + resolution: {integrity: sha512-U56GMYxy4ZQCbDZd6JuvvNV/WFildOjsaWD3Tzzvmw/mas3cXzRJPMjP83JqEsgSbyrmaGjBfDtV7KDXV9UzFQ==} + + '@webassemblyjs/helper-buffer@1.14.1': + resolution: {integrity: sha512-jyH7wtcHiKssDtFPRB+iQdxlDf96m0E39yb0k5uJVhFGleZFoNw1c4aeIcVUPPbXUVJ94wwnMOAqUHyzoEPVMA==} + + '@webassemblyjs/helper-numbers@1.13.2': + resolution: {integrity: sha512-FE8aCmS5Q6eQYcV3gI35O4J789wlQA+7JrqTTpJqn5emA4U2hvwJmvFRC0HODS+3Ye6WioDklgd6scJ3+PLnEA==} + + '@webassemblyjs/helper-wasm-bytecode@1.13.2': + resolution: {integrity: sha512-3QbLKy93F0EAIXLh0ogEVR6rOubA9AoZ+WRYhNbFyuB70j3dRdwH9g+qXhLAO0kiYGlg3TxDV+I4rQTr/YNXkA==} + + '@webassemblyjs/helper-wasm-section@1.14.1': + resolution: {integrity: sha512-ds5mXEqTJ6oxRoqjhWDU83OgzAYjwsCV8Lo/N+oRsNDmx/ZDpqalmrtgOMkHwxsG0iI//3BwWAErYRHtgn0dZw==} + + '@webassemblyjs/ieee754@1.13.2': + resolution: {integrity: sha512-4LtOzh58S/5lX4ITKxnAK2USuNEvpdVV9AlgGQb8rJDHaLeHciwG4zlGr0j/SNWlr7x3vO1lDEsuePvtcDNCkw==} + + '@webassemblyjs/leb128@1.13.2': + resolution: {integrity: sha512-Lde1oNoIdzVzdkNEAWZ1dZ5orIbff80YPdHx20mrHwHrVNNTjNr8E3xz9BdpcGqRQbAEa+fkrCb+fRFTl/6sQw==} + + '@webassemblyjs/utf8@1.13.2': + resolution: {integrity: sha512-3NQWGjKTASY1xV5m7Hr0iPeXD9+RDobLll3T9d2AO+g3my8xy5peVyjSag4I50mR1bBSN/Ct12lo+R9tJk0NZQ==} + + '@webassemblyjs/wasm-edit@1.14.1': + resolution: {integrity: sha512-RNJUIQH/J8iA/1NzlE4N7KtyZNHi3w7at7hDjvRNm5rcUXa00z1vRz3glZoULfJ5mpvYhLybmVcwcjGrC1pRrQ==} + + '@webassemblyjs/wasm-gen@1.14.1': + resolution: {integrity: sha512-AmomSIjP8ZbfGQhumkNvgC33AY7qtMCXnN6bL2u2Js4gVCg8fp735aEiMSBbDR7UQIj90n4wKAFUSEd0QN2Ukg==} + + '@webassemblyjs/wasm-opt@1.14.1': + resolution: {integrity: sha512-PTcKLUNvBqnY2U6E5bdOQcSM+oVP/PmrDY9NzowJjislEjwP/C4an2303MCVS2Mg9d3AJpIGdUFIQQWbPds0Sw==} + + '@webassemblyjs/wasm-parser@1.14.1': + resolution: {integrity: sha512-JLBl+KZ0R5qB7mCnud/yyX08jWFw5MsoalJ1pQ4EdFlgj9VdXKGuENGsiCIjegI1W7p91rUlcB/LB5yRJKNTcQ==} + + '@webassemblyjs/wast-printer@1.14.1': + resolution: {integrity: sha512-kPSSXE6De1XOR820C90RIo2ogvZG+c3KiHzqUoO/F34Y2shGzesfqv7o57xrxovZJH/MetF5UjroJ/R/3isoiw==} + + '@xtuc/ieee754@1.2.0': + resolution: {integrity: sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==} + + '@xtuc/long@4.2.2': + resolution: {integrity: sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==} + + accepts@1.3.8: + resolution: {integrity: sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==} + engines: {node: '>= 0.6'} + + acorn-jsx@5.3.2: + resolution: {integrity: sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==} + peerDependencies: + acorn: ^6.0.0 || ^7.0.0 || ^8.0.0 + + acorn-walk@8.3.4: + resolution: {integrity: sha512-ueEepnujpqee2o5aIYnvHU6C0A42MNdsIDeqy5BydrkuC5R1ZuUFnm27EeFJGoEHJQgn3uleRvmTXaJgfXbt4g==} + engines: {node: '>=0.4.0'} + + acorn@8.14.0: + resolution: {integrity: sha512-cl669nCJTZBsL97OF4kUQm5g5hC2uihk0NxY3WENAC0TYdILVkAyHymAntgxGkl7K+t0cXIrH5siy5S4XkFycA==} + engines: {node: '>=0.4.0'} + hasBin: true + + address@1.2.2: + resolution: {integrity: sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA==} + engines: {node: '>= 10.0.0'} + + aggregate-error@3.1.0: + resolution: {integrity: sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA==} + engines: {node: '>=8'} + + ajv-formats@2.1.1: + resolution: {integrity: sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==} + peerDependencies: + ajv: ^8.0.0 + peerDependenciesMeta: + ajv: + optional: true + + ajv-keywords@3.5.2: + resolution: {integrity: sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==} + peerDependencies: + ajv: ^6.9.1 + + ajv-keywords@5.1.0: + resolution: {integrity: sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw==} + peerDependencies: + ajv: ^8.8.2 + + ajv@6.12.6: + resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==} + + ajv@8.17.1: + resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==} + + algoliasearch-helper@3.22.6: + resolution: {integrity: sha512-F2gSb43QHyvZmvH/2hxIjbk/uFdO2MguQYTFP7J+RowMW1csjIODMobEnpLI8nbLQuzZnGZdIxl5Bpy1k9+CFQ==} + peerDependencies: + algoliasearch: '>= 3.1 < 6' + + algoliasearch@4.24.0: + resolution: {integrity: sha512-bf0QV/9jVejssFBmz2HQLxUadxk574t4iwjCKp5E7NBzwKkrDEhKPISIIjAU/p6K5qDx3qoeh4+26zWN1jmw3g==} + + algoliasearch@5.17.0: + resolution: {integrity: sha512-BpuFprDFc3Pe9a1ZXLzLeqZ+l8Ur37AfzBswkOB4LwikqnRPbIGdluT/nFc/Xk+u/QMxMzUlTN+izqQJVb5vYA==} + engines: {node: '>= 14.0.0'} + + ansi-align@3.0.1: + resolution: {integrity: sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==} + + ansi-escapes@4.3.2: + resolution: {integrity: sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==} + engines: {node: '>=8'} + + ansi-html-community@0.0.8: + resolution: {integrity: sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==} + engines: {'0': node >= 0.8.0} + hasBin: true + + ansi-regex@5.0.1: + resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==} + engines: {node: '>=8'} + + ansi-regex@6.1.0: + resolution: {integrity: sha512-7HSX4QQb4CspciLpVFwyRe79O3xsIZDDLER21kERQ71oaPodF8jL725AgJMFAYbooIqolJoRLuM81SpeUkpkvA==} + engines: {node: '>=12'} + + ansi-styles@4.3.0: + resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==} + engines: {node: '>=8'} + + ansi-styles@6.2.1: + resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==} + engines: {node: '>=12'} + + anymatch@3.1.3: + resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==} + engines: {node: '>= 8'} + + arg@5.0.2: + resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==} + + argparse@1.0.10: + resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==} + + argparse@2.0.1: + resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==} + + array-flatten@1.1.1: + resolution: {integrity: sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==} + + array-union@2.1.0: + resolution: {integrity: sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==} + engines: {node: '>=8'} + + astring@1.9.0: + resolution: {integrity: sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg==} + hasBin: true + + at-least-node@1.0.0: + resolution: {integrity: sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==} + engines: {node: '>= 4.0.0'} + + autoprefixer@10.4.20: + resolution: {integrity: sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g==} + engines: {node: ^10 || ^12 || >=14} + hasBin: true + peerDependencies: + postcss: ^8.1.0 + + b4a@1.6.7: + resolution: {integrity: sha512-OnAYlL5b7LEkALw87fUVafQw5rVR9RjwGd4KUwNQ6DrrNmaVaUCgLipfVlzrPQ4tWOR9P0IXGNOx50jYCCdSJg==} + + babel-loader@9.2.1: + resolution: {integrity: sha512-fqe8naHt46e0yIdkjUZYqddSXfej3AHajX+CSO5X7oy0EmPc6o5Xh+RClNoHjnieWz9AW4kZxW9yyFMhVB1QLA==} + engines: {node: '>= 14.15.0'} + peerDependencies: + '@babel/core': ^7.12.0 + webpack: '>=5' + + babel-plugin-dynamic-import-node@2.3.3: + resolution: {integrity: sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==} + + babel-plugin-polyfill-corejs2@0.4.12: + resolution: {integrity: sha512-CPWT6BwvhrTO2d8QVorhTCQw9Y43zOu7G9HigcfxvepOU6b8o3tcWad6oVgZIsZCTt42FFv97aA7ZJsbM4+8og==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 + + babel-plugin-polyfill-corejs3@0.10.6: + resolution: {integrity: sha512-b37+KR2i/khY5sKmWNVQAnitvquQbNdWy6lJdsr0kmquCKEEUgMKK4SboVM3HtfnZilfjr4MMQ7vY58FVWDtIA==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 + + babel-plugin-polyfill-regenerator@0.6.3: + resolution: {integrity: sha512-LiWSbl4CRSIa5x/JAU6jZiG9eit9w6mz+yVMFwDE83LAWvt0AfGBoZ7HS/mkhrKuh2ZlzfVZYKoLjXdqw6Yt7Q==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 + + bail@2.0.2: + resolution: {integrity: sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==} + + balanced-match@1.0.2: + resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==} + + bare-events@2.5.0: + resolution: {integrity: sha512-/E8dDe9dsbLyh2qrZ64PEPadOQ0F4gbl1sUJOrmph7xOiIxfY8vwab/4bFLh4Y88/Hk/ujKcrQKc+ps0mv873A==} + + bare-fs@2.3.5: + resolution: {integrity: sha512-SlE9eTxifPDJrT6YgemQ1WGFleevzwY+XAP1Xqgl56HtcrisC2CHCZ2tq6dBpcH2TnNxwUEUGhweo+lrQtYuiw==} + + bare-os@2.4.4: + resolution: {integrity: sha512-z3UiI2yi1mK0sXeRdc4O1Kk8aOa/e+FNWZcTiPB/dfTWyLypuE99LibgRaQki914Jq//yAWylcAt+mknKdixRQ==} + + bare-path@2.1.3: + resolution: {integrity: sha512-lh/eITfU8hrj9Ru5quUp0Io1kJWIk1bTjzo7JH1P5dWmQ2EL4hFUlfI8FonAhSlgIfhn63p84CDY/x+PisgcXA==} + + bare-stream@2.4.2: + resolution: {integrity: sha512-XZ4ln/KV4KT+PXdIWTKjsLY+quqCaEtqqtgGJVPw9AoM73By03ij64YjepK0aQvHSWDb6AfAZwqKaFu68qkrdA==} + + base64-js@1.5.1: + resolution: {integrity: sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==} + + batch@0.6.1: + resolution: {integrity: sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw==} + + big.js@5.2.2: + resolution: {integrity: sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==} + + binary-extensions@2.3.0: + resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==} + engines: {node: '>=8'} + + bl@4.1.0: + resolution: {integrity: sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==} + + body-parser@1.20.3: + resolution: {integrity: sha512-7rAxByjUMqQ3/bHJy7D6OGXvx/MMc4IqBn/X0fcM1QUcAItpZrBEYhWGem+tzXH90c+G01ypMcYJBO9Y30203g==} + engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} + + bonjour-service@1.3.0: + resolution: {integrity: sha512-3YuAUiSkWykd+2Azjgyxei8OWf8thdn8AITIog2M4UICzoqfjlqr64WIjEXZllf/W6vK1goqleSR6brGomxQqA==} + + boolbase@1.0.0: + resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==} + + boxen@6.2.1: + resolution: {integrity: sha512-H4PEsJXfFI/Pt8sjDWbHlQPx4zL/bvSQjcilJmaulGt5mLDorHOHpmdXAJcBcmru7PhYSp/cDMWRko4ZUMFkSw==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + boxen@7.1.1: + resolution: {integrity: sha512-2hCgjEmP8YLWQ130n2FerGv7rYpfBmnmp9Uy2Le1vge6X3gZIfSmEzP5QTDElFxcvVcXlEn8Aq6MU/PZygIOog==} + engines: {node: '>=14.16'} + + brace-expansion@1.1.11: + resolution: {integrity: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==} + + braces@3.0.3: + resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==} + engines: {node: '>=8'} + + browserslist@4.24.2: + resolution: {integrity: sha512-ZIc+Q62revdMcqC6aChtW4jz3My3klmCO1fEmINZY/8J3EpBg5/A/D0AKmBveUh6pgoeycoMkVMko84tuYS+Gg==} + engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7} + hasBin: true + + buffer-from@1.1.2: + resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==} + + buffer@5.7.1: + resolution: {integrity: sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==} + + bytes@3.0.0: + resolution: {integrity: sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw==} + engines: {node: '>= 0.8'} + + bytes@3.1.2: + resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==} + engines: {node: '>= 0.8'} + + cacheable-lookup@7.0.0: + resolution: {integrity: sha512-+qJyx4xiKra8mZrcwhjMRMUhD5NR1R8esPkzIYxX96JiecFoxAXFuz/GpR3+ev4PE1WamHip78wV0vcmPQtp8w==} + engines: {node: '>=14.16'} + + cacheable-request@10.2.14: + resolution: {integrity: sha512-zkDT5WAF4hSSoUgyfg5tFIxz8XQK+25W/TLVojJTMKBaxevLBBtLxgqguAuVQB8PVW79FVjHcU+GJ9tVbDZ9mQ==} + engines: {node: '>=14.16'} + + call-bind-apply-helpers@1.0.1: + resolution: {integrity: sha512-BhYE+WDaywFg2TBWYNXAE+8B1ATnThNBqXHP5nQu0jWJdVvY2hvkpyB3qOmtmDePiS5/BDQ8wASEWGMWRG148g==} + engines: {node: '>= 0.4'} + + call-bind@1.0.8: + resolution: {integrity: sha512-oKlSFMcMwpUg2ednkhQ454wfWiU/ul3CkJe/PEHcTKuiX6RpbehUiFMXu13HalGZxfUwCQzZG747YXBn1im9ww==} + engines: {node: '>= 0.4'} + + callsites@3.1.0: + resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==} + engines: {node: '>=6'} + + camel-case@4.1.2: + resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==} + + camelcase@6.3.0: + resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==} + engines: {node: '>=10'} + + camelcase@7.0.1: + resolution: {integrity: sha512-xlx1yCK2Oc1APsPXDL2LdlNP6+uu8OCDdhOBSVT279M/S+y75O30C2VuD8T2ogdePBBl7PfPF4504tnLgX3zfw==} + engines: {node: '>=14.16'} + + caniuse-api@3.0.0: + resolution: {integrity: sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw==} + + caniuse-lite@1.0.30001687: + resolution: {integrity: sha512-0S/FDhf4ZiqrTUiQ39dKeUjYRjkv7lOZU1Dgif2rIqrTzX/1wV2hfKu9TOm1IHkdSijfLswxTFzl/cvir+SLSQ==} + + ccount@2.0.1: + resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==} + + chalk@4.1.2: + resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==} + engines: {node: '>=10'} + + chalk@5.3.0: + resolution: {integrity: sha512-dLitG79d+GV1Nb/VYcCDFivJeK1hiukt9QjRNVOsUtTy1rR1YJsmpGGTZ3qJos+uw7WmWF4wUwBd9jxjocFC2w==} + engines: {node: ^12.17.0 || ^14.13 || >=16.0.0} + + char-regex@1.0.2: + resolution: {integrity: sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw==} + engines: {node: '>=10'} + + character-entities-html4@2.1.0: + resolution: {integrity: sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==} + + character-entities-legacy@3.0.0: + resolution: {integrity: sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==} + + character-entities@2.0.2: + resolution: {integrity: sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ==} + + character-reference-invalid@2.0.1: + resolution: {integrity: sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==} + + cheerio-select@2.1.0: + resolution: {integrity: sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==} + + cheerio@1.0.0: + resolution: {integrity: sha512-quS9HgjQpdaXOvsZz82Oz7uxtXiy6UIsIQcpBj7HRw2M63Skasm9qlDocAM7jNuaxdhpPU7c4kJN+gA5MCu4ww==} + engines: {node: '>=18.17'} + + cheerio@1.0.0-rc.12: + resolution: {integrity: sha512-VqR8m68vM46BNnuZ5NtnGBKIE/DfN0cRIzg9n40EIq9NOv90ayxLBXA8fXC5gquFRGJSTRqBq25Jt2ECLR431Q==} + engines: {node: '>= 6'} + + chokidar@3.6.0: + resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==} + engines: {node: '>= 8.10.0'} + + chownr@1.1.4: + resolution: {integrity: sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==} + + chrome-trace-event@1.0.4: + resolution: {integrity: sha512-rNjApaLzuwaOTjCiT8lSDdGN1APCiqkChLMJxJPWLunPAt5fy8xgU9/jNOchV84wfIxrA0lRQB7oCT8jrn/wrQ==} + engines: {node: '>=6.0'} + + ci-info@3.9.0: + resolution: {integrity: sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==} + engines: {node: '>=8'} + + clean-css@5.3.3: + resolution: {integrity: sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg==} + engines: {node: '>= 10.0'} + + clean-stack@2.2.0: + resolution: {integrity: sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==} + engines: {node: '>=6'} + + cli-boxes@3.0.0: + resolution: {integrity: sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==} + engines: {node: '>=10'} + + cli-table3@0.6.5: + resolution: {integrity: sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ==} + engines: {node: 10.* || >= 12.*} + + clone-deep@4.0.1: + resolution: {integrity: sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==} + engines: {node: '>=6'} + + clsx@1.2.1: + resolution: {integrity: sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==} + engines: {node: '>=6'} + + clsx@2.1.1: + resolution: {integrity: sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==} + engines: {node: '>=6'} + + collapse-white-space@2.1.0: + resolution: {integrity: sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==} + + color-convert@2.0.1: + resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==} + engines: {node: '>=7.0.0'} + + color-name@1.1.4: + resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==} + + color-string@1.9.1: + resolution: {integrity: sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg==} + + color@4.2.3: + resolution: {integrity: sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A==} + engines: {node: '>=12.5.0'} + + colord@2.9.3: + resolution: {integrity: sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw==} + + colorette@2.0.20: + resolution: {integrity: sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==} + + combine-promises@1.2.0: + resolution: {integrity: sha512-VcQB1ziGD0NXrhKxiwyNbCDmRzs/OShMs2GqW2DlU2A/Sd0nQxE1oWDAE5O0ygSx5mgQOn9eIFh7yKPgFRVkPQ==} + engines: {node: '>=10'} + + comma-separated-tokens@2.0.3: + resolution: {integrity: sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==} + + commander@10.0.1: + resolution: {integrity: sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==} + engines: {node: '>=14'} + + commander@2.20.3: + resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==} + + commander@5.1.0: + resolution: {integrity: sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==} + engines: {node: '>= 6'} + + commander@7.2.0: + resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==} + engines: {node: '>= 10'} + + commander@8.3.0: + resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==} + engines: {node: '>= 12'} + + common-path-prefix@3.0.0: + resolution: {integrity: sha512-QE33hToZseCH3jS0qN96O/bSh3kaw/h+Tq7ngyY9eWDUnTlTNUyqfqvCXioLe5Na5jFsL78ra/wuBU4iuEgd4w==} + + compressible@2.0.18: + resolution: {integrity: sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==} + engines: {node: '>= 0.6'} + + compression@1.7.5: + resolution: {integrity: sha512-bQJ0YRck5ak3LgtnpKkiabX5pNF7tMUh1BSy2ZBOTh0Dim0BUu6aPPwByIns6/A5Prh8PufSPerMDUklpzes2Q==} + engines: {node: '>= 0.8.0'} + + concat-map@0.0.1: + resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==} + + config-chain@1.1.13: + resolution: {integrity: sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ==} + + configstore@6.0.0: + resolution: {integrity: sha512-cD31W1v3GqUlQvbBCGcXmd2Nj9SvLDOP1oQ0YFuLETufzSPaKp11rYBsSOm7rCsW3OnIRAFM3OxRhceaXNYHkA==} + engines: {node: '>=12'} + + connect-history-api-fallback@2.0.0: + resolution: {integrity: sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA==} + engines: {node: '>=0.8'} + + consola@3.2.3: + resolution: {integrity: sha512-I5qxpzLv+sJhTVEoLYNcTW+bThDCPsit0vLNKShZx6rLtpilNpmmeTPaeqJb9ZE9dV3DGaeby6Vuhrw38WjeyQ==} + engines: {node: ^14.18.0 || >=16.10.0} + + consolidated-events@2.0.2: + resolution: {integrity: sha512-2/uRVMdRypf5z/TW/ncD/66l75P5hH2vM/GR8Jf8HLc2xnfJtmina6F6du8+v4Z2vTrMo7jC+W1tmEEuuELgkQ==} + + content-disposition@0.5.2: + resolution: {integrity: sha512-kRGRZw3bLlFISDBgwTSA1TMBFN6J6GWDeubmDE3AF+3+yXL8hTWv8r5rkLbqYXY4RjPk/EzHnClI3zQf1cFmHA==} + engines: {node: '>= 0.6'} + + content-disposition@0.5.4: + resolution: {integrity: sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==} + engines: {node: '>= 0.6'} + + content-type@1.0.5: + resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==} + engines: {node: '>= 0.6'} + + convert-source-map@2.0.0: + resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==} + + cookie-signature@1.0.6: + resolution: {integrity: sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==} + + cookie@0.7.1: + resolution: {integrity: sha512-6DnInpx7SJ2AK3+CTUE/ZM0vWTUboZCegxhC2xiIydHR9jNuTAASBrfEpHhiGOZw/nX51bHt6YQl8jsGo4y/0w==} + engines: {node: '>= 0.6'} + + copy-text-to-clipboard@3.2.0: + resolution: {integrity: sha512-RnJFp1XR/LOBDckxTib5Qjr/PMfkatD0MUCQgdpqS8MdKiNUzBjAQBEN6oUy+jW7LI93BBG3DtMB2KOOKpGs2Q==} + engines: {node: '>=12'} + + copy-webpack-plugin@11.0.0: + resolution: {integrity: sha512-fX2MWpamkW0hZxMEg0+mYnA40LTosOSa5TqZ9GYIBzyJa9C3QUaMPSE2xAi/buNr8u89SfD9wHSQVBzrRa/SOQ==} + engines: {node: '>= 14.15.0'} + peerDependencies: + webpack: ^5.1.0 + + core-js-compat@3.39.0: + resolution: {integrity: sha512-VgEUx3VwlExr5no0tXlBt+silBvhTryPwCXRI2Id1PN8WTKu7MreethvddqOubrYxkFdv/RnYrqlv1sFNAUelw==} + + core-js-pure@3.39.0: + resolution: {integrity: sha512-7fEcWwKI4rJinnK+wLTezeg2smbFFdSBP6E2kQZNbnzM2s1rpKQ6aaRteZSSg7FLU3P0HGGVo/gbpfanU36urg==} + + core-js@3.39.0: + resolution: {integrity: sha512-raM0ew0/jJUqkJ0E6e8UDtl+y/7ktFivgWvqw8dNSQeNWoSDLvQ1H/RN3aPXB9tBd4/FhyR4RDPGhsNIMsAn7g==} + + core-util-is@1.0.3: + resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==} + + cosmiconfig@6.0.0: + resolution: {integrity: sha512-xb3ZL6+L8b9JLLCx3ZdoZy4+2ECphCMo2PwqgP1tlfVq6M6YReyzBJtvWWtbDSpNr9hn96pkCiZqUcFEc+54Qg==} + engines: {node: '>=8'} + + cosmiconfig@8.3.6: + resolution: {integrity: sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA==} + engines: {node: '>=14'} + peerDependencies: + typescript: '>=4.9.5' + peerDependenciesMeta: + typescript: + optional: true + + cross-spawn@7.0.6: + resolution: {integrity: sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==} + engines: {node: '>= 8'} + + crypto-random-string@4.0.0: + resolution: {integrity: sha512-x8dy3RnvYdlUcPOjkEHqozhiwzKNSq7GcPuXFbnyMOCHxX8V3OgIg/pYuabl2sbUPfIJaeAQB7PMOK8DFIdoRA==} + engines: {node: '>=12'} + + css-blank-pseudo@7.0.1: + resolution: {integrity: sha512-jf+twWGDf6LDoXDUode+nc7ZlrqfaNphrBIBrcmeP3D8yw1uPaix1gCC8LUQUGQ6CycuK2opkbFFWFuq/a94ag==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + css-declaration-sorter@7.2.0: + resolution: {integrity: sha512-h70rUM+3PNFuaBDTLe8wF/cdWu+dOZmb7pJt8Z2sedYbAcQVQV/tEchueg3GWxwqS0cxtbxmaHEdkNACqcvsow==} + engines: {node: ^14 || ^16 || >=18} + peerDependencies: + postcss: ^8.0.9 + + css-has-pseudo@7.0.1: + resolution: {integrity: sha512-EOcoyJt+OsuKfCADgLT7gADZI5jMzIe/AeI6MeAYKiFBDmNmM7kk46DtSfMj5AohUJisqVzopBpnQTlvbyaBWg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + css-loader@6.11.0: + resolution: {integrity: sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g==} + engines: {node: '>= 12.13.0'} + peerDependencies: + '@rspack/core': 0.x || 1.x + webpack: ^5.0.0 + peerDependenciesMeta: + '@rspack/core': + optional: true + webpack: + optional: true + + css-minimizer-webpack-plugin@5.0.1: + resolution: {integrity: sha512-3caImjKFQkS+ws1TGcFn0V1HyDJFq1Euy589JlD6/3rV2kj+w7r5G9WDMgSHvpvXHNZ2calVypZWuEDQd9wfLg==} + engines: {node: '>= 14.15.0'} + peerDependencies: + '@parcel/css': '*' + '@swc/css': '*' + clean-css: '*' + csso: '*' + esbuild: '*' + lightningcss: '*' + webpack: ^5.0.0 + peerDependenciesMeta: + '@parcel/css': + optional: true + '@swc/css': + optional: true + clean-css: + optional: true + csso: + optional: true + esbuild: + optional: true + lightningcss: + optional: true + + css-prefers-color-scheme@10.0.0: + resolution: {integrity: sha512-VCtXZAWivRglTZditUfB4StnsWr6YVZ2PRtuxQLKTNRdtAf8tpzaVPE9zXIF3VaSc7O70iK/j1+NXxyQCqdPjQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + css-select@4.3.0: + resolution: {integrity: sha512-wPpOYtnsVontu2mODhA19JrqWxNsfdatRKd64kmpRbQgh1KtItko5sTnEpPdpSaJszTOhEMlF/RPz28qj4HqhQ==} + + css-select@5.1.0: + resolution: {integrity: sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==} + + css-tree@2.2.1: + resolution: {integrity: sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==} + engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'} + + css-tree@2.3.1: + resolution: {integrity: sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw==} + engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0} + + css-what@6.1.0: + resolution: {integrity: sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==} + engines: {node: '>= 6'} + + cssdb@8.2.3: + resolution: {integrity: sha512-9BDG5XmJrJQQnJ51VFxXCAtpZ5ebDlAREmO8sxMOVU0aSxN/gocbctjIG5LMh3WBUq+xTlb/jw2LoljBEqraTA==} + + cssesc@3.0.0: + resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==} + engines: {node: '>=4'} + hasBin: true + + cssnano-preset-advanced@6.1.2: + resolution: {integrity: sha512-Nhao7eD8ph2DoHolEzQs5CfRpiEP0xa1HBdnFZ82kvqdmbwVBUr2r1QuQ4t1pi+D1ZpqpcO4T+wy/7RxzJ/WPQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + cssnano-preset-default@6.1.2: + resolution: {integrity: sha512-1C0C+eNaeN8OcHQa193aRgYexyJtU8XwbdieEjClw+J9d94E41LwT6ivKH0WT+fYwYWB0Zp3I3IZ7tI/BbUbrg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + cssnano-utils@4.0.2: + resolution: {integrity: sha512-ZR1jHg+wZ8o4c3zqf1SIUSTIvm/9mU343FMR6Obe/unskbvpGhZOo1J6d/r8D1pzkRQYuwbcH3hToOuoA2G7oQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + cssnano@6.1.2: + resolution: {integrity: sha512-rYk5UeX7VAM/u0lNqewCdasdtPK81CgX8wJFLEIXHbV2oldWRgJAsZrdhRXkV1NJzA2g850KiFm9mMU2HxNxMA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + csso@5.0.5: + resolution: {integrity: sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==} + engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'} + + csstype@3.1.3: + resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==} + + debounce@1.2.1: + resolution: {integrity: sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug==} + + debug@2.6.9: + resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==} + peerDependencies: + supports-color: '*' + peerDependenciesMeta: + supports-color: + optional: true + + debug@4.4.0: + resolution: {integrity: sha512-6WTZ/IxCY/T6BALoZHaE4ctp9xm+Z5kY/pzYaCHRFeyVhojxlrm+46y68HA6hr0TcwEssoxNiDEUJQjfPZ/RYA==} + engines: {node: '>=6.0'} + peerDependencies: + supports-color: '*' + peerDependenciesMeta: + supports-color: + optional: true + + decode-named-character-reference@1.0.2: + resolution: {integrity: sha512-O8x12RzrUF8xyVcY0KJowWsmaJxQbmy0/EtnNtHRpsOcT7dFk5W598coHqBVpmWo1oQQfsCqfCmkZN5DJrZVdg==} + + decompress-response@6.0.0: + resolution: {integrity: sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ==} + engines: {node: '>=10'} + + deep-extend@0.6.0: + resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==} + engines: {node: '>=4.0.0'} + + deepmerge@4.3.1: + resolution: {integrity: sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==} + engines: {node: '>=0.10.0'} + + default-gateway@6.0.3: + resolution: {integrity: sha512-fwSOJsbbNzZ/CUFpqFBqYfYNLj1NbMPm8MMCIzHjC83iSJRBEGmDUxU+WP661BaBQImeC2yHwXtz+P/O9o+XEg==} + engines: {node: '>= 10'} + + defer-to-connect@2.0.1: + resolution: {integrity: sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg==} + engines: {node: '>=10'} + + define-data-property@1.1.4: + resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==} + engines: {node: '>= 0.4'} + + define-lazy-prop@2.0.0: + resolution: {integrity: sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==} + engines: {node: '>=8'} + + define-properties@1.2.1: + resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==} + engines: {node: '>= 0.4'} + + del@6.1.1: + resolution: {integrity: sha512-ua8BhapfP0JUJKC/zV9yHHDW/rDoDxP4Zhn3AkA6/xT6gY7jYXJiaeyBZznYVujhZZET+UgcbZiQ7sN3WqcImg==} + engines: {node: '>=10'} + + depd@1.1.2: + resolution: {integrity: sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ==} + engines: {node: '>= 0.6'} + + depd@2.0.0: + resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==} + engines: {node: '>= 0.8'} + + dequal@2.0.3: + resolution: {integrity: sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==} + engines: {node: '>=6'} + + destroy@1.2.0: + resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==} + engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} + + detect-libc@1.0.3: + resolution: {integrity: sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==} + engines: {node: '>=0.10'} + hasBin: true + + detect-libc@2.0.3: + resolution: {integrity: sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw==} + engines: {node: '>=8'} + + detect-node@2.1.0: + resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==} + + detect-port-alt@1.1.6: + resolution: {integrity: sha512-5tQykt+LqfJFBEYaDITx7S7cR7mJ/zQmLXZ2qt5w04ainYZw6tBf9dBunMjVeVOdYVRUzUOE4HkY5J7+uttb5Q==} + engines: {node: '>= 4.2.1'} + hasBin: true + + detect-port@1.6.1: + resolution: {integrity: sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q==} + engines: {node: '>= 4.0.0'} + hasBin: true + + devlop@1.1.0: + resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==} + + dir-glob@3.0.1: + resolution: {integrity: sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==} + engines: {node: '>=8'} + + dns-packet@5.6.1: + resolution: {integrity: sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==} + engines: {node: '>=6'} + + docusaurus-plugin-image-zoom@2.0.0: + resolution: {integrity: sha512-TWHQZeoiged+95CESlZk++lihzl3pqw34n0/fbexx2AocmFhbo9K2scYDgYB8amki4/X6mUCLTPZE1pQvT+00Q==} + peerDependencies: + '@docusaurus/theme-classic': '>=3.0.0' + + dom-converter@0.2.0: + resolution: {integrity: sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==} + + dom-serializer@1.4.1: + resolution: {integrity: sha512-VHwB3KfrcOOkelEG2ZOfxqLZdfkil8PtJi4P8N2MMXucZq2yLp75ClViUlOVwyoHEDjYU433Aq+5zWP61+RGag==} + + dom-serializer@2.0.0: + resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==} + + domelementtype@2.3.0: + resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==} + + domhandler@4.3.1: + resolution: {integrity: sha512-GrwoxYN+uWlzO8uhUXRl0P+kHE4GtVPfYzVLcUxPL7KNdHKj66vvlhiweIHqYYXWlw+T8iLMp42Lm67ghw4WMQ==} + engines: {node: '>= 4'} + + domhandler@5.0.3: + resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==} + engines: {node: '>= 4'} + + domutils@2.8.0: + resolution: {integrity: sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==} + + domutils@3.1.0: + resolution: {integrity: sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==} + + dot-case@3.0.4: + resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==} + + dot-prop@6.0.1: + resolution: {integrity: sha512-tE7ztYzXHIeyvc7N+hR3oi7FIbf/NIjVP9hmAt3yMXzrQ072/fpjGLx2GxNxGxUl5V73MEqYzioOMoVhGMJ5cA==} + engines: {node: '>=10'} + + dunder-proto@1.0.0: + resolution: {integrity: sha512-9+Sj30DIu+4KvHqMfLUGLFYL2PkURSYMVXJyXe92nFRvlYq5hBjLEhblKB+vkd/WVlUYMWigiY07T91Fkk0+4A==} + engines: {node: '>= 0.4'} + + duplexer@0.1.2: + resolution: {integrity: sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==} + + eastasianwidth@0.2.0: + resolution: {integrity: sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==} + + ee-first@1.1.1: + resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==} + + electron-to-chromium@1.5.72: + resolution: {integrity: sha512-ZpSAUOZ2Izby7qnZluSrAlGgGQzucmFbN0n64dYzocYxnxV5ufurpj3VgEe4cUp7ir9LmeLxNYo8bVnlM8bQHw==} + + emoji-regex@8.0.0: + resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==} + + emoji-regex@9.2.2: + resolution: {integrity: sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==} + + emojilib@2.4.0: + resolution: {integrity: sha512-5U0rVMU5Y2n2+ykNLQqMoqklN9ICBT/KsvC1Gz6vqHbz2AXXGkG+Pm5rMWk/8Vjrr/mY9985Hi8DYzn1F09Nyw==} + + emojis-list@3.0.0: + resolution: {integrity: sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==} + engines: {node: '>= 4'} + + emoticon@4.1.0: + resolution: {integrity: sha512-VWZfnxqwNcc51hIy/sbOdEem6D+cVtpPzEEtVAFdaas30+1dgkyaOQ4sQ6Bp0tOMqWO1v+HQfYaoodOkdhK6SQ==} + + encodeurl@1.0.2: + resolution: {integrity: sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==} + engines: {node: '>= 0.8'} + + encodeurl@2.0.0: + resolution: {integrity: sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg==} + engines: {node: '>= 0.8'} + + encoding-sniffer@0.2.0: + resolution: {integrity: sha512-ju7Wq1kg04I3HtiYIOrUrdfdDvkyO9s5XM8QAj/bN61Yo/Vb4vgJxy5vi4Yxk01gWHbrofpPtpxM8bKger9jhg==} + + end-of-stream@1.4.4: + resolution: {integrity: sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==} + + enhanced-resolve@5.17.1: + resolution: {integrity: sha512-LMHl3dXhTcfv8gM4kEzIUeTQ+7fpdA0l2tUf34BddXPkz2A5xJ5L/Pchd5BL6rdccM9QGvu0sWZzK1Z1t4wwyg==} + engines: {node: '>=10.13.0'} + + entities@2.2.0: + resolution: {integrity: sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==} + + entities@4.5.0: + resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==} + engines: {node: '>=0.12'} + + error-ex@1.3.2: + resolution: {integrity: sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==} + + es-define-property@1.0.1: + resolution: {integrity: sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==} + engines: {node: '>= 0.4'} + + es-errors@1.3.0: + resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==} + engines: {node: '>= 0.4'} + + es-module-lexer@1.5.4: + resolution: {integrity: sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw==} + + esast-util-from-estree@2.0.0: + resolution: {integrity: sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==} + + esast-util-from-js@2.0.1: + resolution: {integrity: sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==} + + escalade@3.2.0: + resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==} + engines: {node: '>=6'} + + escape-goat@4.0.0: + resolution: {integrity: sha512-2Sd4ShcWxbx6OY1IHyla/CVNwvg7XwZVoXZHcSu9w9SReNP1EzzD5T8NWKIR38fIqEns9kDWKUQTXXAmlDrdPg==} + engines: {node: '>=12'} + + escape-html@1.0.3: + resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==} + + escape-string-regexp@1.0.5: + resolution: {integrity: sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==} + engines: {node: '>=0.8.0'} + + escape-string-regexp@4.0.0: + resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==} + engines: {node: '>=10'} + + escape-string-regexp@5.0.0: + resolution: {integrity: sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw==} + engines: {node: '>=12'} + + eslint-scope@5.1.1: + resolution: {integrity: sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==} + engines: {node: '>=8.0.0'} + + esprima@4.0.1: + resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==} + engines: {node: '>=4'} + hasBin: true + + esrecurse@4.3.0: + resolution: {integrity: sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==} + engines: {node: '>=4.0'} + + estraverse@4.3.0: + resolution: {integrity: sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==} + engines: {node: '>=4.0'} + + estraverse@5.3.0: + resolution: {integrity: sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==} + engines: {node: '>=4.0'} + + estree-util-attach-comments@3.0.0: + resolution: {integrity: sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw==} + + estree-util-build-jsx@3.0.1: + resolution: {integrity: sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ==} + + estree-util-is-identifier-name@3.0.0: + resolution: {integrity: sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg==} + + estree-util-scope@1.0.0: + resolution: {integrity: sha512-2CAASclonf+JFWBNJPndcOpA8EMJwa0Q8LUFJEKqXLW6+qBvbFZuF5gItbQOs/umBUkjviCSDCbBwU2cXbmrhQ==} + + estree-util-to-js@2.0.0: + resolution: {integrity: sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg==} + + estree-util-value-to-estree@3.2.1: + resolution: {integrity: sha512-Vt2UOjyPbNQQgT5eJh+K5aATti0OjCIAGc9SgMdOFYbohuifsWclR74l0iZTJwePMgWYdX1hlVS+dedH9XV8kw==} + + estree-util-visit@2.0.0: + resolution: {integrity: sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww==} + + estree-walker@3.0.3: + resolution: {integrity: sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==} + + esutils@2.0.3: + resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==} + engines: {node: '>=0.10.0'} + + eta@2.2.0: + resolution: {integrity: sha512-UVQ72Rqjy/ZKQalzV5dCCJP80GrmPrMxh6NlNf+erV6ObL0ZFkhCstWRawS85z3smdr3d2wXPsZEY7rDPfGd2g==} + engines: {node: '>=6.0.0'} + + etag@1.8.1: + resolution: {integrity: sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==} + engines: {node: '>= 0.6'} + + eval@0.1.8: + resolution: {integrity: sha512-EzV94NYKoO09GLXGjXj9JIlXijVck4ONSr5wiCWDvhsvj5jxSrzTmRU/9C1DyB6uToszLs8aifA6NQ7lEQdvFw==} + engines: {node: '>= 0.8'} + + eventemitter3@4.0.7: + resolution: {integrity: sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==} + + events@3.3.0: + resolution: {integrity: sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==} + engines: {node: '>=0.8.x'} + + execa@5.1.1: + resolution: {integrity: sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==} + engines: {node: '>=10'} + + expand-template@2.0.3: + resolution: {integrity: sha512-XYfuKMvj4O35f/pOXLObndIRvyQ+/+6AhODh+OKWj9S9498pHHn/IMszH+gt0fBCRWMNfk1ZSp5x3AifmnI2vg==} + engines: {node: '>=6'} + + express@4.21.2: + resolution: {integrity: sha512-28HqgMZAmih1Czt9ny7qr6ek2qddF4FclbMzwhCREB6OFfH+rXAnuNCwo1/wFvrtbgsQDb4kSbX9de9lFbrXnA==} + engines: {node: '>= 0.10.0'} + + extend-shallow@2.0.1: + resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==} + engines: {node: '>=0.10.0'} + + extend@3.0.2: + resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==} + + fast-deep-equal@3.1.3: + resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==} + + fast-fifo@1.3.2: + resolution: {integrity: sha512-/d9sfos4yxzpwkDkuN7k2SqFKtYNmCTzgfEpz82x34IM9/zc8KGxQoXg1liNC/izpRM/MBdt44Nmx41ZWqk+FQ==} + + fast-glob@3.3.2: + resolution: {integrity: sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==} + engines: {node: '>=8.6.0'} + + fast-json-stable-stringify@2.1.0: + resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==} + + fast-uri@3.0.3: + resolution: {integrity: sha512-aLrHthzCjH5He4Z2H9YZ+v6Ujb9ocRuW6ZzkJQOrTxleEijANq4v1TsaPaVG1PZcuurEzrLcWRyYBYXD5cEiaw==} + + fastq@1.17.1: + resolution: {integrity: sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==} + + fault@2.0.1: + resolution: {integrity: sha512-WtySTkS4OKev5JtpHXnib4Gxiurzh5NCGvWrFaZ34m6JehfTUhKZvn9njTfw48t6JumVQOmrKqpmGcdwxnhqBQ==} + + faye-websocket@0.11.4: + resolution: {integrity: sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==} + engines: {node: '>=0.8.0'} + + feed@4.2.2: + resolution: {integrity: sha512-u5/sxGfiMfZNtJ3OvQpXcvotFpYkL0n9u9mM2vkui2nGo8b4wvDkJ8gAkYqbA8QpGyFCv3RK0Z+Iv+9veCS9bQ==} + engines: {node: '>=0.4.0'} + + figures@3.2.0: + resolution: {integrity: sha512-yaduQFRKLXYOGgEn6AZau90j3ggSOyiqXU0F9JZfeXYhNa+Jk4X+s45A2zg5jns87GAFa34BBm2kXw4XpNcbdg==} + engines: {node: '>=8'} + + file-loader@6.2.0: + resolution: {integrity: sha512-qo3glqyTa61Ytg4u73GultjHGjdRyig3tG6lPtyX/jOEJvHif9uB0/OCI2Kif6ctF3caQTW2G5gym21oAsI4pw==} + engines: {node: '>= 10.13.0'} + peerDependencies: + webpack: ^4.0.0 || ^5.0.0 + + filesize@8.0.7: + resolution: {integrity: sha512-pjmC+bkIF8XI7fWaH8KxHcZL3DPybs1roSKP4rKDvy20tAWwIObE4+JIseG2byfGKhud5ZnM4YSGKBz7Sh0ndQ==} + engines: {node: '>= 0.4.0'} + + fill-range@7.1.1: + resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==} + engines: {node: '>=8'} + + finalhandler@1.3.1: + resolution: {integrity: sha512-6BN9trH7bp3qvnrRyzsBz+g3lZxTNZTbVO2EV1CS0WIcDbawYVdYvGflME/9QP0h0pYlCDBCTjYa9nZzMDpyxQ==} + engines: {node: '>= 0.8'} + + find-cache-dir@4.0.0: + resolution: {integrity: sha512-9ZonPT4ZAK4a+1pUPVPZJapbi7O5qbbJPdYw/NOQWZZbVLdDTYM3A4R9z/DpAM08IDaFGsvPgiGZ82WEwUDWjg==} + engines: {node: '>=14.16'} + + find-up@3.0.0: + resolution: {integrity: sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==} + engines: {node: '>=6'} + + find-up@5.0.0: + resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==} + engines: {node: '>=10'} + + find-up@6.3.0: + resolution: {integrity: sha512-v2ZsoEuVHYy8ZIlYqwPe/39Cy+cFDzp4dXPaxNvkEuouymu+2Jbz0PxpKarJHYJTmv2HWT3O382qY8l4jMWthw==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + flat@5.0.2: + resolution: {integrity: sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==} + hasBin: true + + follow-redirects@1.15.9: + resolution: {integrity: sha512-gew4GsXizNgdoRyqmyfMHyAmXsZDk6mHkSxZFCzW9gwlbtOW44CDtYavM+y+72qD/Vq2l550kMF52DT8fOLJqQ==} + engines: {node: '>=4.0'} + peerDependencies: + debug: '*' + peerDependenciesMeta: + debug: + optional: true + + fork-ts-checker-webpack-plugin@6.5.3: + resolution: {integrity: sha512-SbH/l9ikmMWycd5puHJKTkZJKddF4iRLyW3DeZ08HTI7NGyLS38MXd/KGgeWumQO7YNQbW2u/NtPT2YowbPaGQ==} + engines: {node: '>=10', yarn: '>=1.0.0'} + peerDependencies: + eslint: '>= 6' + typescript: '>= 2.7' + vue-template-compiler: '*' + webpack: '>= 4' + peerDependenciesMeta: + eslint: + optional: true + vue-template-compiler: + optional: true + + form-data-encoder@2.1.4: + resolution: {integrity: sha512-yDYSgNMraqvnxiEXO4hi88+YZxaHC6QKzb5N84iRCTDeRO7ZALpir/lVmf/uXUhnwUr2O4HU8s/n6x+yNjQkHw==} + engines: {node: '>= 14.17'} + + format@0.2.2: + resolution: {integrity: sha512-wzsgA6WOq+09wrU1tsJ09udeR/YZRaeArL9e1wPbFg3GG2yDnC2ldKpxs4xunpFF9DgqCqOIra3bc1HWrJ37Ww==} + engines: {node: '>=0.4.x'} + + forwarded@0.2.0: + resolution: {integrity: sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==} + engines: {node: '>= 0.6'} + + fraction.js@4.3.7: + resolution: {integrity: sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew==} + + fresh@0.5.2: + resolution: {integrity: sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==} + engines: {node: '>= 0.6'} + + fs-constants@1.0.0: + resolution: {integrity: sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==} + + fs-extra@11.2.0: + resolution: {integrity: sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw==} + engines: {node: '>=14.14'} + + fs-extra@9.1.0: + resolution: {integrity: sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==} + engines: {node: '>=10'} + + fs-monkey@1.0.6: + resolution: {integrity: sha512-b1FMfwetIKymC0eioW7mTywihSQE4oLzQn1dB6rZB5fx/3NpNEdAWeCSMB+60/AeT0TCXsxzAlcYVEFCTAksWg==} + + fs.realpath@1.0.0: + resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==} + + fsevents@2.3.3: + resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==} + engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0} + os: [darwin] + + function-bind@1.1.2: + resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==} + + gensync@1.0.0-beta.2: + resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==} + engines: {node: '>=6.9.0'} + + get-intrinsic@1.2.5: + resolution: {integrity: sha512-Y4+pKa7XeRUPWFNvOOYHkRYrfzW07oraURSvjDmRVOJ748OrVmeXtpE4+GCEHncjCjkTxPNRt8kEbxDhsn6VTg==} + engines: {node: '>= 0.4'} + + get-own-enumerable-property-symbols@3.0.2: + resolution: {integrity: sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g==} + + get-stream@6.0.1: + resolution: {integrity: sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==} + engines: {node: '>=10'} + + github-from-package@0.0.0: + resolution: {integrity: sha512-SyHy3T1v2NUXn29OsWdxmK6RwHD+vkj3v8en8AOBZ1wBQ/hCAQ5bAQTD02kW4W9tUp/3Qh6J8r9EvntiyCmOOw==} + + github-slugger@1.5.0: + resolution: {integrity: sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw==} + + glob-parent@5.1.2: + resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==} + engines: {node: '>= 6'} + + glob-parent@6.0.2: + resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==} + engines: {node: '>=10.13.0'} + + glob-to-regexp@0.4.1: + resolution: {integrity: sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==} + + glob@7.2.3: + resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==} + deprecated: Glob versions prior to v9 are no longer supported + + global-dirs@3.0.1: + resolution: {integrity: sha512-NBcGGFbBA9s1VzD41QXDG+3++t9Mn5t1FpLdhESY6oKY4gYTFpX4wO3sqGUa0Srjtbfj3szX0RnemmrVRUdULA==} + engines: {node: '>=10'} + + global-modules@2.0.0: + resolution: {integrity: sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==} + engines: {node: '>=6'} + + global-prefix@3.0.0: + resolution: {integrity: sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==} + engines: {node: '>=6'} + + globals@11.12.0: + resolution: {integrity: sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==} + engines: {node: '>=4'} + + globby@11.1.0: + resolution: {integrity: sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==} + engines: {node: '>=10'} + + globby@13.2.2: + resolution: {integrity: sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + gopd@1.2.0: + resolution: {integrity: sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==} + engines: {node: '>= 0.4'} + + got@12.6.1: + resolution: {integrity: sha512-mThBblvlAF1d4O5oqyvN+ZxLAYwIJK7bpMxgYqPD9okW0C3qm5FFn7k811QrcuEBwaogR3ngOFoCfs6mRv7teQ==} + engines: {node: '>=14.16'} + + graceful-fs@4.2.10: + resolution: {integrity: sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA==} + + graceful-fs@4.2.11: + resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==} + + gray-matter@4.0.3: + resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==} + engines: {node: '>=6.0'} + + gzip-size@6.0.0: + resolution: {integrity: sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==} + engines: {node: '>=10'} + + handle-thing@2.0.1: + resolution: {integrity: sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg==} + + has-flag@4.0.0: + resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==} + engines: {node: '>=8'} + + has-property-descriptors@1.0.2: + resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==} + + has-symbols@1.1.0: + resolution: {integrity: sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==} + engines: {node: '>= 0.4'} + + has-yarn@3.0.0: + resolution: {integrity: sha512-IrsVwUHhEULx3R8f/aA8AHuEzAorplsab/v8HBzEiIukwq5i/EC+xmOW+HfP1OaDP+2JkgT1yILHN2O3UFIbcA==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + hasown@2.0.2: + resolution: {integrity: sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==} + engines: {node: '>= 0.4'} + + hast-util-from-parse5@8.0.2: + resolution: {integrity: sha512-SfMzfdAi/zAoZ1KkFEyyeXBn7u/ShQrfd675ZEE9M3qj+PMFX05xubzRyF76CCSJu8au9jgVxDV1+okFvgZU4A==} + + hast-util-parse-selector@4.0.0: + resolution: {integrity: sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A==} + + hast-util-raw@9.1.0: + resolution: {integrity: sha512-Y8/SBAHkZGoNkpzqqfCldijcuUKh7/su31kEBp67cFY09Wy0mTRgtsLYsiIxMJxlu0f6AA5SUTbDR8K0rxnbUw==} + + hast-util-to-estree@3.1.0: + resolution: {integrity: sha512-lfX5g6hqVh9kjS/B9E2gSkvHH4SZNiQFiqWS0x9fENzEl+8W12RqdRxX6d/Cwxi30tPQs3bIO+aolQJNp1bIyw==} + + hast-util-to-jsx-runtime@2.3.2: + resolution: {integrity: sha512-1ngXYb+V9UT5h+PxNRa1O1FYguZK/XL+gkeqvp7EdHlB9oHUG0eYRo/vY5inBdcqo3RkPMC58/H94HvkbfGdyg==} + + hast-util-to-parse5@8.0.0: + resolution: {integrity: sha512-3KKrV5ZVI8if87DVSi1vDeByYrkGzg4mEfeu4alwgmmIeARiBLKCZS2uw5Gb6nU9x9Yufyj3iudm6i7nl52PFw==} + + hast-util-whitespace@3.0.0: + resolution: {integrity: sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==} + + hastscript@9.0.0: + resolution: {integrity: sha512-jzaLBGavEDKHrc5EfFImKN7nZKKBdSLIdGvCwDZ9TfzbF2ffXiov8CKE445L2Z1Ek2t/m4SKQ2j6Ipv7NyUolw==} + + he@1.2.0: + resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==} + hasBin: true + + history@4.10.1: + resolution: {integrity: sha512-36nwAD620w12kuzPAsyINPWJqlNbij+hpK1k9XRloDtym8mxzGYl2c17LnV6IAGB2Dmg4tEa7G7DlawS0+qjew==} + + hoist-non-react-statics@3.3.2: + resolution: {integrity: sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==} + + hpack.js@2.1.6: + resolution: {integrity: sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ==} + + htm@3.1.1: + resolution: {integrity: sha512-983Vyg8NwUE7JkZ6NmOqpCZ+sh1bKv2iYTlUkzlWmA5JD2acKoxd4KVxbMmxX/85mtfdnDmTFoNKcg5DGAvxNQ==} + + html-entities@2.5.2: + resolution: {integrity: sha512-K//PSRMQk4FZ78Kyau+mZurHn3FH0Vwr+H36eE0rPbeYkRRi9YxceYPhuN60UwWorxyKHhqoAJl2OFKa4BVtaA==} + + html-escaper@2.0.2: + resolution: {integrity: sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==} + + html-minifier-terser@6.1.0: + resolution: {integrity: sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw==} + engines: {node: '>=12'} + hasBin: true + + html-minifier-terser@7.2.0: + resolution: {integrity: sha512-tXgn3QfqPIpGl9o+K5tpcj3/MN4SfLtsx2GWwBC3SSd0tXQGyF3gsSqad8loJgKZGM3ZxbYDd5yhiBIdWpmvLA==} + engines: {node: ^14.13.1 || >=16.0.0} + hasBin: true + + html-tags@3.3.1: + resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==} + engines: {node: '>=8'} + + html-void-elements@3.0.0: + resolution: {integrity: sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==} + + html-webpack-plugin@5.6.3: + resolution: {integrity: sha512-QSf1yjtSAsmf7rYBV7XX86uua4W/vkhIt0xNXKbsi2foEeW7vjJQz4bhnpL3xH+l1ryl1680uNv968Z+X6jSYg==} + engines: {node: '>=10.13.0'} + peerDependencies: + '@rspack/core': 0.x || 1.x + webpack: ^5.20.0 + peerDependenciesMeta: + '@rspack/core': + optional: true + webpack: + optional: true + + htmlparser2@6.1.0: + resolution: {integrity: sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==} + + htmlparser2@8.0.2: + resolution: {integrity: sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==} + + htmlparser2@9.1.0: + resolution: {integrity: sha512-5zfg6mHUoaer/97TxnGpxmbR7zJtPwIYFMZ/H5ucTlPZhKvtum05yiPK3Mgai3a0DyVxv7qYqoweaEd2nrYQzQ==} + + http-cache-semantics@4.1.1: + resolution: {integrity: sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ==} + + http-deceiver@1.2.7: + resolution: {integrity: sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw==} + + http-errors@1.6.3: + resolution: {integrity: sha512-lks+lVC8dgGyh97jxvxeYTWQFvh4uw4yC12gVl63Cg30sjPX4wuGcdkICVXDAESr6OJGjqGA8Iz5mkeN6zlD7A==} + engines: {node: '>= 0.6'} + + http-errors@2.0.0: + resolution: {integrity: sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==} + engines: {node: '>= 0.8'} + + http-parser-js@0.5.8: + resolution: {integrity: sha512-SGeBX54F94Wgu5RH3X5jsDtf4eHyRogWX1XGT3b4HuW3tQPM4AaBzoUji/4AAJNXCEOWZ5O0DgZmJw1947gD5Q==} + + http-proxy-middleware@2.0.7: + resolution: {integrity: sha512-fgVY8AV7qU7z/MmXJ/rxwbrtQH4jBQ9m7kp3llF0liB7glmFeVZFBepQb32T3y8n8k2+AEYuMPCpinYW+/CuRA==} + engines: {node: '>=12.0.0'} + peerDependencies: + '@types/express': ^4.17.13 + peerDependenciesMeta: + '@types/express': + optional: true + + http-proxy@1.18.1: + resolution: {integrity: sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==} + engines: {node: '>=8.0.0'} + + http2-wrapper@2.2.1: + resolution: {integrity: sha512-V5nVw1PAOgfI3Lmeaj2Exmeg7fenjhRUgz1lPSezy1CuhPYbgQtbQj4jZfEAEMlaL+vupsvhjqCyjzob0yxsmQ==} + engines: {node: '>=10.19.0'} + + human-signals@2.1.0: + resolution: {integrity: sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==} + engines: {node: '>=10.17.0'} + + iconv-lite@0.4.24: + resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==} + engines: {node: '>=0.10.0'} + + iconv-lite@0.6.3: + resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==} + engines: {node: '>=0.10.0'} + + icss-utils@5.1.0: + resolution: {integrity: sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 + + ieee754@1.2.1: + resolution: {integrity: sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==} + + ignore@5.3.2: + resolution: {integrity: sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==} + engines: {node: '>= 4'} + + image-size@1.1.1: + resolution: {integrity: sha512-541xKlUw6jr/6gGuk92F+mYM5zaFAc5ahphvkqvNe2bQ6gVBkd6bfrmVJ2t4KDAfikAYZyIqTnktX3i6/aQDrQ==} + engines: {node: '>=16.x'} + hasBin: true + + immer@9.0.21: + resolution: {integrity: sha512-bc4NBHqOqSfRW7POMkHd51LvClaeMXpm8dx0e8oE2GORbq5aRK7Bxl4FyzVLdGtLmvLKL7BTDBG5ACQm4HWjTA==} + + import-fresh@3.3.0: + resolution: {integrity: sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==} + engines: {node: '>=6'} + + import-lazy@4.0.0: + resolution: {integrity: sha512-rKtvo6a868b5Hu3heneU+L4yEQ4jYKLtjpnPeUdK7h0yzXGmyBTypknlkCvHFBqfX9YlorEiMM6Dnq/5atfHkw==} + engines: {node: '>=8'} + + imurmurhash@0.1.4: + resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==} + engines: {node: '>=0.8.19'} + + indent-string@4.0.0: + resolution: {integrity: sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==} + engines: {node: '>=8'} + + infima@0.2.0-alpha.45: + resolution: {integrity: sha512-uyH0zfr1erU1OohLk0fT4Rrb94AOhguWNOcD9uGrSpRvNB+6gZXUoJX5J0NtvzBO10YZ9PgvA4NFgt+fYg8ojw==} + engines: {node: '>=12'} + + inflight@1.0.6: + resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==} + deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. + + inherits@2.0.3: + resolution: {integrity: sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==} + + inherits@2.0.4: + resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==} + + ini@1.3.8: + resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==} + + ini@2.0.0: + resolution: {integrity: sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA==} + engines: {node: '>=10'} + + inline-style-parser@0.1.1: + resolution: {integrity: sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q==} + + inline-style-parser@0.2.4: + resolution: {integrity: sha512-0aO8FkhNZlj/ZIbNi7Lxxr12obT7cL1moPfE4tg1LkX7LlLfC6DeX4l2ZEud1ukP9jNQyNnfzQVqwbwmAATY4Q==} + + interpret@1.4.0: + resolution: {integrity: sha512-agE4QfB2Lkp9uICn7BAqoscw4SZP9kTE2hxiFI3jBPmXJfdqiahTbUuKGsMoN2GtqL9AxhYioAcVvgsb1HvRbA==} + engines: {node: '>= 0.10'} + + invariant@2.2.4: + resolution: {integrity: sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==} + + ipaddr.js@1.9.1: + resolution: {integrity: sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==} + engines: {node: '>= 0.10'} + + ipaddr.js@2.2.0: + resolution: {integrity: sha512-Ag3wB2o37wslZS19hZqorUnrnzSkpOVy+IiiDEiTqNubEYpYuHWIf6K4psgN2ZWKExS4xhVCrRVfb/wfW8fWJA==} + engines: {node: '>= 10'} + + is-alphabetical@2.0.1: + resolution: {integrity: sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==} + + is-alphanumerical@2.0.1: + resolution: {integrity: sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==} + + is-arrayish@0.2.1: + resolution: {integrity: sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==} + + is-arrayish@0.3.2: + resolution: {integrity: sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==} + + is-binary-path@2.1.0: + resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==} + engines: {node: '>=8'} + + is-ci@3.0.1: + resolution: {integrity: sha512-ZYvCgrefwqoQ6yTyYUbQu64HsITZ3NfKX1lzaEYdkTDcfKzzCI/wthRRYKkdjHKFVgNiXKAKm65Zo1pk2as/QQ==} + hasBin: true + + is-core-module@2.15.1: + resolution: {integrity: sha512-z0vtXSwucUJtANQWldhbtbt7BnL0vxiFjIdDLAatwhDYty2bad6s+rijD6Ri4YuYJubLzIJLUidCh09e1djEVQ==} + engines: {node: '>= 0.4'} + + is-decimal@2.0.1: + resolution: {integrity: sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==} + + is-docker@2.2.1: + resolution: {integrity: sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==} + engines: {node: '>=8'} + hasBin: true + + is-extendable@0.1.1: + resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==} + engines: {node: '>=0.10.0'} + + is-extglob@2.1.1: + resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==} + engines: {node: '>=0.10.0'} + + is-fullwidth-code-point@3.0.0: + resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==} + engines: {node: '>=8'} + + is-glob@4.0.3: + resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==} + engines: {node: '>=0.10.0'} + + is-hexadecimal@2.0.1: + resolution: {integrity: sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==} + + is-installed-globally@0.4.0: + resolution: {integrity: sha512-iwGqO3J21aaSkC7jWnHP/difazwS7SFeIqxv6wEtLU8Y5KlzFTjyqcSIT0d8s4+dDhKytsk9PJZ2BkS5eZwQRQ==} + engines: {node: '>=10'} + + is-npm@6.0.0: + resolution: {integrity: sha512-JEjxbSmtPSt1c8XTkVrlujcXdKV1/tvuQ7GwKcAlyiVLeYFQ2VHat8xfrDJsIkhCdF/tZ7CiIR3sy141c6+gPQ==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + is-number@7.0.0: + resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==} + engines: {node: '>=0.12.0'} + + is-obj@1.0.1: + resolution: {integrity: sha512-l4RyHgRqGN4Y3+9JHVrNqO+tN0rV5My76uW5/nuO4K1b6vw5G8d/cmFjP9tRfEsdhZNt0IFdZuK/c2Vr4Nb+Qg==} + engines: {node: '>=0.10.0'} + + is-obj@2.0.0: + resolution: {integrity: sha512-drqDG3cbczxxEJRoOXcOjtdp1J/lyp1mNn0xaznRs8+muBhgQcrnbspox5X5fOw0HnMnbfDzvnEMEtqDEJEo8w==} + engines: {node: '>=8'} + + is-path-cwd@2.2.0: + resolution: {integrity: sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==} + engines: {node: '>=6'} + + is-path-inside@3.0.3: + resolution: {integrity: sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==} + engines: {node: '>=8'} + + is-plain-obj@3.0.0: + resolution: {integrity: sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA==} + engines: {node: '>=10'} + + is-plain-obj@4.1.0: + resolution: {integrity: sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==} + engines: {node: '>=12'} + + is-plain-object@2.0.4: + resolution: {integrity: sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==} + engines: {node: '>=0.10.0'} + + is-regexp@1.0.0: + resolution: {integrity: sha512-7zjFAPO4/gwyQAAgRRmqeEeyIICSdmCqa3tsVHMdBzaXXRiqopZL4Cyghg/XulGWrtABTpbnYYzzIRffLkP4oA==} + engines: {node: '>=0.10.0'} + + is-root@2.1.0: + resolution: {integrity: sha512-AGOriNp96vNBd3HtU+RzFEc75FfR5ymiYv8E553I71SCeXBiMsVDUtdio1OEFvrPyLIQ9tVR5RxXIFe5PUFjMg==} + engines: {node: '>=6'} + + is-stream@2.0.1: + resolution: {integrity: sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==} + engines: {node: '>=8'} + + is-typedarray@1.0.0: + resolution: {integrity: sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA==} + + is-wsl@2.2.0: + resolution: {integrity: sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==} + engines: {node: '>=8'} + + is-yarn-global@0.4.1: + resolution: {integrity: sha512-/kppl+R+LO5VmhYSEWARUFjodS25D68gvj8W7z0I7OWhUla5xWu8KL6CtB2V0R6yqhnRgbcaREMr4EEM6htLPQ==} + engines: {node: '>=12'} + + isarray@0.0.1: + resolution: {integrity: sha512-D2S+3GLxWH+uhrNEcoh/fnmYeP8E8/zHl644d/jdA0g2uyXvy3sb0qxotE+ne0LtccHknQzWwZEzhak7oJ0COQ==} + + isarray@1.0.0: + resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==} + + isexe@2.0.0: + resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==} + + isobject@3.0.1: + resolution: {integrity: sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==} + engines: {node: '>=0.10.0'} + + jest-util@29.7.0: + resolution: {integrity: sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} + + jest-worker@27.5.1: + resolution: {integrity: sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==} + engines: {node: '>= 10.13.0'} + + jest-worker@29.7.0: + resolution: {integrity: sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} + + jiti@1.21.6: + resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==} + hasBin: true + + joi@17.13.3: + resolution: {integrity: sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA==} + + js-tokens@4.0.0: + resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==} + + js-yaml@3.14.1: + resolution: {integrity: sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==} + hasBin: true + + js-yaml@4.1.0: + resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==} + hasBin: true + + jsesc@3.0.2: + resolution: {integrity: sha512-xKqzzWXDttJuOcawBt4KnKHHIf5oQ/Cxax+0PWFG+DFDgHNAdi+TXECADI+RYiFUMmx8792xsMbbgXj4CwnP4g==} + engines: {node: '>=6'} + hasBin: true + + jsesc@3.1.0: + resolution: {integrity: sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==} + engines: {node: '>=6'} + hasBin: true + + json-buffer@3.0.1: + resolution: {integrity: sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==} + + json-parse-even-better-errors@2.3.1: + resolution: {integrity: sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==} + + json-schema-traverse@0.4.1: + resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==} + + json-schema-traverse@1.0.0: + resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==} + + json5@2.2.3: + resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==} + engines: {node: '>=6'} + hasBin: true + + jsonfile@6.1.0: + resolution: {integrity: sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==} + + keyv@4.5.4: + resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==} + + kind-of@6.0.3: + resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==} + engines: {node: '>=0.10.0'} + + kleur@3.0.3: + resolution: {integrity: sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==} + engines: {node: '>=6'} + + latest-version@7.0.0: + resolution: {integrity: sha512-KvNT4XqAMzdcL6ka6Tl3i2lYeFDgXNCuIX+xNx6ZMVR1dFq+idXd9FLKNMOIx0t9mJ9/HudyX4oZWXZQ0UJHeg==} + engines: {node: '>=14.16'} + + launch-editor@2.9.1: + resolution: {integrity: sha512-Gcnl4Bd+hRO9P9icCP/RVVT2o8SFlPXofuCxvA2SaZuH45whSvf5p8x5oih5ftLiVhEI4sp5xDY+R+b3zJBh5w==} + + leven@3.1.0: + resolution: {integrity: sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==} + engines: {node: '>=6'} + + lightningcss-darwin-arm64@1.28.2: + resolution: {integrity: sha512-/8cPSqZiusHSS+WQz0W4NuaqFjquys1x+NsdN/XOHb+idGHJSoJ7SoQTVl3DZuAgtPZwFZgRfb/vd1oi8uX6+g==} + engines: {node: '>= 12.0.0'} + cpu: [arm64] + os: [darwin] + + lightningcss-darwin-x64@1.28.2: + resolution: {integrity: sha512-R7sFrXlgKjvoEG8umpVt/yutjxOL0z8KWf0bfPT3cYMOW4470xu5qSHpFdIOpRWwl3FKNMUdbKtMUjYt0h2j4g==} + engines: {node: '>= 12.0.0'} + cpu: [x64] + os: [darwin] + + lightningcss-freebsd-x64@1.28.2: + resolution: {integrity: sha512-l2qrCT+x7crAY+lMIxtgvV10R8VurzHAoUZJaVFSlHrN8kRLTvEg9ObojIDIexqWJQvJcVVV3vfzsEynpiuvgA==} + engines: {node: '>= 12.0.0'} + cpu: [x64] + os: [freebsd] + + lightningcss-linux-arm-gnueabihf@1.28.2: + resolution: {integrity: sha512-DKMzpICBEKnL53X14rF7hFDu8KKALUJtcKdFUCW5YOlGSiwRSgVoRjM97wUm/E0NMPkzrTi/rxfvt7ruNK8meg==} + engines: {node: '>= 12.0.0'} + cpu: [arm] + os: [linux] + + lightningcss-linux-arm64-gnu@1.28.2: + resolution: {integrity: sha512-nhfjYkfymWZSxdtTNMWyhFk2ImUm0X7NAgJWFwnsYPOfmtWQEapzG/DXZTfEfMjSzERNUNJoQjPAbdqgB+sjiw==} + engines: {node: '>= 12.0.0'} + cpu: [arm64] + os: [linux] + + lightningcss-linux-arm64-musl@1.28.2: + resolution: {integrity: sha512-1SPG1ZTNnphWvAv8RVOymlZ8BDtAg69Hbo7n4QxARvkFVCJAt0cgjAw1Fox0WEhf4PwnyoOBaVH0Z5YNgzt4dA==} + engines: {node: '>= 12.0.0'} + cpu: [arm64] + os: [linux] + + lightningcss-linux-x64-gnu@1.28.2: + resolution: {integrity: sha512-ZhQy0FcO//INWUdo/iEdbefntTdpPVQ0XJwwtdbBuMQe+uxqZoytm9M+iqR9O5noWFaxK+nbS2iR/I80Q2Ofpg==} + engines: {node: '>= 12.0.0'} + cpu: [x64] + os: [linux] + + lightningcss-linux-x64-musl@1.28.2: + resolution: {integrity: sha512-alb/j1NMrgQmSFyzTbN1/pvMPM+gdDw7YBuQ5VSgcFDypN3Ah0BzC2dTZbzwzaMdUVDszX6zH5MzjfVN1oGuww==} + engines: {node: '>= 12.0.0'} + cpu: [x64] + os: [linux] + + lightningcss-win32-arm64-msvc@1.28.2: + resolution: {integrity: sha512-WnwcjcBeAt0jGdjlgbT9ANf30pF0C/QMb1XnLnH272DQU8QXh+kmpi24R55wmWBwaTtNAETZ+m35ohyeMiNt+g==} + engines: {node: '>= 12.0.0'} + cpu: [arm64] + os: [win32] + + lightningcss-win32-x64-msvc@1.28.2: + resolution: {integrity: sha512-3piBifyT3avz22o6mDKywQC/OisH2yDK+caHWkiMsF82i3m5wDBadyCjlCQ5VNgzYkxrWZgiaxHDdd5uxsi0/A==} + engines: {node: '>= 12.0.0'} + cpu: [x64] + os: [win32] + + lightningcss@1.28.2: + resolution: {integrity: sha512-ePLRrbt3fgjXI5VFZOLbvkLD5ZRuxGKm+wJ3ujCqBtL3NanDHPo/5zicR5uEKAPiIjBYF99BM4K4okvMznjkVA==} + engines: {node: '>= 12.0.0'} + + lilconfig@3.1.3: + resolution: {integrity: sha512-/vlFKAoH5Cgt3Ie+JLhRbwOsCQePABiU3tJ1egGvyQ+33R/vcwM2Zl2QR/LzjsBeItPt3oSVXapn+m4nQDvpzw==} + engines: {node: '>=14'} + + lines-and-columns@1.2.4: + resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==} + + loader-runner@4.3.0: + resolution: {integrity: sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==} + engines: {node: '>=6.11.5'} + + loader-utils@2.0.4: + resolution: {integrity: sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==} + engines: {node: '>=8.9.0'} + + loader-utils@3.3.1: + resolution: {integrity: sha512-FMJTLMXfCLMLfJxcX9PFqX5qD88Z5MRGaZCVzfuqeZSPsyiBzs+pahDQjbIWz2QIzPZz0NX9Zy4FX3lmK6YHIg==} + engines: {node: '>= 12.13.0'} + + locate-path@3.0.0: + resolution: {integrity: sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==} + engines: {node: '>=6'} + + locate-path@6.0.0: + resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==} + engines: {node: '>=10'} + + locate-path@7.2.0: + resolution: {integrity: sha512-gvVijfZvn7R+2qyPX8mAuKcFGDf6Nc61GdvGafQsHL0sBIxfKzA+usWn4GFC/bk+QdwPUD4kWFJLhElipq+0VA==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + lodash.debounce@4.0.8: + resolution: {integrity: sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==} + + lodash.memoize@4.1.2: + resolution: {integrity: sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==} + + lodash.uniq@4.5.0: + resolution: {integrity: sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==} + + lodash@4.17.21: + resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==} + + longest-streak@3.1.0: + resolution: {integrity: sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g==} + + loose-envify@1.4.0: + resolution: {integrity: sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==} + hasBin: true + + lower-case@2.0.2: + resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==} + + lowercase-keys@3.0.0: + resolution: {integrity: sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + lru-cache@5.1.1: + resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==} + + lunr-languages@1.14.0: + resolution: {integrity: sha512-hWUAb2KqM3L7J5bcrngszzISY4BxrXn/Xhbb9TTCJYEGqlR1nG67/M14sp09+PTIRklobrn57IAxcdcO/ZFyNA==} + + mark.js@8.11.1: + resolution: {integrity: sha512-1I+1qpDt4idfgLQG+BNWmrqku+7/2bi5nLf4YwF8y8zXvmfiTBY3PV3ZibfrjBueCByROpuBjLLFCajqkgYoLQ==} + + markdown-extensions@2.0.0: + resolution: {integrity: sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==} + engines: {node: '>=16'} + + markdown-table@2.0.0: + resolution: {integrity: sha512-Ezda85ToJUBhM6WGaG6veasyym+Tbs3cMAw/ZhOPqXiYsr0jgocBV3j3nx+4lk47plLlIqjwuTm/ywVI+zjJ/A==} + + markdown-table@3.0.4: + resolution: {integrity: sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw==} + + mdast-util-directive@3.0.0: + resolution: {integrity: sha512-JUpYOqKI4mM3sZcNxmF/ox04XYFFkNwr0CFlrQIkCwbvH0xzMCqkMqAde9wRd80VAhaUrwFwKm2nxretdT1h7Q==} + + mdast-util-find-and-replace@3.0.1: + resolution: {integrity: sha512-SG21kZHGC3XRTSUhtofZkBzZTJNM5ecCi0SK2IMKmSXR8vO3peL+kb1O0z7Zl83jKtutG4k5Wv/W7V3/YHvzPA==} + + mdast-util-from-markdown@2.0.2: + resolution: {integrity: sha512-uZhTV/8NBuw0WHkPTrCqDOl0zVe1BIng5ZtHoDk49ME1qqcjYmmLmOf0gELgcRMxN4w2iuIeVso5/6QymSrgmA==} + + mdast-util-frontmatter@2.0.1: + resolution: {integrity: sha512-LRqI9+wdgC25P0URIJY9vwocIzCcksduHQ9OF2joxQoyTNVduwLAFUzjoopuRJbJAReaKrNQKAZKL3uCMugWJA==} + + mdast-util-gfm-autolink-literal@2.0.1: + resolution: {integrity: sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ==} + + mdast-util-gfm-footnote@2.0.0: + resolution: {integrity: sha512-5jOT2boTSVkMnQ7LTrd6n/18kqwjmuYqo7JUPe+tRCY6O7dAuTFMtTPauYYrMPpox9hlN0uOx/FL8XvEfG9/mQ==} + + mdast-util-gfm-strikethrough@2.0.0: + resolution: {integrity: sha512-mKKb915TF+OC5ptj5bJ7WFRPdYtuHv0yTRxK2tJvi+BDqbkiG7h7u/9SI89nRAYcmap2xHQL9D+QG/6wSrTtXg==} + + mdast-util-gfm-table@2.0.0: + resolution: {integrity: sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg==} + + mdast-util-gfm-task-list-item@2.0.0: + resolution: {integrity: sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ==} + + mdast-util-gfm@3.0.0: + resolution: {integrity: sha512-dgQEX5Amaq+DuUqf26jJqSK9qgixgd6rYDHAv4aTBuA92cTknZlKpPfa86Z/s8Dj8xsAQpFfBmPUHWJBWqS4Bw==} + + mdast-util-mdx-expression@2.0.1: + resolution: {integrity: sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ==} + + mdast-util-mdx-jsx@3.1.3: + resolution: {integrity: sha512-bfOjvNt+1AcbPLTFMFWY149nJz0OjmewJs3LQQ5pIyVGxP4CdOqNVJL6kTaM5c68p8q82Xv3nCyFfUnuEcH3UQ==} + + mdast-util-mdx@3.0.0: + resolution: {integrity: sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w==} + + mdast-util-mdxjs-esm@2.0.1: + resolution: {integrity: sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg==} + + mdast-util-phrasing@4.1.0: + resolution: {integrity: sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w==} + + mdast-util-to-hast@13.2.0: + resolution: {integrity: sha512-QGYKEuUsYT9ykKBCMOEDLsU5JRObWQusAolFMeko/tYPufNkRffBAQjIE+99jbA87xv6FgmjLtwjh9wBWajwAA==} + + mdast-util-to-markdown@2.1.2: + resolution: {integrity: sha512-xj68wMTvGXVOKonmog6LwyJKrYXZPvlwabaryTjLh9LuvovB/KAH+kvi8Gjj+7rJjsFi23nkUxRQv1KqSroMqA==} + + mdast-util-to-string@4.0.0: + resolution: {integrity: sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==} + + mdn-data@2.0.28: + resolution: {integrity: sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==} + + mdn-data@2.0.30: + resolution: {integrity: sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA==} + + media-typer@0.3.0: + resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==} + engines: {node: '>= 0.6'} + + medium-zoom@1.1.0: + resolution: {integrity: sha512-ewyDsp7k4InCUp3jRmwHBRFGyjBimKps/AJLjRSox+2q/2H4p/PNpQf+pwONWlJiOudkBXtbdmVbFjqyybfTmQ==} + + memfs@3.5.3: + resolution: {integrity: sha512-UERzLsxzllchadvbPs5aolHh65ISpKpM+ccLbOJ8/vvpBKmAWf+la7dXFy7Mr0ySHbdHrFv5kGFCUHHe6GFEmw==} + engines: {node: '>= 4.0.0'} + + merge-descriptors@1.0.3: + resolution: {integrity: sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ==} + + merge-stream@2.0.0: + resolution: {integrity: sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==} + + merge2@1.4.1: + resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==} + engines: {node: '>= 8'} + + methods@1.1.2: + resolution: {integrity: sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==} + engines: {node: '>= 0.6'} + + micromark-core-commonmark@2.0.2: + resolution: {integrity: sha512-FKjQKbxd1cibWMM1P9N+H8TwlgGgSkWZMmfuVucLCHaYqeSvJ0hFeHsIa65pA2nYbes0f8LDHPMrd9X7Ujxg9w==} + + micromark-extension-directive@3.0.2: + resolution: {integrity: sha512-wjcXHgk+PPdmvR58Le9d7zQYWy+vKEU9Se44p2CrCDPiLr2FMyiT4Fyb5UFKFC66wGB3kPlgD7q3TnoqPS7SZA==} + + micromark-extension-frontmatter@2.0.0: + resolution: {integrity: sha512-C4AkuM3dA58cgZha7zVnuVxBhDsbttIMiytjgsM2XbHAB2faRVaHRle40558FBN+DJcrLNCoqG5mlrpdU4cRtg==} + + micromark-extension-gfm-autolink-literal@2.1.0: + resolution: {integrity: sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==} + + micromark-extension-gfm-footnote@2.1.0: + resolution: {integrity: sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==} + + micromark-extension-gfm-strikethrough@2.1.0: + resolution: {integrity: sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw==} + + micromark-extension-gfm-table@2.1.0: + resolution: {integrity: sha512-Ub2ncQv+fwD70/l4ou27b4YzfNaCJOvyX4HxXU15m7mpYY+rjuWzsLIPZHJL253Z643RpbcP1oeIJlQ/SKW67g==} + + micromark-extension-gfm-tagfilter@2.0.0: + resolution: {integrity: sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg==} + + micromark-extension-gfm-task-list-item@2.1.0: + resolution: {integrity: sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw==} + + micromark-extension-gfm@3.0.0: + resolution: {integrity: sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w==} + + micromark-extension-mdx-expression@3.0.0: + resolution: {integrity: sha512-sI0nwhUDz97xyzqJAbHQhp5TfaxEvZZZ2JDqUo+7NvyIYG6BZ5CPPqj2ogUoPJlmXHBnyZUzISg9+oUmU6tUjQ==} + + micromark-extension-mdx-jsx@3.0.1: + resolution: {integrity: sha512-vNuFb9czP8QCtAQcEJn0UJQJZA8Dk6DXKBqx+bg/w0WGuSxDxNr7hErW89tHUY31dUW4NqEOWwmEUNhjTFmHkg==} + + micromark-extension-mdx-md@2.0.0: + resolution: {integrity: sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ==} + + micromark-extension-mdxjs-esm@3.0.0: + resolution: {integrity: sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A==} + + micromark-extension-mdxjs@3.0.0: + resolution: {integrity: sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ==} + + micromark-factory-destination@2.0.1: + resolution: {integrity: sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA==} + + micromark-factory-label@2.0.1: + resolution: {integrity: sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg==} + + micromark-factory-mdx-expression@2.0.2: + resolution: {integrity: sha512-5E5I2pFzJyg2CtemqAbcyCktpHXuJbABnsb32wX2U8IQKhhVFBqkcZR5LRm1WVoFqa4kTueZK4abep7wdo9nrw==} + + micromark-factory-space@1.1.0: + resolution: {integrity: sha512-cRzEj7c0OL4Mw2v6nwzttyOZe8XY/Z8G0rzmWQZTBi/jjwyw/U4uqKtUORXQrR5bAZZnbTI/feRV/R7hc4jQYQ==} + + micromark-factory-space@2.0.1: + resolution: {integrity: sha512-zRkxjtBxxLd2Sc0d+fbnEunsTj46SWXgXciZmHq0kDYGnck/ZSGj9/wULTV95uoeYiK5hRXP2mJ98Uo4cq/LQg==} + + micromark-factory-title@2.0.1: + resolution: {integrity: sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw==} + + micromark-factory-whitespace@2.0.1: + resolution: {integrity: sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ==} + + micromark-util-character@1.2.0: + resolution: {integrity: sha512-lXraTwcX3yH/vMDaFWCQJP1uIszLVebzUa3ZHdrgxr7KEU/9mL4mVgCpGbyhvNLNlauROiNUq7WN5u7ndbY6xg==} + + micromark-util-character@2.1.1: + resolution: {integrity: sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==} + + micromark-util-chunked@2.0.1: + resolution: {integrity: sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA==} + + micromark-util-classify-character@2.0.1: + resolution: {integrity: sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q==} + + micromark-util-combine-extensions@2.0.1: + resolution: {integrity: sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg==} + + micromark-util-decode-numeric-character-reference@2.0.2: + resolution: {integrity: sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw==} + + micromark-util-decode-string@2.0.1: + resolution: {integrity: sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ==} + + micromark-util-encode@2.0.1: + resolution: {integrity: sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw==} + + micromark-util-events-to-acorn@2.0.2: + resolution: {integrity: sha512-Fk+xmBrOv9QZnEDguL9OI9/NQQp6Hz4FuQ4YmCb/5V7+9eAh1s6AYSvL20kHkD67YIg7EpE54TiSlcsf3vyZgA==} + + micromark-util-html-tag-name@2.0.1: + resolution: {integrity: sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA==} + + micromark-util-normalize-identifier@2.0.1: + resolution: {integrity: sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q==} + + micromark-util-resolve-all@2.0.1: + resolution: {integrity: sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg==} + + micromark-util-sanitize-uri@2.0.1: + resolution: {integrity: sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ==} + + micromark-util-subtokenize@2.0.3: + resolution: {integrity: sha512-VXJJuNxYWSoYL6AJ6OQECCFGhIU2GGHMw8tahogePBrjkG8aCCas3ibkp7RnVOSTClg2is05/R7maAhF1XyQMg==} + + micromark-util-symbol@1.1.0: + resolution: {integrity: sha512-uEjpEYY6KMs1g7QfJ2eX1SQEV+ZT4rUD3UcF6l57acZvLNK7PBZL+ty82Z1qhK1/yXIY4bdx04FKMgR0g4IAag==} + + micromark-util-symbol@2.0.1: + resolution: {integrity: sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q==} + + micromark-util-types@1.1.0: + resolution: {integrity: sha512-ukRBgie8TIAcacscVHSiddHjO4k/q3pnedmzMQ4iwDcK0FtFCohKOlFbaOL/mPgfnPsL3C1ZyxJa4sbWrBl3jg==} + + micromark-util-types@2.0.1: + resolution: {integrity: sha512-534m2WhVTddrcKVepwmVEVnUAmtrx9bfIjNoQHRqfnvdaHQiFytEhJoTgpWJvDEXCO5gLTQh3wYC1PgOJA4NSQ==} + + micromark@4.0.1: + resolution: {integrity: sha512-eBPdkcoCNvYcxQOAKAlceo5SNdzZWfF+FcSupREAzdAh9rRmE239CEQAiTwIgblwnoM8zzj35sZ5ZwvSEOF6Kw==} + + micromatch@4.0.8: + resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==} + engines: {node: '>=8.6'} + + mime-db@1.33.0: + resolution: {integrity: sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ==} + engines: {node: '>= 0.6'} + + mime-db@1.52.0: + resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==} + engines: {node: '>= 0.6'} + + mime-db@1.53.0: + resolution: {integrity: sha512-oHlN/w+3MQ3rba9rqFr6V/ypF10LSkdwUysQL7GkXoTgIWeV+tcXGA852TBxH+gsh8UWoyhR1hKcoMJTuWflpg==} + engines: {node: '>= 0.6'} + + mime-types@2.1.18: + resolution: {integrity: sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ==} + engines: {node: '>= 0.6'} + + mime-types@2.1.35: + resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==} + engines: {node: '>= 0.6'} + + mime@1.6.0: + resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==} + engines: {node: '>=4'} + hasBin: true + + mimic-fn@2.1.0: + resolution: {integrity: sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==} + engines: {node: '>=6'} + + mimic-response@3.1.0: + resolution: {integrity: sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ==} + engines: {node: '>=10'} + + mimic-response@4.0.0: + resolution: {integrity: sha512-e5ISH9xMYU0DzrT+jl8q2ze9D6eWBto+I8CNpe+VI+K2J/F/k3PdkdTdz4wvGVH4NTpo+NRYTVIuMQEMMcsLqg==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + mini-css-extract-plugin@2.9.2: + resolution: {integrity: sha512-GJuACcS//jtq4kCtd5ii/M0SZf7OZRH+BxdqXZHaJfb8TJiVl+NgQRPwiYt2EuqeSkNydn/7vP+bcE27C5mb9w==} + engines: {node: '>= 12.13.0'} + peerDependencies: + webpack: ^5.0.0 + + minimalistic-assert@1.0.1: + resolution: {integrity: sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==} + + minimatch@3.1.2: + resolution: {integrity: sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==} + + minimist@1.2.8: + resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==} + + mkdirp-classic@0.5.3: + resolution: {integrity: sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==} + + mrmime@2.0.0: + resolution: {integrity: sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw==} + engines: {node: '>=10'} + + ms@2.0.0: + resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==} + + ms@2.1.3: + resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==} + + multicast-dns@7.2.5: + resolution: {integrity: sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg==} + hasBin: true + + nanoid@3.3.8: + resolution: {integrity: sha512-WNLf5Sd8oZxOm+TzppcYk8gVOgP+l58xNy58D0nbUnOxOWRWvlcCV4kUF7ltmI6PsrLl/BgKEyS4mqsGChFN0w==} + engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1} + hasBin: true + + napi-build-utils@1.0.2: + resolution: {integrity: sha512-ONmRUqK7zj7DWX0D9ADe03wbwOBZxNAfF20PlGfCWQcD3+/MakShIHrMqx9YwPTfxDdF1zLeL+RGZiR9kGMLdg==} + + negotiator@0.6.3: + resolution: {integrity: sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==} + engines: {node: '>= 0.6'} + + negotiator@0.6.4: + resolution: {integrity: sha512-myRT3DiWPHqho5PrJaIRyaMv2kgYf0mUVgBNOYMuCH5Ki1yEiQaf/ZJuQ62nvpc44wL5WDbTX7yGJi1Neevw8w==} + engines: {node: '>= 0.6'} + + neo-async@2.6.2: + resolution: {integrity: sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==} + + no-case@3.0.4: + resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==} + + node-abi@3.71.0: + resolution: {integrity: sha512-SZ40vRiy/+wRTf21hxkkEjPJZpARzUMVcJoQse2EF8qkUWbbO2z7vd5oA/H6bVH6SZQ5STGcu0KRDS7biNRfxw==} + engines: {node: '>=10'} + + node-addon-api@6.1.0: + resolution: {integrity: sha512-+eawOlIgy680F0kBzPUNFhMZGtJ1YmqM6l4+Crf4IkImjYrO/mqPwRMh352g23uIaQKFItcQ64I7KMaJxHgAVA==} + + node-emoji@2.2.0: + resolution: {integrity: sha512-Z3lTE9pLaJF47NyMhd4ww1yFTAP8YhYI8SleJiHzM46Fgpm5cnNzSl9XfzFNqbaz+VlJrIj3fXQ4DeN1Rjm6cw==} + engines: {node: '>=18'} + + node-forge@1.3.1: + resolution: {integrity: sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA==} + engines: {node: '>= 6.13.0'} + + node-releases@2.0.19: + resolution: {integrity: sha512-xxOWJsBKtzAq7DY0J+DTzuz58K8e7sJbdgwkbMWQe8UYB6ekmsQ45q0M/tJDsGaZmbC+l7n57UV8Hl5tHxO9uw==} + + normalize-path@3.0.0: + resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==} + engines: {node: '>=0.10.0'} + + normalize-range@0.1.2: + resolution: {integrity: sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA==} + engines: {node: '>=0.10.0'} + + normalize-url@8.0.1: + resolution: {integrity: sha512-IO9QvjUMWxPQQhs60oOu10CRkWCiZzSUkzbXGGV9pviYl1fXYcvkzQ5jV9z8Y6un8ARoVRl4EtC6v6jNqbaJ/w==} + engines: {node: '>=14.16'} + + npm-run-path@4.0.1: + resolution: {integrity: sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==} + engines: {node: '>=8'} + + nprogress@0.2.0: + resolution: {integrity: sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA==} + + nth-check@2.1.1: + resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==} + + null-loader@4.0.1: + resolution: {integrity: sha512-pxqVbi4U6N26lq+LmgIbB5XATP0VdZKOG25DhHi8btMmJJefGArFyDg1yc4U3hWCJbMqSrw0qyrz1UQX+qYXqg==} + engines: {node: '>= 10.13.0'} + peerDependencies: + webpack: ^4.0.0 || ^5.0.0 + + object-assign@4.1.1: + resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==} + engines: {node: '>=0.10.0'} + + object-inspect@1.13.3: + resolution: {integrity: sha512-kDCGIbxkDSXE3euJZZXzc6to7fCrKHNI/hSRQnRuQ+BWjFNzZwiFF8fj/6o2t2G9/jTj8PSIYTfCLelLZEeRpA==} + engines: {node: '>= 0.4'} + + object-keys@1.1.1: + resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==} + engines: {node: '>= 0.4'} + + object.assign@4.1.5: + resolution: {integrity: sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==} + engines: {node: '>= 0.4'} + + obuf@1.1.2: + resolution: {integrity: sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==} + + on-finished@2.4.1: + resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==} + engines: {node: '>= 0.8'} + + on-headers@1.0.2: + resolution: {integrity: sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==} + engines: {node: '>= 0.8'} + + once@1.4.0: + resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==} + + onetime@5.1.2: + resolution: {integrity: sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==} + engines: {node: '>=6'} + + open@8.4.2: + resolution: {integrity: sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==} + engines: {node: '>=12'} + + opener@1.5.2: + resolution: {integrity: sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==} + hasBin: true + + p-cancelable@3.0.0: + resolution: {integrity: sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==} + engines: {node: '>=12.20'} + + p-limit@2.3.0: + resolution: {integrity: sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==} + engines: {node: '>=6'} + + p-limit@3.1.0: + resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==} + engines: {node: '>=10'} + + p-limit@4.0.0: + resolution: {integrity: sha512-5b0R4txpzjPWVw/cXXUResoD4hb6U/x9BH08L7nw+GN1sezDzPdxeRvpc9c433fZhBan/wusjbCsqwqm4EIBIQ==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + p-locate@3.0.0: + resolution: {integrity: sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==} + engines: {node: '>=6'} + + p-locate@5.0.0: + resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==} + engines: {node: '>=10'} + + p-locate@6.0.0: + resolution: {integrity: sha512-wPrq66Llhl7/4AGC6I+cqxT07LhXvWL08LNXz1fENOw0Ap4sRZZ/gZpTTJ5jpurzzzfS2W/Ge9BY3LgLjCShcw==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + p-map@4.0.0: + resolution: {integrity: sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ==} + engines: {node: '>=10'} + + p-retry@4.6.2: + resolution: {integrity: sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ==} + engines: {node: '>=8'} + + p-try@2.2.0: + resolution: {integrity: sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==} + engines: {node: '>=6'} + + package-json@8.1.1: + resolution: {integrity: sha512-cbH9IAIJHNj9uXi196JVsRlt7cHKak6u/e6AkL/bkRelZ7rlL3X1YKxsZwa36xipOEKAsdtmaG6aAJoM1fx2zA==} + engines: {node: '>=14.16'} + + param-case@3.0.4: + resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==} + + parent-module@1.0.1: + resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==} + engines: {node: '>=6'} + + parse-entities@4.0.1: + resolution: {integrity: sha512-SWzvYcSJh4d/SGLIOQfZ/CoNv6BTlI6YEQ7Nj82oDVnRpwe/Z/F1EMx42x3JAOwGBlCjeCH0BRJQbQ/opHL17w==} + + parse-json@5.2.0: + resolution: {integrity: sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==} + engines: {node: '>=8'} + + parse-numeric-range@1.3.0: + resolution: {integrity: sha512-twN+njEipszzlMJd4ONUYgSfZPDxgHhT9Ahed5uTigpQn90FggW4SA/AIPq/6a149fTbE9qBEcSwE3FAEp6wQQ==} + + parse5-htmlparser2-tree-adapter@7.1.0: + resolution: {integrity: sha512-ruw5xyKs6lrpo9x9rCZqZZnIUntICjQAd0Wsmp396Ul9lN/h+ifgVV1x1gZHi8euej6wTfpqX8j+BFQxF0NS/g==} + + parse5-parser-stream@7.1.2: + resolution: {integrity: sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow==} + + parse5@7.2.1: + resolution: {integrity: sha512-BuBYQYlv1ckiPdQi/ohiivi9Sagc9JG+Ozs0r7b/0iK3sKmrb0b9FdWdBbOdx6hBCM/F9Ir82ofnBhtZOjCRPQ==} + + parseurl@1.3.3: + resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==} + engines: {node: '>= 0.8'} + + pascal-case@3.1.2: + resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==} + + path-exists@3.0.0: + resolution: {integrity: sha512-bpC7GYwiDYQ4wYLe+FA8lhRjhQCMcQGuSgGGqDkg/QerRWw9CmGRT0iSOVRSZJ29NMLZgIzqaljJ63oaL4NIJQ==} + engines: {node: '>=4'} + + path-exists@4.0.0: + resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==} + engines: {node: '>=8'} + + path-exists@5.0.0: + resolution: {integrity: sha512-RjhtfwJOxzcFmNOi6ltcbcu4Iu+FL3zEj83dk4kAS+fVpTxXLO1b38RvJgT/0QwvV/L3aY9TAnyv0EOqW4GoMQ==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + path-is-absolute@1.0.1: + resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==} + engines: {node: '>=0.10.0'} + + path-is-inside@1.0.2: + resolution: {integrity: sha512-DUWJr3+ULp4zXmol/SZkFf3JGsS9/SIv+Y3Rt93/UjPpDpklB5f1er4O3POIbUuUJ3FXgqte2Q7SrU6zAqwk8w==} + + path-key@3.1.1: + resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==} + engines: {node: '>=8'} + + path-parse@1.0.7: + resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==} + + path-root-regex@0.1.2: + resolution: {integrity: sha512-4GlJ6rZDhQZFE0DPVKh0e9jmZ5egZfxTkp7bcRDuPlJXbAwhxcl2dINPUAsjLdejqaLsCeg8axcLjIbvBjN4pQ==} + engines: {node: '>=0.10.0'} + + path-root@0.1.1: + resolution: {integrity: sha512-QLcPegTHF11axjfojBIoDygmS2E3Lf+8+jI6wOVmNVenrKSo3mFdSGiIgdSHenczw3wPtlVMQaFVwGmM7BJdtg==} + engines: {node: '>=0.10.0'} + + path-to-regexp@0.1.12: + resolution: {integrity: sha512-RA1GjUVMnvYFxuqovrEqZoxxW5NUZqbwKtYz/Tt7nXerk0LbLblQmrsgdeOxV5SFHf0UDggjS/bSeOZwt1pmEQ==} + + path-to-regexp@1.9.0: + resolution: {integrity: sha512-xIp7/apCFJuUHdDLWe8O1HIkb0kQrOMb/0u6FXQjemHn/ii5LrIzU6bdECnsiTF/GjZkMEKg1xdiZwNqDYlZ6g==} + + path-to-regexp@3.3.0: + resolution: {integrity: sha512-qyCH421YQPS2WFDxDjftfc1ZR5WKQzVzqsp4n9M2kQhVOo/ByahFoUNJfl58kOcEGfQ//7weFTDhm+ss8Ecxgw==} + + path-type@4.0.0: + resolution: {integrity: sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==} + engines: {node: '>=8'} + + picocolors@1.1.1: + resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==} + + picomatch@2.3.1: + resolution: {integrity: sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==} + engines: {node: '>=8.6'} + + pkg-dir@7.0.0: + resolution: {integrity: sha512-Ie9z/WINcxxLp27BKOCHGde4ITq9UklYKDzVo1nhk5sqGEXU3FpkwP5GM2voTGJkGd9B3Otl+Q4uwSOeSUtOBA==} + engines: {node: '>=14.16'} + + pkg-up@3.1.0: + resolution: {integrity: sha512-nDywThFk1i4BQK4twPQ6TA4RT8bDY96yeuCVBWL3ePARCiEKDRSrNGbFIgUJpLp+XeIR65v8ra7WuJOFUBtkMA==} + engines: {node: '>=8'} + + postcss-attribute-case-insensitive@7.0.1: + resolution: {integrity: sha512-Uai+SupNSqzlschRyNx3kbCTWgY/2hcwtHEI/ej2LJWc9JJ77qKgGptd8DHwY1mXtZ7Aoh4z4yxfwMBue9eNgw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-calc@9.0.1: + resolution: {integrity: sha512-TipgjGyzP5QzEhsOZUaIkeO5mKeMFpebWzRogWG/ysonUlnHcq5aJe0jOjpfzUU8PeSaBQnrE8ehR0QA5vs8PQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.2.2 + + postcss-clamp@4.1.0: + resolution: {integrity: sha512-ry4b1Llo/9zz+PKC+030KUnPITTJAHeOwjfAyyB60eT0AorGLdzp52s31OsPRHRf8NchkgFoG2y6fCfn1IV1Ow==} + engines: {node: '>=7.6.0'} + peerDependencies: + postcss: ^8.4.6 + + postcss-color-functional-notation@7.0.6: + resolution: {integrity: sha512-wLXvm8RmLs14Z2nVpB4CWlnvaWPRcOZFltJSlcbYwSJ1EDZKsKDhPKIMecCnuU054KSmlmubkqczmm6qBPCBhA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-color-hex-alpha@10.0.0: + resolution: {integrity: sha512-1kervM2cnlgPs2a8Vt/Qbe5cQ++N7rkYo/2rz2BkqJZIHQwaVuJgQH38REHrAi4uM0b1fqxMkWYmese94iMp3w==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-color-rebeccapurple@10.0.0: + resolution: {integrity: sha512-JFta737jSP+hdAIEhk1Vs0q0YF5P8fFcj+09pweS8ktuGuZ8pPlykHsk6mPxZ8awDl4TrcxUqJo9l1IhVr/OjQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-colormin@6.1.0: + resolution: {integrity: sha512-x9yX7DOxeMAR+BgGVnNSAxmAj98NX/YxEMNFP+SDCEeNLb2r3i6Hh1ksMsnW8Ub5SLCpbescQqn9YEbE9554Sw==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-convert-values@6.1.0: + resolution: {integrity: sha512-zx8IwP/ts9WvUM6NkVSkiU902QZL1bwPhaVaLynPtCsOTqp+ZKbNi+s6XJg3rfqpKGA/oc7Oxk5t8pOQJcwl/w==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-custom-media@11.0.5: + resolution: {integrity: sha512-SQHhayVNgDvSAdX9NQ/ygcDQGEY+aSF4b/96z7QUX6mqL5yl/JgG/DywcF6fW9XbnCRE+aVYk+9/nqGuzOPWeQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-custom-properties@14.0.4: + resolution: {integrity: sha512-QnW8FCCK6q+4ierwjnmXF9Y9KF8q0JkbgVfvQEMa93x1GT8FvOiUevWCN2YLaOWyByeDX8S6VFbZEeWoAoXs2A==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-custom-selectors@8.0.4: + resolution: {integrity: sha512-ASOXqNvDCE0dAJ/5qixxPeL1aOVGHGW2JwSy7HyjWNbnWTQCl+fDc968HY1jCmZI0+BaYT5CxsOiUhavpG/7eg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-dir-pseudo-class@9.0.1: + resolution: {integrity: sha512-tRBEK0MHYvcMUrAuYMEOa0zg9APqirBcgzi6P21OhxtJyJADo/SWBwY1CAwEohQ/6HDaa9jCjLRG7K3PVQYHEA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-discard-comments@6.0.2: + resolution: {integrity: sha512-65w/uIqhSBBfQmYnG92FO1mWZjJ4GL5b8atm5Yw2UgrwD7HiNiSSNwJor1eCFGzUgYnN/iIknhNRVqjrrpuglw==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-discard-duplicates@6.0.3: + resolution: {integrity: sha512-+JA0DCvc5XvFAxwx6f/e68gQu/7Z9ud584VLmcgto28eB8FqSFZwtrLwB5Kcp70eIoWP/HXqz4wpo8rD8gpsTw==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-discard-empty@6.0.3: + resolution: {integrity: sha512-znyno9cHKQsK6PtxL5D19Fj9uwSzC2mB74cpT66fhgOadEUPyXFkbgwm5tvc3bt3NAy8ltE5MrghxovZRVnOjQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-discard-overridden@6.0.2: + resolution: {integrity: sha512-j87xzI4LUggC5zND7KdjsI25APtyMuynXZSujByMaav2roV6OZX+8AaCUcZSWqckZpjAjRyFDdpqybgjFO0HJQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-discard-unused@6.0.5: + resolution: {integrity: sha512-wHalBlRHkaNnNwfC8z+ppX57VhvS+HWgjW508esjdaEYr3Mx7Gnn2xA4R/CKf5+Z9S5qsqC+Uzh4ueENWwCVUA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-double-position-gradients@6.0.0: + resolution: {integrity: sha512-JkIGah3RVbdSEIrcobqj4Gzq0h53GG4uqDPsho88SgY84WnpkTpI0k50MFK/sX7XqVisZ6OqUfFnoUO6m1WWdg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-focus-visible@10.0.1: + resolution: {integrity: sha512-U58wyjS/I1GZgjRok33aE8juW9qQgQUNwTSdxQGuShHzwuYdcklnvK/+qOWX1Q9kr7ysbraQ6ht6r+udansalA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-focus-within@9.0.1: + resolution: {integrity: sha512-fzNUyS1yOYa7mOjpci/bR+u+ESvdar6hk8XNK/TRR0fiGTp2QT5N+ducP0n3rfH/m9I7H/EQU6lsa2BrgxkEjw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-font-variant@5.0.0: + resolution: {integrity: sha512-1fmkBaCALD72CK2a9i468mA/+tr9/1cBxRRMXOUaZqO43oWPR5imcyPjXwuv7PXbCid4ndlP5zWhidQVVa3hmA==} + peerDependencies: + postcss: ^8.1.0 + + postcss-gap-properties@6.0.0: + resolution: {integrity: sha512-Om0WPjEwiM9Ru+VhfEDPZJAKWUd0mV1HmNXqp2C29z80aQ2uP9UVhLc7e3aYMIor/S5cVhoPgYQ7RtfeZpYTRw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-image-set-function@7.0.0: + resolution: {integrity: sha512-QL7W7QNlZuzOwBTeXEmbVckNt1FSmhQtbMRvGGqqU4Nf4xk6KUEQhAoWuMzwbSv5jxiRiSZ5Tv7eiDB9U87znA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-lab-function@7.0.6: + resolution: {integrity: sha512-HPwvsoK7C949vBZ+eMyvH2cQeMr3UREoHvbtra76/UhDuiViZH6pir+z71UaJQohd7VDSVUdR6TkWYKExEc9aQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-loader@7.3.4: + resolution: {integrity: sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A==} + engines: {node: '>= 14.15.0'} + peerDependencies: + postcss: ^7.0.0 || ^8.0.1 + webpack: ^5.0.0 + + postcss-logical@8.0.0: + resolution: {integrity: sha512-HpIdsdieClTjXLOyYdUPAX/XQASNIwdKt5hoZW08ZOAiI+tbV0ta1oclkpVkW5ANU+xJvk3KkA0FejkjGLXUkg==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-merge-idents@6.0.3: + resolution: {integrity: sha512-1oIoAsODUs6IHQZkLQGO15uGEbK3EAl5wi9SS8hs45VgsxQfMnxvt+L+zIr7ifZFIH14cfAeVe2uCTa+SPRa3g==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-merge-longhand@6.0.5: + resolution: {integrity: sha512-5LOiordeTfi64QhICp07nzzuTDjNSO8g5Ksdibt44d+uvIIAE1oZdRn8y/W5ZtYgRH/lnLDlvi9F8btZcVzu3w==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-merge-rules@6.1.1: + resolution: {integrity: sha512-KOdWF0gju31AQPZiD+2Ar9Qjowz1LTChSjFFbS+e2sFgc4uHOp3ZvVX4sNeTlk0w2O31ecFGgrFzhO0RSWbWwQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-minify-font-values@6.1.0: + resolution: {integrity: sha512-gklfI/n+9rTh8nYaSJXlCo3nOKqMNkxuGpTn/Qm0gstL3ywTr9/WRKznE+oy6fvfolH6dF+QM4nCo8yPLdvGJg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-minify-gradients@6.0.3: + resolution: {integrity: sha512-4KXAHrYlzF0Rr7uc4VrfwDJ2ajrtNEpNEuLxFgwkhFZ56/7gaE4Nr49nLsQDZyUe+ds+kEhf+YAUolJiYXF8+Q==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-minify-params@6.1.0: + resolution: {integrity: sha512-bmSKnDtyyE8ujHQK0RQJDIKhQ20Jq1LYiez54WiaOoBtcSuflfK3Nm596LvbtlFcpipMjgClQGyGr7GAs+H1uA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-minify-selectors@6.0.4: + resolution: {integrity: sha512-L8dZSwNLgK7pjTto9PzWRoMbnLq5vsZSTu8+j1P/2GB8qdtGQfn+K1uSvFgYvgh83cbyxT5m43ZZhUMTJDSClQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-modules-extract-imports@3.1.0: + resolution: {integrity: sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 + + postcss-modules-local-by-default@4.1.0: + resolution: {integrity: sha512-rm0bdSv4jC3BDma3s9H19ZddW0aHX6EoqwDYU2IfZhRN+53QrufTRo2IdkAbRqLx4R2IYbZnbjKKxg4VN5oU9Q==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 + + postcss-modules-scope@3.2.1: + resolution: {integrity: sha512-m9jZstCVaqGjTAuny8MdgE88scJnCiQSlSrOWcTQgM2t32UBe+MUmFSO5t7VMSfAf/FJKImAxBav8ooCHJXCJA==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 + + postcss-modules-values@4.0.0: + resolution: {integrity: sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 + + postcss-nesting@13.0.1: + resolution: {integrity: sha512-VbqqHkOBOt4Uu3G8Dm8n6lU5+9cJFxiuty9+4rcoyRPO9zZS1JIs6td49VIoix3qYqELHlJIn46Oih9SAKo+yQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-normalize-charset@6.0.2: + resolution: {integrity: sha512-a8N9czmdnrjPHa3DeFlwqst5eaL5W8jYu3EBbTTkI5FHkfMhFZh1EGbku6jhHhIzTA6tquI2P42NtZ59M/H/kQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-display-values@6.0.2: + resolution: {integrity: sha512-8H04Mxsb82ON/aAkPeq8kcBbAtI5Q2a64X/mnRRfPXBq7XeogoQvReqxEfc0B4WPq1KimjezNC8flUtC3Qz6jg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-positions@6.0.2: + resolution: {integrity: sha512-/JFzI441OAB9O7VnLA+RtSNZvQ0NCFZDOtp6QPFo1iIyawyXg0YI3CYM9HBy1WvwCRHnPep/BvI1+dGPKoXx/Q==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-repeat-style@6.0.2: + resolution: {integrity: sha512-YdCgsfHkJ2jEXwR4RR3Tm/iOxSfdRt7jplS6XRh9Js9PyCR/aka/FCb6TuHT2U8gQubbm/mPmF6L7FY9d79VwQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-string@6.0.2: + resolution: {integrity: sha512-vQZIivlxlfqqMp4L9PZsFE4YUkWniziKjQWUtsxUiVsSSPelQydwS8Wwcuw0+83ZjPWNTl02oxlIvXsmmG+CiQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-timing-functions@6.0.2: + resolution: {integrity: sha512-a+YrtMox4TBtId/AEwbA03VcJgtyW4dGBizPl7e88cTFULYsprgHWTbfyjSLyHeBcK/Q9JhXkt2ZXiwaVHoMzA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-unicode@6.1.0: + resolution: {integrity: sha512-QVC5TQHsVj33otj8/JD869Ndr5Xcc/+fwRh4HAsFsAeygQQXm+0PySrKbr/8tkDKzW+EVT3QkqZMfFrGiossDg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-url@6.0.2: + resolution: {integrity: sha512-kVNcWhCeKAzZ8B4pv/DnrU1wNh458zBNp8dh4y5hhxih5RZQ12QWMuQrDgPRw3LRl8mN9vOVfHl7uhvHYMoXsQ==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-normalize-whitespace@6.0.2: + resolution: {integrity: sha512-sXZ2Nj1icbJOKmdjXVT9pnyHQKiSAyuNQHSgRCUgThn2388Y9cGVDR+E9J9iAYbSbLHI+UUwLVl1Wzco/zgv0Q==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-opacity-percentage@3.0.0: + resolution: {integrity: sha512-K6HGVzyxUxd/VgZdX04DCtdwWJ4NGLG212US4/LA1TLAbHgmAsTWVR86o+gGIbFtnTkfOpb9sCRBx8K7HO66qQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-ordered-values@6.0.2: + resolution: {integrity: sha512-VRZSOB+JU32RsEAQrO94QPkClGPKJEL/Z9PCBImXMhIeK5KAYo6slP/hBYlLgrCjFxyqvn5VC81tycFEDBLG1Q==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-overflow-shorthand@6.0.0: + resolution: {integrity: sha512-BdDl/AbVkDjoTofzDQnwDdm/Ym6oS9KgmO7Gr+LHYjNWJ6ExORe4+3pcLQsLA9gIROMkiGVjjwZNoL/mpXHd5Q==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-page-break@3.0.4: + resolution: {integrity: sha512-1JGu8oCjVXLa9q9rFTo4MbeeA5FMe00/9C7lN4va606Rdb+HkxXtXsmEDrIraQ11fGz/WvKWa8gMuCKkrXpTsQ==} + peerDependencies: + postcss: ^8 + + postcss-place@10.0.0: + resolution: {integrity: sha512-5EBrMzat2pPAxQNWYavwAfoKfYcTADJ8AXGVPcUZ2UkNloUTWzJQExgrzrDkh3EKzmAx1evfTAzF9I8NGcc+qw==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-preset-env@10.1.1: + resolution: {integrity: sha512-wqqsnBFD6VIwcHHRbhjTOcOi4qRVlB26RwSr0ordPj7OubRRxdWebv/aLjKLRR8zkZrbxZyuus03nOIgC5elMQ==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-pseudo-class-any-link@10.0.1: + resolution: {integrity: sha512-3el9rXlBOqTFaMFkWDOkHUTQekFIYnaQY55Rsp8As8QQkpiSgIYEcF/6Ond93oHiDsGb4kad8zjt+NPlOC1H0Q==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-reduce-idents@6.0.3: + resolution: {integrity: sha512-G3yCqZDpsNPoQgbDUy3T0E6hqOQ5xigUtBQyrmq3tn2GxlyiL0yyl7H+T8ulQR6kOcHJ9t7/9H4/R2tv8tJbMA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-reduce-initial@6.1.0: + resolution: {integrity: sha512-RarLgBK/CrL1qZags04oKbVbrrVK2wcxhvta3GCxrZO4zveibqbRPmm2VI8sSgCXwoUHEliRSbOfpR0b/VIoiw==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-reduce-transforms@6.0.2: + resolution: {integrity: sha512-sB+Ya++3Xj1WaT9+5LOOdirAxP7dJZms3GRcYheSPi1PiTMigsxHAdkrbItHxwYHr4kt1zL7mmcHstgMYT+aiA==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-replace-overflow-wrap@4.0.0: + resolution: {integrity: sha512-KmF7SBPphT4gPPcKZc7aDkweHiKEEO8cla/GjcBK+ckKxiZslIu3C4GCRW3DNfL0o7yW7kMQu9xlZ1kXRXLXtw==} + peerDependencies: + postcss: ^8.0.3 + + postcss-selector-not@8.0.1: + resolution: {integrity: sha512-kmVy/5PYVb2UOhy0+LqUYAhKj7DUGDpSWa5LZqlkWJaaAV+dxxsOG3+St0yNLu6vsKD7Dmqx+nWQt0iil89+WA==} + engines: {node: '>=18'} + peerDependencies: + postcss: ^8.4 + + postcss-selector-parser@6.1.2: + resolution: {integrity: sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==} + engines: {node: '>=4'} + + postcss-selector-parser@7.0.0: + resolution: {integrity: sha512-9RbEr1Y7FFfptd/1eEdntyjMwLeghW1bHX9GWjXo19vx4ytPQhANltvVxDggzJl7mnWM+dX28kb6cyS/4iQjlQ==} + engines: {node: '>=4'} + + postcss-sort-media-queries@5.2.0: + resolution: {integrity: sha512-AZ5fDMLD8SldlAYlvi8NIqo0+Z8xnXU2ia0jxmuhxAU+Lqt9K+AlmLNJ/zWEnE9x+Zx3qL3+1K20ATgNOr3fAA==} + engines: {node: '>=14.0.0'} + peerDependencies: + postcss: ^8.4.23 + + postcss-svgo@6.0.3: + resolution: {integrity: sha512-dlrahRmxP22bX6iKEjOM+c8/1p+81asjKT+V5lrgOH944ryx/OHpclnIbGsKVd3uWOXFLYJwCVf0eEkJGvO96g==} + engines: {node: ^14 || ^16 || >= 18} + peerDependencies: + postcss: ^8.4.31 + + postcss-unique-selectors@6.0.4: + resolution: {integrity: sha512-K38OCaIrO8+PzpArzkLKB42dSARtC2tmG6PvD4b1o1Q2E9Os8jzfWFfSy/rixsHwohtsDdFtAWGjFVFUdwYaMg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss-value-parser@4.2.0: + resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==} + + postcss-zindex@6.0.2: + resolution: {integrity: sha512-5BxW9l1evPB/4ZIc+2GobEBoKC+h8gPGCMi+jxsYvd2x0mjq7wazk6DrP71pStqxE9Foxh5TVnonbWpFZzXaYg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + postcss@8.4.49: + resolution: {integrity: sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA==} + engines: {node: ^10 || ^12 || >=14} + + preact@10.25.1: + resolution: {integrity: sha512-frxeZV2vhQSohQwJ7FvlqC40ze89+8friponWUFeVEkaCfhC6Eu4V0iND5C9CXz8JLndV07QRDeXzH1+Anz5Og==} + + prebuild-install@7.1.2: + resolution: {integrity: sha512-UnNke3IQb6sgarcZIDU3gbMeTp/9SSU1DAIkil7PrqG1vZlBtY5msYccSKSHDqa3hNg436IXK+SNImReuA1wEQ==} + engines: {node: '>=10'} + hasBin: true + + pretty-error@4.0.0: + resolution: {integrity: sha512-AoJ5YMAcXKYxKhuJGdcvse+Voc6v1RgnsR3nWcYU7q4t6z0Q6T86sv5Zq8VIRbOWWFpvdGE83LtdSMNd+6Y0xw==} + + pretty-time@1.1.0: + resolution: {integrity: sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA==} + engines: {node: '>=4'} + + prism-react-renderer@2.4.0: + resolution: {integrity: sha512-327BsVCD/unU4CNLZTWVHyUHKnsqcvj2qbPlQ8MiBE2eq2rgctjigPA1Gp9HLF83kZ20zNN6jgizHJeEsyFYOw==} + peerDependencies: + react: '>=16.0.0' + + prismjs@1.29.0: + resolution: {integrity: sha512-Kx/1w86q/epKcmte75LNrEoT+lX8pBpavuAbvJWRXar7Hz8jrtF+e3vY751p0R8H9HdArwaCTNDDzHg/ScJK1Q==} + engines: {node: '>=6'} + + process-nextick-args@2.0.1: + resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==} + + prompts@2.4.2: + resolution: {integrity: sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==} + engines: {node: '>= 6'} + + prop-types@15.8.1: + resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==} + + property-information@6.5.0: + resolution: {integrity: sha512-PgTgs/BlvHxOu8QuEN7wi5A0OmXaBcHpmCSTehcs6Uuu9IkDIEo13Hy7n898RHfrQ49vKCoGeWZSaAK01nwVig==} + + proto-list@1.2.4: + resolution: {integrity: sha512-vtK/94akxsTMhe0/cbfpR+syPuszcuwhqVjJq26CuNDgFGj682oRBXOP5MJpv2r7JtE8MsiepGIqvvOTBwn2vA==} + + proxy-addr@2.0.7: + resolution: {integrity: sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==} + engines: {node: '>= 0.10'} + + pump@3.0.2: + resolution: {integrity: sha512-tUPXtzlGM8FE3P0ZL6DVs/3P58k9nk8/jZeQCurTJylQA8qFYzHFfhBJkuqyE0FifOsQ0uKWekiZ5g8wtr28cw==} + + punycode@2.3.1: + resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==} + engines: {node: '>=6'} + + pupa@3.1.0: + resolution: {integrity: sha512-FLpr4flz5xZTSJxSeaheeMKN/EDzMdK7b8PTOC6a5PYFKTucWbdqjgqaEyH0shFiSJrVB1+Qqi4Tk19ccU6Aug==} + engines: {node: '>=12.20'} + + qs@6.13.0: + resolution: {integrity: sha512-+38qI9SOr8tfZ4QmJNplMUxqjbe7LKvvZgWdExBOmd+egZTtjLB67Gu0HRX3u/XOq7UU2Nx6nsjvS16Z9uwfpg==} + engines: {node: '>=0.6'} + + queue-microtask@1.2.3: + resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==} + + queue-tick@1.0.1: + resolution: {integrity: sha512-kJt5qhMxoszgU/62PLP1CJytzd2NKetjSRnyuj31fDd3Rlcz3fzlFdFLD1SItunPwyqEOkca6GbV612BWfaBag==} + + queue@6.0.2: + resolution: {integrity: sha512-iHZWu+q3IdFZFX36ro/lKBkSvfkztY5Y7HMiPlOUjhupPcG2JMfst2KKEpu5XndviX/3UhFbRngUPNKtgvtZiA==} + + quick-lru@5.1.1: + resolution: {integrity: sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==} + engines: {node: '>=10'} + + randombytes@2.1.0: + resolution: {integrity: sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==} + + range-parser@1.2.0: + resolution: {integrity: sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A==} + engines: {node: '>= 0.6'} + + range-parser@1.2.1: + resolution: {integrity: sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==} + engines: {node: '>= 0.6'} + + raw-body@2.5.2: + resolution: {integrity: sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==} + engines: {node: '>= 0.8'} + + rc@1.2.8: + resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==} + hasBin: true + + react-dev-utils@12.0.1: + resolution: {integrity: sha512-84Ivxmr17KjUupyqzFode6xKhjwuEJDROWKJy/BthkL7Wn6NJ8h4WE6k/exAv6ImS+0oZLRRW5j/aINMHyeGeQ==} + engines: {node: '>=14'} + peerDependencies: + typescript: '>=2.7' + webpack: '>=4' + peerDependenciesMeta: + typescript: + optional: true + + react-dom@18.3.1: + resolution: {integrity: sha512-5m4nQKp+rZRb09LNH59GM4BxTh9251/ylbKIbpe7TpGxfJ+9kv6BLkLBXIjjspbgbnIBNqlI23tRnTWT0snUIw==} + peerDependencies: + react: ^18.3.1 + + react-error-overlay@6.0.11: + resolution: {integrity: sha512-/6UZ2qgEyH2aqzYZgQPxEnz33NJ2gNsnHA2o5+o4wW9bLM/JYQitNP9xPhsXwC08hMMovfGe/8retsdDsczPRg==} + + react-fast-compare@3.2.2: + resolution: {integrity: sha512-nsO+KSNgo1SbJqJEYRE9ERzo7YtYbou/OqjSQKxV7jcKox7+usiUVZOAC+XnDOABXggQTno0Y1CpVnuWEc1boQ==} + + react-helmet-async@1.3.0: + resolution: {integrity: sha512-9jZ57/dAn9t3q6hneQS0wukqC2ENOBgMNVEhb/ZG9ZSxUetzVIw4iAmEU38IaVg3QGYauQPhSeUTuIUtFglWpg==} + peerDependencies: + react: ^16.6.0 || ^17.0.0 || ^18.0.0 + react-dom: ^16.6.0 || ^17.0.0 || ^18.0.0 + + react-helmet-async@2.0.5: + resolution: {integrity: sha512-rYUYHeus+i27MvFE+Jaa4WsyBKGkL6qVgbJvSBoX8mbsWoABJXdEO0bZyi0F6i+4f0NuIb8AvqPMj3iXFHkMwg==} + peerDependencies: + react: ^16.6.0 || ^17.0.0 || ^18.0.0 + + react-is@16.13.1: + resolution: {integrity: sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==} + + react-is@18.3.1: + resolution: {integrity: sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg==} + + react-json-view-lite@1.5.0: + resolution: {integrity: sha512-nWqA1E4jKPklL2jvHWs6s+7Na0qNgw9HCP6xehdQJeg6nPBTFZgGwyko9Q0oj+jQWKTTVRS30u0toM5wiuL3iw==} + engines: {node: '>=14'} + peerDependencies: + react: ^16.13.1 || ^17.0.0 || ^18.0.0 + + react-loadable-ssr-addon-v5-slorber@1.0.1: + resolution: {integrity: sha512-lq3Lyw1lGku8zUEJPDxsNm1AfYHBrO9Y1+olAYwpUJ2IGFBskM0DMKok97A6LWUpHm+o7IvQBOWu9MLenp9Z+A==} + engines: {node: '>=10.13.0'} + peerDependencies: + react-loadable: '*' + webpack: '>=4.41.1 || 5.x' + + react-router-config@5.1.1: + resolution: {integrity: sha512-DuanZjaD8mQp1ppHjgnnUnyOlqYXZVjnov/JzFhjLEwd3Z4dYjMSnqrEzzGThH47vpCOqPPwJM2FtthLeJ8Pbg==} + peerDependencies: + react: '>=15' + react-router: '>=5' + + react-router-dom@5.3.4: + resolution: {integrity: sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ==} + peerDependencies: + react: '>=15' + + react-router@5.3.4: + resolution: {integrity: sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA==} + peerDependencies: + react: '>=15' + + react-waypoint@10.3.0: + resolution: {integrity: sha512-iF1y2c1BsoXuEGz08NoahaLFIGI9gTUAAOKip96HUmylRT6DUtpgoBPjk/Y8dfcFVmfVDvUzWjNXpZyKTOV0SQ==} + peerDependencies: + react: ^15.3.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 + + react@18.3.1: + resolution: {integrity: sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ==} + engines: {node: '>=0.10.0'} + + readable-stream@2.3.8: + resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==} + + readable-stream@3.6.2: + resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==} + engines: {node: '>= 6'} + + readdirp@3.6.0: + resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==} + engines: {node: '>=8.10.0'} + + reading-time@1.5.0: + resolution: {integrity: sha512-onYyVhBNr4CmAxFsKS7bz+uTLRakypIe4R+5A824vBSkQy/hB3fZepoVEf8OVAxzLvK+H/jm9TzpI3ETSm64Kg==} + + rechoir@0.6.2: + resolution: {integrity: sha512-HFM8rkZ+i3zrV+4LQjwQ0W+ez98pApMGM3HUrN04j3CqzPOzl9nmP15Y8YXNm8QHGv/eacOVEjqhmWpkRV0NAw==} + engines: {node: '>= 0.10'} + + recma-build-jsx@1.0.0: + resolution: {integrity: sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew==} + + recma-jsx@1.0.0: + resolution: {integrity: sha512-5vwkv65qWwYxg+Atz95acp8DMu1JDSqdGkA2Of1j6rCreyFUE/gp15fC8MnGEuG1W68UKjM6x6+YTWIh7hZM/Q==} + + recma-parse@1.0.0: + resolution: {integrity: sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ==} + + recma-stringify@1.0.0: + resolution: {integrity: sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g==} + + recursive-readdir@2.2.3: + resolution: {integrity: sha512-8HrF5ZsXk5FAH9dgsx3BlUer73nIhuj+9OrQwEbLTPOBzGkL1lsFCR01am+v+0m2Cmbs1nP12hLDl5FA7EszKA==} + engines: {node: '>=6.0.0'} + + regenerate-unicode-properties@10.2.0: + resolution: {integrity: sha512-DqHn3DwbmmPVzeKj9woBadqmXxLvQoQIwu7nopMc72ztvxVmVk2SBhSnx67zuye5TP+lJsb/TBQsjLKhnDf3MA==} + engines: {node: '>=4'} + + regenerate@1.4.2: + resolution: {integrity: sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==} + + regenerator-runtime@0.14.1: + resolution: {integrity: sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw==} + + regenerator-transform@0.15.2: + resolution: {integrity: sha512-hfMp2BoF0qOk3uc5V20ALGDS2ddjQaLrdl7xrGXvAIow7qeWRM2VA2HuCHkUKk9slq3VwEwLNK3DFBqDfPGYtg==} + + regexpu-core@6.2.0: + resolution: {integrity: sha512-H66BPQMrv+V16t8xtmq+UC0CBpiTBA60V8ibS1QVReIp8T1z8hwFxqcGzm9K6lgsN7sB5edVH8a+ze6Fqm4weA==} + engines: {node: '>=4'} + + registry-auth-token@5.0.3: + resolution: {integrity: sha512-1bpc9IyC+e+CNFRaWyn77tk4xGG4PPUyfakSmA6F6cvUDjrm58dfyJ3II+9yb10EDkHoy1LaPSmHaWLOH3m6HA==} + engines: {node: '>=14'} + + registry-url@6.0.1: + resolution: {integrity: sha512-+crtS5QjFRqFCoQmvGduwYWEBng99ZvmFvF+cUJkGYF1L1BfU8C6Zp9T7f5vPAwyLkUExpvK+ANVZmGU49qi4Q==} + engines: {node: '>=12'} + + regjsgen@0.8.0: + resolution: {integrity: sha512-RvwtGe3d7LvWiDQXeQw8p5asZUmfU1G/l6WbUXeHta7Y2PEIvBTwH6E2EfmYUK8pxcxEdEmaomqyp0vZZ7C+3Q==} + + regjsparser@0.12.0: + resolution: {integrity: sha512-cnE+y8bz4NhMjISKbgeVJtqNbtf5QpjZP+Bslo+UqkIt9QPnX9q095eiRRASJG1/tz6dlNr6Z5NsBiWYokp6EQ==} + hasBin: true + + rehype-raw@7.0.0: + resolution: {integrity: sha512-/aE8hCfKlQeA8LmyeyQvQF3eBiLRGNlfBJEvWH7ivp9sBqs7TNqBL5X3v157rM4IFETqDnIOO+z5M/biZbo9Ww==} + + rehype-recma@1.0.0: + resolution: {integrity: sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw==} + + relateurl@0.2.7: + resolution: {integrity: sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog==} + engines: {node: '>= 0.10'} + + remark-directive@3.0.0: + resolution: {integrity: sha512-l1UyWJ6Eg1VPU7Hm/9tt0zKtReJQNOA4+iDMAxTyZNWnJnFlbS/7zhiel/rogTLQ2vMYwDzSJa4BiVNqGlqIMA==} + + remark-emoji@4.0.1: + resolution: {integrity: sha512-fHdvsTR1dHkWKev9eNyhTo4EFwbUvJ8ka9SgeWkMPYFX4WoI7ViVBms3PjlQYgw5TLvNQso3GUB/b/8t3yo+dg==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} + + remark-frontmatter@5.0.0: + resolution: {integrity: sha512-XTFYvNASMe5iPN0719nPrdItC9aU0ssC4v14mH1BCi1u0n1gAocqcujWUrByftZTbLhRtiKRyjYTSIOcr69UVQ==} + + remark-gfm@4.0.0: + resolution: {integrity: sha512-U92vJgBPkbw4Zfu/IiW2oTZLSL3Zpv+uI7My2eq8JxKgqraFdU8YUGicEJCEgSbeaG+QDFqIcwwfMTOEelPxuA==} + + remark-mdx@3.1.0: + resolution: {integrity: sha512-Ngl/H3YXyBV9RcRNdlYsZujAmhsxwzxpDzpDEhFBVAGthS4GDgnctpDjgFl/ULx5UEDzqtW1cyBSNKqYYrqLBA==} + + remark-parse@11.0.0: + resolution: {integrity: sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==} + + remark-rehype@11.1.1: + resolution: {integrity: sha512-g/osARvjkBXb6Wo0XvAeXQohVta8i84ACbenPpoSsxTOQH/Ae0/RGP4WZgnMH5pMLpsj4FG7OHmcIcXxpza8eQ==} + + remark-stringify@11.0.0: + resolution: {integrity: sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==} + + renderkid@3.0.0: + resolution: {integrity: sha512-q/7VIQA8lmM1hF+jn+sFSPWGlMkSAeNYcPLmDQx2zzuiDfaLrOmumR8iaUKlenFgh0XRPIUeSPlH3A+AW3Z5pg==} + + repeat-string@1.6.1: + resolution: {integrity: sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==} + engines: {node: '>=0.10'} + + require-from-string@2.0.2: + resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==} + engines: {node: '>=0.10.0'} + + require-like@0.1.2: + resolution: {integrity: sha512-oyrU88skkMtDdauHDuKVrgR+zuItqr6/c//FXzvmxRGMexSDc6hNvJInGW3LL46n+8b50RykrvwSUIIQH2LQ5A==} + + requires-port@1.0.0: + resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==} + + resolve-alpn@1.2.1: + resolution: {integrity: sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g==} + + resolve-from@4.0.0: + resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==} + engines: {node: '>=4'} + + resolve-package-path@4.0.3: + resolution: {integrity: sha512-SRpNAPW4kewOaNUt8VPqhJ0UMxawMwzJD8V7m1cJfdSTK9ieZwS6K7Dabsm4bmLFM96Z5Y/UznrpG5kt1im8yA==} + engines: {node: '>= 12'} + + resolve-pathname@3.0.0: + resolution: {integrity: sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng==} + + resolve@1.22.8: + resolution: {integrity: sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==} + hasBin: true + + responselike@3.0.0: + resolution: {integrity: sha512-40yHxbNcl2+rzXvZuVkrYohathsSJlMTXKryG5y8uciHv1+xDLHQpgjG64JUO9nrEq2jGLH6IZ8BcZyw3wrweg==} + engines: {node: '>=14.16'} + + retry@0.13.1: + resolution: {integrity: sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==} + engines: {node: '>= 4'} + + reusify@1.0.4: + resolution: {integrity: sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==} + engines: {iojs: '>=1.0.0', node: '>=0.10.0'} + + rimraf@3.0.2: + resolution: {integrity: sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==} + deprecated: Rimraf versions prior to v4 are no longer supported + hasBin: true + + rtl-detect@1.1.2: + resolution: {integrity: sha512-PGMBq03+TTG/p/cRB7HCLKJ1MgDIi07+QU1faSjiYRfmY5UsAttV9Hs08jDAHVwcOwmVLcSJkpwyfXszVjWfIQ==} + + rtlcss@4.3.0: + resolution: {integrity: sha512-FI+pHEn7Wc4NqKXMXFM+VAYKEj/mRIcW4h24YVwVtyjI+EqGrLc2Hx/Ny0lrZ21cBWU2goLy36eqMcNj3AQJig==} + engines: {node: '>=12.0.0'} + hasBin: true + + run-parallel@1.2.0: + resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==} + + safe-buffer@5.1.2: + resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==} + + safe-buffer@5.2.1: + resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==} + + safer-buffer@2.1.2: + resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==} + + sax@1.4.1: + resolution: {integrity: sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg==} + + scheduler@0.23.2: + resolution: {integrity: sha512-UOShsPwz7NrMUqhR6t0hWjFduvOzbtv7toDH1/hIrfRNIDBnnBWd0CwJTGvTpngVlmwGCdP9/Zl/tVrDqcuYzQ==} + + schema-utils@2.7.0: + resolution: {integrity: sha512-0ilKFI6QQF5nxDZLFn2dMjvc4hjg/Wkg7rHd3jK6/A4a1Hl9VFdQWvgB1UMGoU94pad1P/8N7fMcEnLnSiju8A==} + engines: {node: '>= 8.9.0'} + + schema-utils@3.3.0: + resolution: {integrity: sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==} + engines: {node: '>= 10.13.0'} + + schema-utils@4.2.0: + resolution: {integrity: sha512-L0jRsrPpjdckP3oPug3/VxNKt2trR8TcabrM6FOAAlvC/9Phcmm+cuAgTlxBqdBR1WJx7Naj9WHw+aOmheSVbw==} + engines: {node: '>= 12.13.0'} + + search-insights@2.17.3: + resolution: {integrity: sha512-RQPdCYTa8A68uM2jwxoY842xDhvx3E5LFL1LxvxCNMev4o5mLuokczhzjAgGwUZBAmOKZknArSxLKmXtIi2AxQ==} + + section-matter@1.0.0: + resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==} + engines: {node: '>=4'} + + select-hose@2.0.0: + resolution: {integrity: sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg==} + + selfsigned@2.4.1: + resolution: {integrity: sha512-th5B4L2U+eGLq1TVh7zNRGBapioSORUeymIydxgFpwww9d2qyKvtuPU2jJuHvYAwwqi2Y596QBL3eEqcPEYL8Q==} + engines: {node: '>=10'} + + semver-diff@4.0.0: + resolution: {integrity: sha512-0Ju4+6A8iOnpL/Thra7dZsSlOHYAHIeMxfhWQRI1/VLcT3WDBZKKtQt/QkBOsiIN9ZpuvHE6cGZ0x4glCMmfiA==} + engines: {node: '>=12'} + + semver@6.3.1: + resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==} + hasBin: true + + semver@7.6.3: + resolution: {integrity: sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==} + engines: {node: '>=10'} + hasBin: true + + send@0.19.0: + resolution: {integrity: sha512-dW41u5VfLXu8SJh5bwRmyYUbAoSB3c9uQh6L8h/KtsFREPWpbX1lrljJo186Jc4nmci/sGUZ9a0a0J2zgfq2hw==} + engines: {node: '>= 0.8.0'} + + serialize-javascript@6.0.2: + resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==} + + serve-handler@6.1.6: + resolution: {integrity: sha512-x5RL9Y2p5+Sh3D38Fh9i/iQ5ZK+e4xuXRd/pGbM4D13tgo/MGwbttUk8emytcr1YYzBYs+apnUngBDFYfpjPuQ==} + + serve-index@1.9.1: + resolution: {integrity: sha512-pXHfKNP4qujrtteMrSBb0rc8HJ9Ms/GrXwcUtUtD5s4ewDJI8bT3Cz2zTVRMKtri49pLx2e0Ya8ziP5Ya2pZZw==} + engines: {node: '>= 0.8.0'} + + serve-static@1.16.2: + resolution: {integrity: sha512-VqpjJZKadQB/PEbEwvFdO43Ax5dFBZ2UECszz8bQ7pi7wt//PWe1P6MN7eCnjsatYtBT6EuiClbjSWP2WrIoTw==} + engines: {node: '>= 0.8.0'} + + set-function-length@1.2.2: + resolution: {integrity: sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==} + engines: {node: '>= 0.4'} + + setprototypeof@1.1.0: + resolution: {integrity: sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==} + + setprototypeof@1.2.0: + resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==} + + shallow-clone@3.0.1: + resolution: {integrity: sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==} + engines: {node: '>=8'} + + shallowequal@1.1.0: + resolution: {integrity: sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==} + + sharp@0.32.6: + resolution: {integrity: sha512-KyLTWwgcR9Oe4d9HwCwNM2l7+J0dUQwn/yf7S0EnTtb0eVS4RxO0eUSvxPtzT4F3SY+C4K6fqdv/DO27sJ/v/w==} + engines: {node: '>=14.15.0'} + + shebang-command@2.0.0: + resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==} + engines: {node: '>=8'} + + shebang-regex@3.0.0: + resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==} + engines: {node: '>=8'} + + shell-quote@1.8.2: + resolution: {integrity: sha512-AzqKpGKjrj7EM6rKVQEPpB288oCfnrEIuyoT9cyF4nmGa7V8Zk6f7RRqYisX8X9m+Q7bd632aZW4ky7EhbQztA==} + engines: {node: '>= 0.4'} + + shelljs@0.8.5: + resolution: {integrity: sha512-TiwcRcrkhHvbrZbnRcFYMLl30Dfov3HKqzp5tO5b4pt6G/SezKcYhmDg15zXVBswHmctSAQKznqNW2LO5tTDow==} + engines: {node: '>=4'} + hasBin: true + + side-channel@1.0.6: + resolution: {integrity: sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA==} + engines: {node: '>= 0.4'} + + signal-exit@3.0.7: + resolution: {integrity: sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==} + + simple-concat@1.0.1: + resolution: {integrity: sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q==} + + simple-get@4.0.1: + resolution: {integrity: sha512-brv7p5WgH0jmQJr1ZDDfKDOSeWWg+OVypG99A/5vYGPqJ6pxiaHLy8nxtFjBA7oMa01ebA9gfh1uMCFqOuXxvA==} + + simple-swizzle@0.2.2: + resolution: {integrity: sha512-JA//kQgZtbuY83m+xT+tXJkmJncGMTFT+C+g2h2R9uxkYIrE2yy9sgmcLhCnw57/WSD+Eh3J97FPEDFnbXnDUg==} + + sirv@2.0.4: + resolution: {integrity: sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ==} + engines: {node: '>= 10'} + + sisteransi@1.0.5: + resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==} + + sitemap@7.1.2: + resolution: {integrity: sha512-ARCqzHJ0p4gWt+j7NlU5eDlIO9+Rkr/JhPFZKKQ1l5GCus7rJH4UdrlVAh0xC/gDS/Qir2UMxqYNHtsKr2rpCw==} + engines: {node: '>=12.0.0', npm: '>=5.6.0'} + hasBin: true + + skin-tone@2.0.0: + resolution: {integrity: sha512-kUMbT1oBJCpgrnKoSr0o6wPtvRWT9W9UKvGLwfJYO2WuahZRHOpEyL1ckyMGgMWh0UdpmaoFqKKD29WTomNEGA==} + engines: {node: '>=8'} + + slash@3.0.0: + resolution: {integrity: sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==} + engines: {node: '>=8'} + + slash@4.0.0: + resolution: {integrity: sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==} + engines: {node: '>=12'} + + snake-case@3.0.4: + resolution: {integrity: sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==} + + sockjs@0.3.24: + resolution: {integrity: sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ==} + + sort-css-media-queries@2.2.0: + resolution: {integrity: sha512-0xtkGhWCC9MGt/EzgnvbbbKhqWjl1+/rncmhTh5qCpbYguXh6S/qwePfv/JQ8jePXXmqingylxoC49pCkSPIbA==} + engines: {node: '>= 6.3.0'} + + source-map-js@1.2.1: + resolution: {integrity: sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==} + engines: {node: '>=0.10.0'} + + source-map-support@0.5.21: + resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==} + + source-map@0.6.1: + resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==} + engines: {node: '>=0.10.0'} + + source-map@0.7.4: + resolution: {integrity: sha512-l3BikUxvPOcn5E74dZiq5BGsTb5yEwhaTSzccU6t4sDOH8NWJCstKO5QT2CvtFoK6F0saL7p9xHAqHOlCPJygA==} + engines: {node: '>= 8'} + + space-separated-tokens@2.0.2: + resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==} + + spdy-transport@3.0.0: + resolution: {integrity: sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==} + + spdy@4.0.2: + resolution: {integrity: sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA==} + engines: {node: '>=6.0.0'} + + sprintf-js@1.0.3: + resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==} + + srcset@4.0.0: + resolution: {integrity: sha512-wvLeHgcVHKO8Sc/H/5lkGreJQVeYMm9rlmt8PuR1xE31rIuXhuzznUUqAt8MqLhB3MqJdFzlNAfpcWnxiFUcPw==} + engines: {node: '>=12'} + + statuses@1.5.0: + resolution: {integrity: sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==} + engines: {node: '>= 0.6'} + + statuses@2.0.1: + resolution: {integrity: sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==} + engines: {node: '>= 0.8'} + + std-env@3.8.0: + resolution: {integrity: sha512-Bc3YwwCB+OzldMxOXJIIvC6cPRWr/LxOp48CdQTOkPyk/t4JWWJbrilwBd7RJzKV8QW7tJkcgAmeuLLJugl5/w==} + + streamx@2.21.0: + resolution: {integrity: sha512-Qz6MsDZXJ6ur9u+b+4xCG18TluU7PGlRfXVAAjNiGsFrBUt/ioyLkxbFaKJygoPs+/kW4VyBj0bSj89Qu0IGyg==} + + string-width@4.2.3: + resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==} + engines: {node: '>=8'} + + string-width@5.1.2: + resolution: {integrity: sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==} + engines: {node: '>=12'} + + string_decoder@1.1.1: + resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==} + + string_decoder@1.3.0: + resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==} + + stringify-entities@4.0.4: + resolution: {integrity: sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==} + + stringify-object@3.3.0: + resolution: {integrity: sha512-rHqiFh1elqCQ9WPLIC8I0Q/g/wj5J1eMkyoiD6eoQApWHP0FtlK7rqnhmabL5VUY9JQCcqwwvlOaSuutekgyrw==} + engines: {node: '>=4'} + + strip-ansi@6.0.1: + resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==} + engines: {node: '>=8'} + + strip-ansi@7.1.0: + resolution: {integrity: sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==} + engines: {node: '>=12'} + + strip-bom-string@1.0.0: + resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==} + engines: {node: '>=0.10.0'} + + strip-final-newline@2.0.0: + resolution: {integrity: sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==} + engines: {node: '>=6'} + + strip-json-comments@2.0.1: + resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==} + engines: {node: '>=0.10.0'} + + strip-json-comments@3.1.1: + resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==} + engines: {node: '>=8'} + + style-to-object@0.4.4: + resolution: {integrity: sha512-HYNoHZa2GorYNyqiCaBgsxvcJIn7OHq6inEga+E6Ke3m5JkoqpQbnFssk4jwe+K7AhGa2fcha4wSOf1Kn01dMg==} + + style-to-object@1.0.8: + resolution: {integrity: sha512-xT47I/Eo0rwJmaXC4oilDGDWLohVhR6o/xAQcPQN8q6QBuZVL8qMYL85kLmST5cPjAorwvqIA4qXTRQoYHaL6g==} + + stylehacks@6.1.1: + resolution: {integrity: sha512-gSTTEQ670cJNoaeIp9KX6lZmm8LJ3jPB5yJmX8Zq/wQxOsAFXV3qjWzHas3YYk1qesuVIyYWWUpZ0vSE/dTSGg==} + engines: {node: ^14 || ^16 || >=18.0} + peerDependencies: + postcss: ^8.4.31 + + supports-color@7.2.0: + resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==} + engines: {node: '>=8'} + + supports-color@8.1.1: + resolution: {integrity: sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==} + engines: {node: '>=10'} + + supports-preserve-symlinks-flag@1.0.0: + resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==} + engines: {node: '>= 0.4'} + + svg-parser@2.0.4: + resolution: {integrity: sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ==} + + svgo@3.3.2: + resolution: {integrity: sha512-OoohrmuUlBs8B8o6MB2Aevn+pRIH9zDALSR+6hhqVfa6fRwG/Qw9VUMSMW9VNg2CFc/MTIfabtdOVl9ODIJjpw==} + engines: {node: '>=14.0.0'} + hasBin: true + + swc-loader@0.2.6: + resolution: {integrity: sha512-9Zi9UP2YmDpgmQVbyOPJClY0dwf58JDyDMQ7uRc4krmc72twNI2fvlBWHLqVekBpPc7h5NJkGVT1zNDxFrqhvg==} + peerDependencies: + '@swc/core': ^1.2.147 + webpack: '>=2' + + tapable@1.1.3: + resolution: {integrity: sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==} + engines: {node: '>=6'} + + tapable@2.2.1: + resolution: {integrity: sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==} + engines: {node: '>=6'} + + tar-fs@2.1.1: + resolution: {integrity: sha512-V0r2Y9scmbDRLCNex/+hYzvp/zyYjvFbHPNgVTKfQvVrb6guiE/fxP+XblDNR011utopbkex2nM4dHNV6GDsng==} + + tar-fs@3.0.6: + resolution: {integrity: sha512-iokBDQQkUyeXhgPYaZxmczGPhnhXZ0CmrqI+MOb/WFGS9DW5wnfrLgtjUJBvz50vQ3qfRwJ62QVoCFu8mPVu5w==} + + tar-stream@2.2.0: + resolution: {integrity: sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ==} + engines: {node: '>=6'} + + tar-stream@3.1.7: + resolution: {integrity: sha512-qJj60CXt7IU1Ffyc3NJMjh6EkuCFej46zUqJ4J7pqYlThyd9bO0XBTmcOIhSzZJVWfsLks0+nle/j538YAW9RQ==} + + terser-webpack-plugin@5.3.10: + resolution: {integrity: sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w==} + engines: {node: '>= 10.13.0'} + peerDependencies: + '@swc/core': '*' + esbuild: '*' + uglify-js: '*' + webpack: ^5.1.0 + peerDependenciesMeta: + '@swc/core': + optional: true + esbuild: + optional: true + uglify-js: + optional: true + + terser@5.37.0: + resolution: {integrity: sha512-B8wRRkmre4ERucLM/uXx4MOV5cbnOlVAqUst+1+iLKPI0dOgFO28f84ptoQt9HEI537PMzfYa/d+GEPKTRXmYA==} + engines: {node: '>=10'} + hasBin: true + + text-decoder@1.2.2: + resolution: {integrity: sha512-/MDslo7ZyWTA2vnk1j7XoDVfXsGk3tp+zFEJHJGm0UjIlQifonVFwlVbQDFh8KJzTBnT8ie115TYqir6bclddA==} + + text-table@0.2.0: + resolution: {integrity: sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==} + + thunky@1.1.0: + resolution: {integrity: sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==} + + tiny-invariant@1.3.3: + resolution: {integrity: sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg==} + + tiny-warning@1.0.3: + resolution: {integrity: sha512-lBN9zLN/oAf68o3zNXYrdCt1kP8WsiGW8Oo2ka41b2IM5JL/S1CTyX1rW0mb/zSuJun0ZUrDxx4sqvYS2FWzPA==} + + to-regex-range@5.0.1: + resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==} + engines: {node: '>=8.0'} + + toidentifier@1.0.1: + resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==} + engines: {node: '>=0.6'} + + totalist@3.0.1: + resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==} + engines: {node: '>=6'} + + trim-lines@3.0.1: + resolution: {integrity: sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==} + + trough@2.2.0: + resolution: {integrity: sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw==} + + tslib@2.8.1: + resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==} + + tunnel-agent@0.6.0: + resolution: {integrity: sha512-McnNiV1l8RYeY8tBgEpuodCC1mLUdbSN+CYBL7kJsJNInOP8UjDDEwdk6Mw60vdLLrr5NHKZhMAOSrR2NZuQ+w==} + + type-fest@0.21.3: + resolution: {integrity: sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==} + engines: {node: '>=10'} + + type-fest@1.4.0: + resolution: {integrity: sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==} + engines: {node: '>=10'} + + type-fest@2.19.0: + resolution: {integrity: sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA==} + engines: {node: '>=12.20'} + + type-is@1.6.18: + resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==} + engines: {node: '>= 0.6'} + + typedarray-to-buffer@3.1.5: + resolution: {integrity: sha512-zdu8XMNEDepKKR+XYOXAVPtWui0ly0NtohUscw+UmaHiAWT8hrV1rr//H6V+0DvJ3OQ19S979M0laLfX8rm82Q==} + + typeface-roboto@1.1.13: + resolution: {integrity: sha512-YXvbd3a1QTREoD+FJoEkl0VQNJoEjewR2H11IjVv4bp6ahuIcw0yyw/3udC4vJkHw3T3cUh85FTg8eWef3pSaw==} + + typescript@5.7.2: + resolution: {integrity: sha512-i5t66RHxDvVN40HfDd1PsEThGNnlMCMT3jMUuoh9/0TaqWevNontacunWyN02LA9/fIbEWlcHZcgTKb9QoaLfg==} + engines: {node: '>=14.17'} + hasBin: true + + undici-types@6.20.0: + resolution: {integrity: sha512-Ny6QZ2Nju20vw1SRHe3d9jVu6gJ+4e3+MMpqu7pqE5HT6WsTSlce++GQmK5UXS8mzV8DSYHrQH+Xrf2jVcuKNg==} + + undici@6.21.0: + resolution: {integrity: sha512-BUgJXc752Kou3oOIuU1i+yZZypyZRqNPW0vqoMPl8VaoalSfeR0D8/t4iAS3yirs79SSMTxTag+ZC86uswv+Cw==} + engines: {node: '>=18.17'} + + unicode-canonical-property-names-ecmascript@2.0.1: + resolution: {integrity: sha512-dA8WbNeb2a6oQzAQ55YlT5vQAWGV9WXOsi3SskE3bcCdM0P4SDd+24zS/OCacdRq5BkdsRj9q3Pg6YyQoxIGqg==} + engines: {node: '>=4'} + + unicode-emoji-modifier-base@1.0.0: + resolution: {integrity: sha512-yLSH4py7oFH3oG/9K+XWrz1pSi3dfUrWEnInbxMfArOfc1+33BlGPQtLsOYwvdMy11AwUBetYuaRxSPqgkq+8g==} + engines: {node: '>=4'} + + unicode-match-property-ecmascript@2.0.0: + resolution: {integrity: sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==} + engines: {node: '>=4'} + + unicode-match-property-value-ecmascript@2.2.0: + resolution: {integrity: sha512-4IehN3V/+kkr5YeSSDDQG8QLqO26XpL2XP3GQtqwlT/QYSECAwFztxVHjlbh0+gjJ3XmNLS0zDsbgs9jWKExLg==} + engines: {node: '>=4'} + + unicode-property-aliases-ecmascript@2.1.0: + resolution: {integrity: sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w==} + engines: {node: '>=4'} + + unified@11.0.5: + resolution: {integrity: sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==} + + unique-string@3.0.0: + resolution: {integrity: sha512-VGXBUVwxKMBUznyffQweQABPRRW1vHZAbadFZud4pLFAqRGvv/96vafgjWFqzourzr8YonlQiPgH0YCJfawoGQ==} + engines: {node: '>=12'} + + unist-util-is@6.0.0: + resolution: {integrity: sha512-2qCTHimwdxLfz+YzdGfkqNlH0tLi9xjTnHddPmJwtIG9MGsdbutfTc4P+haPD7l7Cjxf/WZj+we5qfVPvvxfYw==} + + unist-util-position-from-estree@2.0.0: + resolution: {integrity: sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ==} + + unist-util-position@5.0.0: + resolution: {integrity: sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==} + + unist-util-stringify-position@4.0.0: + resolution: {integrity: sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==} + + unist-util-visit-parents@6.0.1: + resolution: {integrity: sha512-L/PqWzfTP9lzzEa6CKs0k2nARxTdZduw3zyh8d2NVBnsyvHjSX4TWse388YrrQKbvI8w20fGjGlhgT96WwKykw==} + + unist-util-visit@5.0.0: + resolution: {integrity: sha512-MR04uvD+07cwl/yhVuVWAtw+3GOR/knlL55Nd/wAdblk27GCVt3lqpTivy/tkJcZoNPzTwS1Y+KMojlLDhoTzg==} + + universalify@2.0.1: + resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==} + engines: {node: '>= 10.0.0'} + + unpipe@1.0.0: + resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==} + engines: {node: '>= 0.8'} + + update-browserslist-db@1.1.1: + resolution: {integrity: sha512-R8UzCaa9Az+38REPiJ1tXlImTJXlVfgHZsglwBD/k6nj76ctsH1E3q4doGrukiLQd3sGQYu56r5+lo5r94l29A==} + hasBin: true + peerDependencies: + browserslist: '>= 4.21.0' + + update-notifier@6.0.2: + resolution: {integrity: sha512-EDxhTEVPZZRLWYcJ4ZXjGFN0oP7qYvbXWzEgRm/Yql4dHX5wDbvh89YHP6PK1lzZJYrMtXUuZZz8XGK+U6U1og==} + engines: {node: '>=14.16'} + + uri-js@4.4.1: + resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==} + + url-loader@4.1.1: + resolution: {integrity: sha512-3BTV812+AVHHOJQO8O5MkWgZ5aosP7GnROJwvzLS9hWDj00lZ6Z0wNak423Lp9PBZN05N+Jk/N5Si8jRAlGyWA==} + engines: {node: '>= 10.13.0'} + peerDependencies: + file-loader: '*' + webpack: ^4.0.0 || ^5.0.0 + peerDependenciesMeta: + file-loader: + optional: true + + util-deprecate@1.0.2: + resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==} + + utila@0.4.0: + resolution: {integrity: sha512-Z0DbgELS9/L/75wZbro8xAnT50pBVFQZ+hUEueGDU5FN51YSCYM+jdxsfCiHjwNP/4LCDD0i/graKpeBnOXKRA==} + + utility-types@3.11.0: + resolution: {integrity: sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw==} + engines: {node: '>= 4'} + + utils-merge@1.0.1: + resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==} + engines: {node: '>= 0.4.0'} + + uuid@8.3.2: + resolution: {integrity: sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==} + hasBin: true + + validate-peer-dependencies@2.2.0: + resolution: {integrity: sha512-8X1OWlERjiUY6P6tdeU9E0EwO8RA3bahoOVG7ulOZT5MqgNDUO/BQoVjYiHPcNe+v8glsboZRIw9iToMAA2zAA==} + engines: {node: '>= 12'} + + value-equal@1.0.1: + resolution: {integrity: sha512-NOJ6JZCAWr0zlxZt+xqCHNTEKOsrks2HQd4MqhP1qy4z1SkbEP467eNx6TgDKXMvUOb+OENfJCZwM+16n7fRfw==} + + vary@1.1.2: + resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==} + engines: {node: '>= 0.8'} + + vfile-location@5.0.3: + resolution: {integrity: sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg==} + + vfile-message@4.0.2: + resolution: {integrity: sha512-jRDZ1IMLttGj41KcZvlrYAaI3CfqpLpfpf+Mfig13viT6NKvRzWZ+lXz0Y5D60w6uJIBAOGq9mSHf0gktF0duw==} + + vfile@6.0.3: + resolution: {integrity: sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==} + + watchpack@2.4.2: + resolution: {integrity: sha512-TnbFSbcOCcDgjZ4piURLCbJ3nJhznVh9kw6F6iokjiFPl8ONxe9A6nMDVXDiNbrSfLILs6vB07F7wLBrwPYzJw==} + engines: {node: '>=10.13.0'} + + wbuf@1.7.3: + resolution: {integrity: sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==} + + web-namespaces@2.0.1: + resolution: {integrity: sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ==} + + webpack-bundle-analyzer@4.10.2: + resolution: {integrity: sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw==} + engines: {node: '>= 10.13.0'} + hasBin: true + + webpack-dev-middleware@5.3.4: + resolution: {integrity: sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q==} + engines: {node: '>= 12.13.0'} + peerDependencies: + webpack: ^4.0.0 || ^5.0.0 + + webpack-dev-server@4.15.2: + resolution: {integrity: sha512-0XavAZbNJ5sDrCbkpWL8mia0o5WPOd2YGtxrEiZkBK9FjLppIUK2TgxK6qGD2P3hUXTJNNPVibrerKcx5WkR1g==} + engines: {node: '>= 12.13.0'} + hasBin: true + peerDependencies: + webpack: ^4.37.0 || ^5.0.0 + webpack-cli: '*' + peerDependenciesMeta: + webpack: + optional: true + webpack-cli: + optional: true + + webpack-merge@5.10.0: + resolution: {integrity: sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA==} + engines: {node: '>=10.0.0'} + + webpack-merge@6.0.1: + resolution: {integrity: sha512-hXXvrjtx2PLYx4qruKl+kyRSLc52V+cCvMxRjmKwoA+CBbbF5GfIBtR6kCvl0fYGqTUPKB+1ktVmTHqMOzgCBg==} + engines: {node: '>=18.0.0'} + + webpack-sources@3.2.3: + resolution: {integrity: sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==} + engines: {node: '>=10.13.0'} + + webpack@5.97.1: + resolution: {integrity: sha512-EksG6gFY3L1eFMROS/7Wzgrii5mBAFe4rIr3r2BTfo7bcc+DWwFZ4OJ/miOuHJO/A85HwyI4eQ0F6IKXesO7Fg==} + engines: {node: '>=10.13.0'} + hasBin: true + peerDependencies: + webpack-cli: '*' + peerDependenciesMeta: + webpack-cli: + optional: true + + webpackbar@6.0.1: + resolution: {integrity: sha512-TnErZpmuKdwWBdMoexjio3KKX6ZtoKHRVvLIU0A47R0VVBDtx3ZyOJDktgYixhoJokZTYTt1Z37OkO9pnGJa9Q==} + engines: {node: '>=14.21.3'} + peerDependencies: + webpack: 3 || 4 || 5 + + websocket-driver@0.7.4: + resolution: {integrity: sha512-b17KeDIQVjvb0ssuSDF2cYXSg2iztliJ4B9WdsuB6J952qCPKmnVq4DyW5motImXHDC1cBT/1UezrJVsKw5zjg==} + engines: {node: '>=0.8.0'} + + websocket-extensions@0.1.4: + resolution: {integrity: sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg==} + engines: {node: '>=0.8.0'} + + whatwg-encoding@3.1.1: + resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==} + engines: {node: '>=18'} + + whatwg-mimetype@4.0.0: + resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==} + engines: {node: '>=18'} + + which@1.3.1: + resolution: {integrity: sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==} + hasBin: true + + which@2.0.2: + resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==} + engines: {node: '>= 8'} + hasBin: true + + widest-line@4.0.1: + resolution: {integrity: sha512-o0cyEG0e8GPzT4iGHphIOh0cJOV8fivsXxddQasHPHfoZf1ZexrfeA21w2NaEN1RHE+fXlfISmOE8R9N3u3Qig==} + engines: {node: '>=12'} + + wildcard@2.0.1: + resolution: {integrity: sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ==} + + wrap-ansi@7.0.0: + resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==} + engines: {node: '>=10'} + + wrap-ansi@8.1.0: + resolution: {integrity: sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==} + engines: {node: '>=12'} + + wrappy@1.0.2: + resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==} + + write-file-atomic@3.0.3: + resolution: {integrity: sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q==} + + ws@7.5.10: + resolution: {integrity: sha512-+dbF1tHwZpXcbOJdVOkzLDxZP1ailvSxM6ZweXTegylPny803bFhA+vqBYw4s31NSAk4S2Qz+AKXK9a4wkdjcQ==} + engines: {node: '>=8.3.0'} + peerDependencies: + bufferutil: ^4.0.1 + utf-8-validate: ^5.0.2 + peerDependenciesMeta: + bufferutil: + optional: true + utf-8-validate: + optional: true + + ws@8.18.0: + resolution: {integrity: sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw==} + engines: {node: '>=10.0.0'} + peerDependencies: + bufferutil: ^4.0.1 + utf-8-validate: '>=5.0.2' + peerDependenciesMeta: + bufferutil: + optional: true + utf-8-validate: + optional: true + + xdg-basedir@5.1.0: + resolution: {integrity: sha512-GCPAHLvrIH13+c0SuacwvRYj2SxJXQ4kaVTT5xgL3kPrz56XxkF21IGhjSE1+W0aw7gpBWRGXLCPnPby6lSpmQ==} + engines: {node: '>=12'} + + xml-js@1.6.11: + resolution: {integrity: sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g==} + hasBin: true + + yallist@3.1.1: + resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==} + + yaml@1.10.2: + resolution: {integrity: sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==} + engines: {node: '>= 6'} + + yocto-queue@0.1.0: + resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==} + engines: {node: '>=10'} + + yocto-queue@1.1.1: + resolution: {integrity: sha512-b4JR1PFR10y1mKjhHY9LaGo6tmrgjit7hxVIeAmyMw3jegXR4dhYqLaQF5zMXZxY7tLpMyJeLjr1C4rLmkVe8g==} + engines: {node: '>=12.20'} + + zwitch@2.0.4: + resolution: {integrity: sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==} + +snapshots: + + '@algolia/autocomplete-core@1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-plugin-algolia-insights': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)(search-insights@2.17.3) + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0) + transitivePeerDependencies: + - '@algolia/client-search' + - algoliasearch + - search-insights + + '@algolia/autocomplete-core@1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-plugin-algolia-insights': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3) + '@algolia/autocomplete-shared': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) + transitivePeerDependencies: + - '@algolia/client-search' + - algoliasearch + - search-insights + + '@algolia/autocomplete-js@1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-core': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3) + '@algolia/autocomplete-preset-algolia': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) + '@algolia/autocomplete-shared': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) + '@algolia/client-search': 4.24.0 + algoliasearch: 4.24.0 + htm: 3.1.1 + preact: 10.25.1 + transitivePeerDependencies: + - search-insights + + '@algolia/autocomplete-plugin-algolia-insights@1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0) + search-insights: 2.17.3 + transitivePeerDependencies: + - '@algolia/client-search' + - algoliasearch + + '@algolia/autocomplete-plugin-algolia-insights@1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-shared': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) + search-insights: 2.17.3 + transitivePeerDependencies: + - '@algolia/client-search' + - algoliasearch + + '@algolia/autocomplete-preset-algolia@1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)': + dependencies: + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0) + '@algolia/client-search': 4.24.0 + algoliasearch: 5.17.0 + + '@algolia/autocomplete-preset-algolia@1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)': + dependencies: + '@algolia/autocomplete-shared': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) + '@algolia/client-search': 4.24.0 + algoliasearch: 4.24.0 + + '@algolia/autocomplete-shared@1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)': + dependencies: + '@algolia/client-search': 4.24.0 + algoliasearch: 5.17.0 + + '@algolia/autocomplete-shared@1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)': + dependencies: + '@algolia/client-search': 4.24.0 + algoliasearch: 4.24.0 + + '@algolia/autocomplete-theme-classic@1.17.8': {} + + '@algolia/cache-browser-local-storage@4.24.0': + dependencies: + '@algolia/cache-common': 4.24.0 + + '@algolia/cache-common@4.24.0': {} + + '@algolia/cache-in-memory@4.24.0': + dependencies: + '@algolia/cache-common': 4.24.0 + + '@algolia/client-abtesting@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/client-account@4.24.0': + dependencies: + '@algolia/client-common': 4.24.0 + '@algolia/client-search': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/client-analytics@4.24.0': + dependencies: + '@algolia/client-common': 4.24.0 + '@algolia/client-search': 4.24.0 + '@algolia/requester-common': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/client-analytics@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/client-common@4.24.0': + dependencies: + '@algolia/requester-common': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/client-common@5.17.0': {} + + '@algolia/client-insights@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/client-personalization@4.24.0': + dependencies: + '@algolia/client-common': 4.24.0 + '@algolia/requester-common': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/client-personalization@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/client-query-suggestions@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/client-search@4.24.0': + dependencies: + '@algolia/client-common': 4.24.0 + '@algolia/requester-common': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/client-search@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/events@4.0.1': {} + + '@algolia/ingestion@1.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/logger-common@4.24.0': {} + + '@algolia/logger-console@4.24.0': + dependencies: + '@algolia/logger-common': 4.24.0 + + '@algolia/monitoring@1.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/recommend@4.24.0': + dependencies: + '@algolia/cache-browser-local-storage': 4.24.0 + '@algolia/cache-common': 4.24.0 + '@algolia/cache-in-memory': 4.24.0 + '@algolia/client-common': 4.24.0 + '@algolia/client-search': 4.24.0 + '@algolia/logger-common': 4.24.0 + '@algolia/logger-console': 4.24.0 + '@algolia/requester-browser-xhr': 4.24.0 + '@algolia/requester-common': 4.24.0 + '@algolia/requester-node-http': 4.24.0 + '@algolia/transporter': 4.24.0 + + '@algolia/recommend@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + '@algolia/requester-browser-xhr@4.24.0': + dependencies: + '@algolia/requester-common': 4.24.0 + + '@algolia/requester-browser-xhr@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + + '@algolia/requester-common@4.24.0': {} + + '@algolia/requester-fetch@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + + '@algolia/requester-node-http@4.24.0': + dependencies: + '@algolia/requester-common': 4.24.0 + + '@algolia/requester-node-http@5.17.0': + dependencies: + '@algolia/client-common': 5.17.0 + + '@algolia/transporter@4.24.0': + dependencies: + '@algolia/cache-common': 4.24.0 + '@algolia/logger-common': 4.24.0 + '@algolia/requester-common': 4.24.0 + + '@ampproject/remapping@2.3.0': + dependencies: + '@jridgewell/gen-mapping': 0.3.5 + '@jridgewell/trace-mapping': 0.3.25 + + '@babel/code-frame@7.26.2': + dependencies: + '@babel/helper-validator-identifier': 7.25.9 + js-tokens: 4.0.0 + picocolors: 1.1.1 + + '@babel/compat-data@7.26.3': {} + + '@babel/core@7.26.0': + dependencies: + '@ampproject/remapping': 2.3.0 + '@babel/code-frame': 7.26.2 + '@babel/generator': 7.26.3 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-module-transforms': 7.26.0(@babel/core@7.26.0) + '@babel/helpers': 7.26.0 + '@babel/parser': 7.26.3 + '@babel/template': 7.25.9 + '@babel/traverse': 7.26.4 + '@babel/types': 7.26.3 + convert-source-map: 2.0.0 + debug: 4.4.0 + gensync: 1.0.0-beta.2 + json5: 2.2.3 + semver: 6.3.1 + transitivePeerDependencies: + - supports-color + + '@babel/generator@7.26.3': + dependencies: + '@babel/parser': 7.26.3 + '@babel/types': 7.26.3 + '@jridgewell/gen-mapping': 0.3.5 + '@jridgewell/trace-mapping': 0.3.25 + jsesc: 3.1.0 + + '@babel/helper-annotate-as-pure@7.25.9': + dependencies: + '@babel/types': 7.26.3 + + '@babel/helper-compilation-targets@7.25.9': + dependencies: + '@babel/compat-data': 7.26.3 + '@babel/helper-validator-option': 7.25.9 + browserslist: 4.24.2 + lru-cache: 5.1.1 + semver: 6.3.1 + + '@babel/helper-create-class-features-plugin@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-member-expression-to-functions': 7.25.9 + '@babel/helper-optimise-call-expression': 7.25.9 + '@babel/helper-replace-supers': 7.25.9(@babel/core@7.26.0) + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + '@babel/traverse': 7.26.4 + semver: 6.3.1 + transitivePeerDependencies: + - supports-color + + '@babel/helper-create-regexp-features-plugin@7.26.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + regexpu-core: 6.2.0 + semver: 6.3.1 + + '@babel/helper-define-polyfill-provider@0.6.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + debug: 4.4.0 + lodash.debounce: 4.0.8 + resolve: 1.22.8 + transitivePeerDependencies: + - supports-color + + '@babel/helper-member-expression-to-functions@7.25.9': + dependencies: + '@babel/traverse': 7.26.4 + '@babel/types': 7.26.3 + transitivePeerDependencies: + - supports-color + + '@babel/helper-module-imports@7.25.9': + dependencies: + '@babel/traverse': 7.26.4 + '@babel/types': 7.26.3 + transitivePeerDependencies: + - supports-color + + '@babel/helper-module-transforms@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-imports': 7.25.9 + '@babel/helper-validator-identifier': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/helper-optimise-call-expression@7.25.9': + dependencies: + '@babel/types': 7.26.3 + + '@babel/helper-plugin-utils@7.25.9': {} + + '@babel/helper-remap-async-to-generator@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-wrap-function': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/helper-replace-supers@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-member-expression-to-functions': 7.25.9 + '@babel/helper-optimise-call-expression': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/helper-skip-transparent-expression-wrappers@7.25.9': + dependencies: + '@babel/traverse': 7.26.4 + '@babel/types': 7.26.3 + transitivePeerDependencies: + - supports-color + + '@babel/helper-string-parser@7.25.9': {} + + '@babel/helper-validator-identifier@7.25.9': {} + + '@babel/helper-validator-option@7.25.9': {} + + '@babel/helper-wrap-function@7.25.9': + dependencies: + '@babel/template': 7.25.9 + '@babel/traverse': 7.26.4 + '@babel/types': 7.26.3 + transitivePeerDependencies: + - supports-color + + '@babel/helpers@7.26.0': + dependencies: + '@babel/template': 7.25.9 + '@babel/types': 7.26.3 + + '@babel/parser@7.26.3': + dependencies: + '@babel/types': 7.26.3 + + '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + '@babel/plugin-transform-optional-chaining': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@babel/plugin-syntax-dynamic-import@7.8.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-syntax-import-assertions@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-syntax-import-attributes@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-syntax-jsx@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-syntax-typescript@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-syntax-unicode-sets-regex@7.18.6(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-arrow-functions@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-async-generator-functions@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-remap-async-to-generator': 7.25.9(@babel/core@7.26.0) + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-async-to-generator@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-imports': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-remap-async-to-generator': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-block-scoped-functions@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-block-scoping@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-class-properties@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-class-features-plugin': 7.25.9(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-class-static-block@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-class-features-plugin': 7.25.9(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-classes@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-replace-supers': 7.25.9(@babel/core@7.26.0) + '@babel/traverse': 7.26.4 + globals: 11.12.0 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-computed-properties@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/template': 7.25.9 + + '@babel/plugin-transform-destructuring@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-dotall-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-duplicate-keys@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-dynamic-import@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-exponentiation-operator@7.26.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-export-namespace-from@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-for-of@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-function-name@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-json-strings@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-literals@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-logical-assignment-operators@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-member-expression-literals@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-modules-amd@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-transforms': 7.26.0(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-modules-commonjs@7.26.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-transforms': 7.26.0(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-modules-systemjs@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-transforms': 7.26.0(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-validator-identifier': 7.25.9 + '@babel/traverse': 7.26.4 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-modules-umd@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-transforms': 7.26.0(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-named-capturing-groups-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-new-target@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-nullish-coalescing-operator@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-numeric-separator@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-object-rest-spread@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/plugin-transform-parameters': 7.25.9(@babel/core@7.26.0) + + '@babel/plugin-transform-object-super@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-replace-supers': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-optional-catch-binding@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-optional-chaining@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-parameters@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-private-methods@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-class-features-plugin': 7.25.9(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-private-property-in-object@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-create-class-features-plugin': 7.25.9(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-property-literals@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-react-constant-elements@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-react-display-name@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-react-jsx-development@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/plugin-transform-react-jsx': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-react-jsx@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-module-imports': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/plugin-syntax-jsx': 7.25.9(@babel/core@7.26.0) + '@babel/types': 7.26.3 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-react-pure-annotations@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-regenerator@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + regenerator-transform: 0.15.2 + + '@babel/plugin-transform-regexp-modifiers@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-reserved-words@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-runtime@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-module-imports': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + babel-plugin-polyfill-corejs2: 0.4.12(@babel/core@7.26.0) + babel-plugin-polyfill-corejs3: 0.10.6(@babel/core@7.26.0) + babel-plugin-polyfill-regenerator: 0.6.3(@babel/core@7.26.0) + semver: 6.3.1 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-shorthand-properties@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-spread@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-sticky-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-template-literals@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-typeof-symbol@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-typescript@7.26.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-annotate-as-pure': 7.25.9 + '@babel/helper-create-class-features-plugin': 7.25.9(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-skip-transparent-expression-wrappers': 7.25.9 + '@babel/plugin-syntax-typescript': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/plugin-transform-unicode-escapes@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-unicode-property-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-unicode-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/plugin-transform-unicode-sets-regex@7.25.9(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-create-regexp-features-plugin': 7.26.3(@babel/core@7.26.0) + '@babel/helper-plugin-utils': 7.25.9 + + '@babel/preset-env@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/compat-data': 7.26.3 + '@babel/core': 7.26.0 + '@babel/helper-compilation-targets': 7.25.9 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-validator-option': 7.25.9 + '@babel/plugin-bugfix-firefox-class-in-computed-class-key': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-bugfix-safari-class-field-initializer-scope': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-proposal-private-property-in-object': 7.21.0-placeholder-for-preset-env.2(@babel/core@7.26.0) + '@babel/plugin-syntax-import-assertions': 7.26.0(@babel/core@7.26.0) + '@babel/plugin-syntax-import-attributes': 7.26.0(@babel/core@7.26.0) + '@babel/plugin-syntax-unicode-sets-regex': 7.18.6(@babel/core@7.26.0) + '@babel/plugin-transform-arrow-functions': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-async-generator-functions': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-async-to-generator': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-block-scoped-functions': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-block-scoping': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-class-properties': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-class-static-block': 7.26.0(@babel/core@7.26.0) + '@babel/plugin-transform-classes': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-computed-properties': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-destructuring': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-dotall-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-duplicate-keys': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-duplicate-named-capturing-groups-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-dynamic-import': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-exponentiation-operator': 7.26.3(@babel/core@7.26.0) + '@babel/plugin-transform-export-namespace-from': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-for-of': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-function-name': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-json-strings': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-literals': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-logical-assignment-operators': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-member-expression-literals': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-modules-amd': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-modules-commonjs': 7.26.3(@babel/core@7.26.0) + '@babel/plugin-transform-modules-systemjs': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-modules-umd': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-named-capturing-groups-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-new-target': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-nullish-coalescing-operator': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-numeric-separator': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-object-rest-spread': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-object-super': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-optional-catch-binding': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-optional-chaining': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-parameters': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-private-methods': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-private-property-in-object': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-property-literals': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-regenerator': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-regexp-modifiers': 7.26.0(@babel/core@7.26.0) + '@babel/plugin-transform-reserved-words': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-shorthand-properties': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-spread': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-sticky-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-template-literals': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-typeof-symbol': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-unicode-escapes': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-unicode-property-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-unicode-regex': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-unicode-sets-regex': 7.25.9(@babel/core@7.26.0) + '@babel/preset-modules': 0.1.6-no-external-plugins(@babel/core@7.26.0) + babel-plugin-polyfill-corejs2: 0.4.12(@babel/core@7.26.0) + babel-plugin-polyfill-corejs3: 0.10.6(@babel/core@7.26.0) + babel-plugin-polyfill-regenerator: 0.6.3(@babel/core@7.26.0) + core-js-compat: 3.39.0 + semver: 6.3.1 + transitivePeerDependencies: + - supports-color + + '@babel/preset-modules@0.1.6-no-external-plugins(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/types': 7.26.3 + esutils: 2.0.3 + + '@babel/preset-react@7.26.3(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-validator-option': 7.25.9 + '@babel/plugin-transform-react-display-name': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-react-jsx': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-react-jsx-development': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-react-pure-annotations': 7.25.9(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/preset-typescript@7.26.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-plugin-utils': 7.25.9 + '@babel/helper-validator-option': 7.25.9 + '@babel/plugin-syntax-jsx': 7.25.9(@babel/core@7.26.0) + '@babel/plugin-transform-modules-commonjs': 7.26.3(@babel/core@7.26.0) + '@babel/plugin-transform-typescript': 7.26.3(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + '@babel/runtime-corejs3@7.26.0': + dependencies: + core-js-pure: 3.39.0 + regenerator-runtime: 0.14.1 + + '@babel/runtime@7.26.0': + dependencies: + regenerator-runtime: 0.14.1 + + '@babel/template@7.25.9': + dependencies: + '@babel/code-frame': 7.26.2 + '@babel/parser': 7.26.3 + '@babel/types': 7.26.3 + + '@babel/traverse@7.26.4': + dependencies: + '@babel/code-frame': 7.26.2 + '@babel/generator': 7.26.3 + '@babel/parser': 7.26.3 + '@babel/template': 7.25.9 + '@babel/types': 7.26.3 + debug: 4.4.0 + globals: 11.12.0 + transitivePeerDependencies: + - supports-color + + '@babel/types@7.26.3': + dependencies: + '@babel/helper-string-parser': 7.25.9 + '@babel/helper-validator-identifier': 7.25.9 + + '@cmfcmf/docusaurus-search-local@1.2.0(@docusaurus/core@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-js': 1.17.8(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.3) + '@algolia/autocomplete-theme-classic': 1.17.8 + '@algolia/client-search': 4.24.0 + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + algoliasearch: 4.24.0 + cheerio: 1.0.0 + clsx: 1.2.1 + lunr-languages: 1.14.0 + mark.js: 8.11.1 + tslib: 2.8.1 + transitivePeerDependencies: + - search-insights + + '@colors/colors@1.5.0': + optional: true + + '@csstools/cascade-layer-name-parser@2.0.4(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + + '@csstools/color-helpers@5.0.1': {} + + '@csstools/css-calc@2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + + '@csstools/css-color-parser@3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3)': + dependencies: + '@csstools/color-helpers': 5.0.1 + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + + '@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3)': + dependencies: + '@csstools/css-tokenizer': 3.0.3 + + '@csstools/css-tokenizer@3.0.3': {} + + '@csstools/media-query-list-parser@4.0.2(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + + '@csstools/postcss-cascade-layers@5.0.1(postcss@8.4.49)': + dependencies: + '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.0.0) + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + '@csstools/postcss-color-function@4.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-color-mix-function@3.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-content-alt-text@2.0.4(postcss@8.4.49)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-exponential-functions@2.0.5(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-font-format-keywords@4.0.0(postcss@8.4.49)': + dependencies: + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-gamut-mapping@2.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-gradients-interpolation-method@5.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-hwb-function@4.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-ic-unit@4.0.0(postcss@8.4.49)': + dependencies: + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-initial@2.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@csstools/postcss-is-pseudo-class@5.0.1(postcss@8.4.49)': + dependencies: + '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.0.0) + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + '@csstools/postcss-light-dark-function@2.0.7(postcss@8.4.49)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-logical-float-and-clear@3.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@csstools/postcss-logical-overflow@2.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@csstools/postcss-logical-overscroll-behavior@2.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@csstools/postcss-logical-resize@3.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-logical-viewport-units@3.0.3(postcss@8.4.49)': + dependencies: + '@csstools/css-tokenizer': 3.0.3 + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-media-minmax@2.0.5(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/media-query-list-parser': 4.0.2(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + postcss: 8.4.49 + + '@csstools/postcss-media-queries-aspect-ratio-number-values@3.0.4(postcss@8.4.49)': + dependencies: + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/media-query-list-parser': 4.0.2(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + postcss: 8.4.49 + + '@csstools/postcss-nested-calc@4.0.0(postcss@8.4.49)': + dependencies: + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-normalize-display-values@4.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-oklab-function@4.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-progressive-custom-properties@4.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-random-function@1.0.1(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-relative-color-syntax@3.0.6(postcss@8.4.49)': + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + '@csstools/postcss-scope-pseudo-class@4.0.1(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + '@csstools/postcss-sign-functions@1.1.0(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-stepped-value-functions@4.0.5(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-text-decoration-shorthand@4.0.1(postcss@8.4.49)': + dependencies: + '@csstools/color-helpers': 5.0.1 + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + '@csstools/postcss-trigonometric-functions@4.0.5(postcss@8.4.49)': + dependencies: + '@csstools/css-calc': 2.1.0(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + + '@csstools/postcss-unset-value@4.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@csstools/selector-resolve-nested@3.0.0(postcss-selector-parser@7.0.0)': + dependencies: + postcss-selector-parser: 7.0.0 + + '@csstools/selector-specificity@5.0.0(postcss-selector-parser@7.0.0)': + dependencies: + postcss-selector-parser: 7.0.0 + + '@csstools/utilities@2.0.0(postcss@8.4.49)': + dependencies: + postcss: 8.4.49 + + '@discoveryjs/json-ext@0.5.7': {} + + '@docsearch/css@3.8.0': {} + + '@docsearch/react@3.8.0(@algolia/client-search@4.24.0)(@types/react@19.0.1)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)': + dependencies: + '@algolia/autocomplete-core': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0)(search-insights@2.17.3) + '@algolia/autocomplete-preset-algolia': 1.17.7(@algolia/client-search@4.24.0)(algoliasearch@5.17.0) + '@docsearch/css': 3.8.0 + algoliasearch: 5.17.0 + optionalDependencies: + '@types/react': 19.0.1 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + search-insights: 2.17.3 + transitivePeerDependencies: + - '@algolia/client-search' + + '@docusaurus/babel@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@babel/core': 7.26.0 + '@babel/generator': 7.26.3 + '@babel/plugin-syntax-dynamic-import': 7.8.3(@babel/core@7.26.0) + '@babel/plugin-transform-runtime': 7.25.9(@babel/core@7.26.0) + '@babel/preset-env': 7.26.0(@babel/core@7.26.0) + '@babel/preset-react': 7.26.3(@babel/core@7.26.0) + '@babel/preset-typescript': 7.26.0(@babel/core@7.26.0) + '@babel/runtime': 7.26.0 + '@babel/runtime-corejs3': 7.26.0 + '@babel/traverse': 7.26.4 + '@docusaurus/logger': 3.6.3 + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + babel-plugin-dynamic-import-node: 2.3.3 + fs-extra: 11.2.0 + tslib: 2.8.1 + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - react + - react-dom + - supports-color + - typescript + - uglify-js + - webpack-cli + + '@docusaurus/bundler@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@babel/core': 7.26.0 + '@docusaurus/babel': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/cssnano-preset': 3.6.3 + '@docusaurus/logger': 3.6.3 + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + babel-loader: 9.2.1(@babel/core@7.26.0)(webpack@5.97.1(@swc/core@1.10.1)) + clean-css: 5.3.3 + copy-webpack-plugin: 11.0.0(webpack@5.97.1(@swc/core@1.10.1)) + css-loader: 6.11.0(@rspack/core@1.1.6)(webpack@5.97.1(@swc/core@1.10.1)) + css-minimizer-webpack-plugin: 5.0.1(clean-css@5.3.3)(webpack@5.97.1(@swc/core@1.10.1)) + cssnano: 6.1.2(postcss@8.4.49) + file-loader: 6.2.0(webpack@5.97.1(@swc/core@1.10.1)) + html-minifier-terser: 7.2.0 + mini-css-extract-plugin: 2.9.2(webpack@5.97.1(@swc/core@1.10.1)) + null-loader: 4.0.1(webpack@5.97.1(@swc/core@1.10.1)) + postcss: 8.4.49 + postcss-loader: 7.3.4(postcss@8.4.49)(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)) + postcss-preset-env: 10.1.1(postcss@8.4.49) + react-dev-utils: 12.0.1(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)) + terser-webpack-plugin: 5.3.10(@swc/core@1.10.1)(webpack@5.97.1(@swc/core@1.10.1)) + tslib: 2.8.1 + url-loader: 4.1.1(file-loader@6.2.0(webpack@5.97.1(@swc/core@1.10.1)))(webpack@5.97.1(@swc/core@1.10.1)) + webpack: 5.97.1(@swc/core@1.10.1) + webpackbar: 6.0.1(webpack@5.97.1(@swc/core@1.10.1)) + optionalDependencies: + '@docusaurus/faster': 3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)) + transitivePeerDependencies: + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - csso + - esbuild + - eslint + - lightningcss + - react + - react-dom + - supports-color + - typescript + - uglify-js + - vue-template-compiler + - webpack-cli + + '@docusaurus/core@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/babel': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/bundler': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@mdx-js/react': 3.1.0(@types/react@19.0.1)(react@18.3.1) + boxen: 6.2.1 + chalk: 4.1.2 + chokidar: 3.6.0 + cli-table3: 0.6.5 + combine-promises: 1.2.0 + commander: 5.1.0 + core-js: 3.39.0 + del: 6.1.1 + detect-port: 1.6.1 + escape-html: 1.0.3 + eta: 2.2.0 + eval: 0.1.8 + fs-extra: 11.2.0 + html-tags: 3.3.1 + html-webpack-plugin: 5.6.3(@rspack/core@1.1.6)(webpack@5.97.1(@swc/core@1.10.1)) + leven: 3.1.0 + lodash: 4.17.21 + p-map: 4.0.0 + prompts: 2.4.2 + react: 18.3.1 + react-dev-utils: 12.0.1(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)) + react-dom: 18.3.1(react@18.3.1) + react-helmet-async: 1.3.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + react-loadable: '@docusaurus/react-loadable@6.0.0(react@18.3.1)' + react-loadable-ssr-addon-v5-slorber: 1.0.1(@docusaurus/react-loadable@6.0.0(react@18.3.1))(webpack@5.97.1(@swc/core@1.10.1)) + react-router: 5.3.4(react@18.3.1) + react-router-config: 5.1.1(react-router@5.3.4(react@18.3.1))(react@18.3.1) + react-router-dom: 5.3.4(react@18.3.1) + rtl-detect: 1.1.2 + semver: 7.6.3 + serve-handler: 6.1.6 + shelljs: 0.8.5 + tslib: 2.8.1 + update-notifier: 6.0.2 + webpack: 5.97.1(@swc/core@1.10.1) + webpack-bundle-analyzer: 4.10.2 + webpack-dev-server: 4.15.2(webpack@5.97.1(@swc/core@1.10.1)) + webpack-merge: 6.0.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/cssnano-preset@3.6.3': + dependencies: + cssnano-preset-advanced: 6.1.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-sort-media-queries: 5.2.0(postcss@8.4.49) + tslib: 2.8.1 + + '@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))': + dependencies: + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@rspack/core': 1.1.6 + '@swc/core': 1.10.1 + '@swc/html': 1.10.1 + browserslist: 4.24.2 + lightningcss: 1.28.2 + swc-loader: 0.2.6(@swc/core@1.10.1)(webpack@5.97.1(@swc/core@1.10.1)) + tslib: 2.8.1 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@swc/helpers' + - esbuild + - uglify-js + - webpack-cli + + '@docusaurus/logger@3.6.3': + dependencies: + chalk: 4.1.2 + tslib: 2.8.1 + + '@docusaurus/lqip-loader@3.6.3(webpack@5.97.1(@swc/core@1.10.1))': + dependencies: + '@docusaurus/logger': 3.6.3 + file-loader: 6.2.0(webpack@5.97.1(@swc/core@1.10.1)) + lodash: 4.17.21 + sharp: 0.32.6 + tslib: 2.8.1 + transitivePeerDependencies: + - webpack + + '@docusaurus/mdx-loader@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/logger': 3.6.3 + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@mdx-js/mdx': 3.1.0(acorn@8.14.0) + '@slorber/remark-comment': 1.0.0 + escape-html: 1.0.3 + estree-util-value-to-estree: 3.2.1 + file-loader: 6.2.0(webpack@5.97.1(@swc/core@1.10.1)) + fs-extra: 11.2.0 + image-size: 1.1.1 + mdast-util-mdx: 3.0.0 + mdast-util-to-string: 4.0.0 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + rehype-raw: 7.0.0 + remark-directive: 3.0.0 + remark-emoji: 4.0.1 + remark-frontmatter: 5.0.0 + remark-gfm: 4.0.0 + stringify-object: 3.3.0 + tslib: 2.8.1 + unified: 11.0.5 + unist-util-visit: 5.0.0 + url-loader: 4.1.1(file-loader@6.2.0(webpack@5.97.1(@swc/core@1.10.1)))(webpack@5.97.1(@swc/core@1.10.1)) + vfile: 6.0.3 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - supports-color + - typescript + - uglify-js + - webpack-cli + + '@docusaurus/module-type-aliases@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + dependencies: + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@types/history': 4.7.11 + '@types/react': 19.0.1 + '@types/react-router-config': 5.0.11 + '@types/react-router-dom': 5.3.3 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-helmet-async: 2.0.5(react@18.3.1) + react-loadable: '@docusaurus/react-loadable@6.0.0(react@18.3.1)' + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - supports-color + - uglify-js + - webpack-cli + + '@docusaurus/plugin-content-blog@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-docs': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-common': 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + cheerio: 1.0.0-rc.12 + feed: 4.2.2 + fs-extra: 11.2.0 + lodash: 4.17.21 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + reading-time: 1.5.0 + srcset: 4.0.0 + tslib: 2.8.1 + unist-util-visit: 5.0.0 + utility-types: 3.11.0 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/module-type-aliases': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/theme-common': 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@types/react-router-config': 5.0.11 + combine-promises: 1.2.0 + fs-extra: 11.2.0 + js-yaml: 4.1.0 + lodash: 4.17.21 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + utility-types: 3.11.0 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-content-pages@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + fs-extra: 11.2.0 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-debug@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + fs-extra: 11.2.0 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-json-view-lite: 1.5.0(react@18.3.1) + tslib: 2.8.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-google-analytics@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-google-gtag@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@types/gtag.js': 0.0.12 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-google-tag-manager@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-ideal-image@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(prop-types@15.8.1)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/lqip-loader': 3.6.3(webpack@5.97.1(@swc/core@1.10.1)) + '@docusaurus/responsive-loader': 1.7.0(sharp@0.32.6) + '@docusaurus/theme-translations': 3.6.3 + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@slorber/react-ideal-image': 0.0.12(prop-types@15.8.1)(react-waypoint@10.3.0(react@18.3.1))(react@18.3.1) + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-waypoint: 10.3.0(react@18.3.1) + sharp: 0.32.6 + tslib: 2.8.1 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - prop-types + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/plugin-sitemap@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + fs-extra: 11.2.0 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + sitemap: 7.1.2 + tslib: 2.8.1 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/preset-classic@3.6.3(@algolia/client-search@4.24.0)(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-blog': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-docs': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-pages': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-debug': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-google-analytics': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-google-gtag': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-google-tag-manager': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-sitemap': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-classic': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-common': 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-search-algolia': 3.6.3(@algolia/client-search@4.24.0)(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)(typescript@5.7.2) + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + transitivePeerDependencies: + - '@algolia/client-search' + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - '@types/react' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - search-insights + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/react-loadable@6.0.0(react@18.3.1)': + dependencies: + '@types/react': 19.0.1 + react: 18.3.1 + + '@docusaurus/responsive-loader@1.7.0(sharp@0.32.6)': + dependencies: + loader-utils: 2.0.4 + optionalDependencies: + sharp: 0.32.6 + + '@docusaurus/theme-classic@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/module-type-aliases': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/plugin-content-blog': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-docs': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/plugin-content-pages': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-common': 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-translations': 3.6.3 + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@mdx-js/react': 3.1.0(@types/react@19.0.1)(react@18.3.1) + clsx: 2.1.1 + copy-text-to-clipboard: 3.2.0 + infima: 0.2.0-alpha.45 + lodash: 4.17.21 + nprogress: 0.2.0 + postcss: 8.4.49 + prism-react-renderer: 2.4.0(react@18.3.1) + prismjs: 1.29.0 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-router-dom: 5.3.4(react@18.3.1) + rtlcss: 4.3.0 + tslib: 2.8.1 + utility-types: 3.11.0 + transitivePeerDependencies: + - '@docusaurus/faster' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - '@types/react' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/theme-common@3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/mdx-loader': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/module-type-aliases': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/plugin-content-docs': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@types/history': 4.7.11 + '@types/react': 19.0.1 + '@types/react-router-config': 5.0.11 + clsx: 2.1.1 + parse-numeric-range: 1.3.0 + prism-react-renderer: 2.4.0(react@18.3.1) + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + utility-types: 3.11.0 + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - supports-color + - typescript + - uglify-js + - webpack-cli + + '@docusaurus/theme-search-algolia@3.6.3(@algolia/client-search@4.24.0)(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)(typescript@5.7.2)': + dependencies: + '@docsearch/react': 3.8.0(@algolia/client-search@4.24.0)(@types/react@19.0.1)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3) + '@docusaurus/core': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/logger': 3.6.3 + '@docusaurus/plugin-content-docs': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-common': 3.6.3(@docusaurus/plugin-content-docs@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1))(@rspack/core@1.1.6)(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2))(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/theme-translations': 3.6.3 + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-validation': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + algoliasearch: 4.24.0 + algoliasearch-helper: 3.22.6(algoliasearch@4.24.0) + clsx: 2.1.1 + eta: 2.2.0 + fs-extra: 11.2.0 + lodash: 4.17.21 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + tslib: 2.8.1 + utility-types: 3.11.0 + transitivePeerDependencies: + - '@algolia/client-search' + - '@docusaurus/faster' + - '@mdx-js/react' + - '@parcel/css' + - '@rspack/core' + - '@swc/core' + - '@swc/css' + - '@types/react' + - acorn + - bufferutil + - csso + - debug + - esbuild + - eslint + - lightningcss + - search-insights + - supports-color + - typescript + - uglify-js + - utf-8-validate + - vue-template-compiler + - webpack-cli + + '@docusaurus/theme-translations@3.6.3': + dependencies: + fs-extra: 11.2.0 + tslib: 2.8.1 + + '@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + dependencies: + '@mdx-js/mdx': 3.1.0(acorn@8.14.0) + '@types/history': 4.7.11 + '@types/react': 19.0.1 + commander: 5.1.0 + joi: 17.13.3 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-helmet-async: 1.3.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + utility-types: 3.11.0 + webpack: 5.97.1(@swc/core@1.10.1) + webpack-merge: 5.10.0 + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - supports-color + - uglify-js + - webpack-cli + + '@docusaurus/utils-common@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + dependencies: + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + tslib: 2.8.1 + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - react + - react-dom + - supports-color + - uglify-js + - webpack-cli + + '@docusaurus/utils-validation@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/logger': 3.6.3 + '@docusaurus/utils': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + fs-extra: 11.2.0 + joi: 17.13.3 + js-yaml: 4.1.0 + lodash: 4.17.21 + tslib: 2.8.1 + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - react + - react-dom + - supports-color + - typescript + - uglify-js + - webpack-cli + + '@docusaurus/utils@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)': + dependencies: + '@docusaurus/logger': 3.6.3 + '@docusaurus/types': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@docusaurus/utils-common': 3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@svgr/webpack': 8.1.0(typescript@5.7.2) + escape-string-regexp: 4.0.0 + file-loader: 6.2.0(webpack@5.97.1(@swc/core@1.10.1)) + fs-extra: 11.2.0 + github-slugger: 1.5.0 + globby: 11.1.0 + gray-matter: 4.0.3 + jiti: 1.21.6 + js-yaml: 4.1.0 + lodash: 4.17.21 + micromatch: 4.0.8 + prompts: 2.4.2 + resolve-pathname: 3.0.0 + shelljs: 0.8.5 + tslib: 2.8.1 + url-loader: 4.1.1(file-loader@6.2.0(webpack@5.97.1(@swc/core@1.10.1)))(webpack@5.97.1(@swc/core@1.10.1)) + utility-types: 3.11.0 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - '@swc/core' + - acorn + - esbuild + - react + - react-dom + - supports-color + - typescript + - uglify-js + - webpack-cli + + '@hapi/hoek@9.3.0': {} + + '@hapi/topo@5.1.0': + dependencies: + '@hapi/hoek': 9.3.0 + + '@jest/schemas@29.6.3': + dependencies: + '@sinclair/typebox': 0.27.8 + + '@jest/types@29.6.3': + dependencies: + '@jest/schemas': 29.6.3 + '@types/istanbul-lib-coverage': 2.0.6 + '@types/istanbul-reports': 3.0.4 + '@types/node': 22.10.1 + '@types/yargs': 17.0.33 + chalk: 4.1.2 + + '@jridgewell/gen-mapping@0.3.5': + dependencies: + '@jridgewell/set-array': 1.2.1 + '@jridgewell/sourcemap-codec': 1.5.0 + '@jridgewell/trace-mapping': 0.3.25 + + '@jridgewell/resolve-uri@3.1.2': {} + + '@jridgewell/set-array@1.2.1': {} + + '@jridgewell/source-map@0.3.6': + dependencies: + '@jridgewell/gen-mapping': 0.3.5 + '@jridgewell/trace-mapping': 0.3.25 + + '@jridgewell/sourcemap-codec@1.5.0': {} + + '@jridgewell/trace-mapping@0.3.25': + dependencies: + '@jridgewell/resolve-uri': 3.1.2 + '@jridgewell/sourcemap-codec': 1.5.0 + + '@leichtgewicht/ip-codec@2.0.5': {} + + '@mdx-js/mdx@3.1.0(acorn@8.14.0)': + dependencies: + '@types/estree': 1.0.6 + '@types/estree-jsx': 1.0.5 + '@types/hast': 3.0.4 + '@types/mdx': 2.0.13 + collapse-white-space: 2.1.0 + devlop: 1.1.0 + estree-util-is-identifier-name: 3.0.0 + estree-util-scope: 1.0.0 + estree-walker: 3.0.3 + hast-util-to-jsx-runtime: 2.3.2 + markdown-extensions: 2.0.0 + recma-build-jsx: 1.0.0 + recma-jsx: 1.0.0(acorn@8.14.0) + recma-stringify: 1.0.0 + rehype-recma: 1.0.0 + remark-mdx: 3.1.0 + remark-parse: 11.0.0 + remark-rehype: 11.1.1 + source-map: 0.7.4 + unified: 11.0.5 + unist-util-position-from-estree: 2.0.0 + unist-util-stringify-position: 4.0.0 + unist-util-visit: 5.0.0 + vfile: 6.0.3 + transitivePeerDependencies: + - acorn + - supports-color + + '@mdx-js/react@3.1.0(@types/react@19.0.1)(react@18.3.1)': + dependencies: + '@types/mdx': 2.0.13 + '@types/react': 19.0.1 + react: 18.3.1 + + '@module-federation/runtime-tools@0.5.1': + dependencies: + '@module-federation/runtime': 0.5.1 + '@module-federation/webpack-bundler-runtime': 0.5.1 + + '@module-federation/runtime@0.5.1': + dependencies: + '@module-federation/sdk': 0.5.1 + + '@module-federation/sdk@0.5.1': {} + + '@module-federation/webpack-bundler-runtime@0.5.1': + dependencies: + '@module-federation/runtime': 0.5.1 + '@module-federation/sdk': 0.5.1 + + '@nodelib/fs.scandir@2.1.5': + dependencies: + '@nodelib/fs.stat': 2.0.5 + run-parallel: 1.2.0 + + '@nodelib/fs.stat@2.0.5': {} + + '@nodelib/fs.walk@1.2.8': + dependencies: + '@nodelib/fs.scandir': 2.1.5 + fastq: 1.17.1 + + '@pnpm/config.env-replace@1.1.0': {} + + '@pnpm/network.ca-file@1.0.2': + dependencies: + graceful-fs: 4.2.10 + + '@pnpm/npm-conf@2.3.1': + dependencies: + '@pnpm/config.env-replace': 1.1.0 + '@pnpm/network.ca-file': 1.0.2 + config-chain: 1.1.13 + + '@polka/url@1.0.0-next.28': {} + + '@rspack/binding-darwin-arm64@1.1.6': + optional: true + + '@rspack/binding-darwin-x64@1.1.6': + optional: true + + '@rspack/binding-linux-arm64-gnu@1.1.6': + optional: true + + '@rspack/binding-linux-arm64-musl@1.1.6': + optional: true + + '@rspack/binding-linux-x64-gnu@1.1.6': + optional: true + + '@rspack/binding-linux-x64-musl@1.1.6': + optional: true + + '@rspack/binding-win32-arm64-msvc@1.1.6': + optional: true + + '@rspack/binding-win32-ia32-msvc@1.1.6': + optional: true + + '@rspack/binding-win32-x64-msvc@1.1.6': + optional: true + + '@rspack/binding@1.1.6': + optionalDependencies: + '@rspack/binding-darwin-arm64': 1.1.6 + '@rspack/binding-darwin-x64': 1.1.6 + '@rspack/binding-linux-arm64-gnu': 1.1.6 + '@rspack/binding-linux-arm64-musl': 1.1.6 + '@rspack/binding-linux-x64-gnu': 1.1.6 + '@rspack/binding-linux-x64-musl': 1.1.6 + '@rspack/binding-win32-arm64-msvc': 1.1.6 + '@rspack/binding-win32-ia32-msvc': 1.1.6 + '@rspack/binding-win32-x64-msvc': 1.1.6 + + '@rspack/core@1.1.6': + dependencies: + '@module-federation/runtime-tools': 0.5.1 + '@rspack/binding': 1.1.6 + '@rspack/lite-tapable': 1.0.1 + caniuse-lite: 1.0.30001687 + + '@rspack/lite-tapable@1.0.1': {} + + '@sideway/address@4.1.5': + dependencies: + '@hapi/hoek': 9.3.0 + + '@sideway/formula@3.0.1': {} + + '@sideway/pinpoint@2.0.0': {} + + '@sinclair/typebox@0.27.8': {} + + '@sindresorhus/is@4.6.0': {} + + '@sindresorhus/is@5.6.0': {} + + '@slorber/react-ideal-image@0.0.12(prop-types@15.8.1)(react-waypoint@10.3.0(react@18.3.1))(react@18.3.1)': + dependencies: + prop-types: 15.8.1 + react: 18.3.1 + react-waypoint: 10.3.0(react@18.3.1) + + '@slorber/remark-comment@1.0.0': + dependencies: + micromark-factory-space: 1.1.0 + micromark-util-character: 1.2.0 + micromark-util-symbol: 1.1.0 + + '@svgr/babel-plugin-add-jsx-attribute@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-remove-jsx-attribute@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-svg-dynamic-title@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-svg-em-dimensions@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-transform-react-native-svg@8.1.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-plugin-transform-svg-component@8.0.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + + '@svgr/babel-preset@8.1.0(@babel/core@7.26.0)': + dependencies: + '@babel/core': 7.26.0 + '@svgr/babel-plugin-add-jsx-attribute': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-remove-jsx-attribute': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-remove-jsx-empty-expression': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-replace-jsx-attribute-value': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-svg-dynamic-title': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-svg-em-dimensions': 8.0.0(@babel/core@7.26.0) + '@svgr/babel-plugin-transform-react-native-svg': 8.1.0(@babel/core@7.26.0) + '@svgr/babel-plugin-transform-svg-component': 8.0.0(@babel/core@7.26.0) + + '@svgr/core@8.1.0(typescript@5.7.2)': + dependencies: + '@babel/core': 7.26.0 + '@svgr/babel-preset': 8.1.0(@babel/core@7.26.0) + camelcase: 6.3.0 + cosmiconfig: 8.3.6(typescript@5.7.2) + snake-case: 3.0.4 + transitivePeerDependencies: + - supports-color + - typescript + + '@svgr/hast-util-to-babel-ast@8.0.0': + dependencies: + '@babel/types': 7.26.3 + entities: 4.5.0 + + '@svgr/plugin-jsx@8.1.0(@svgr/core@8.1.0(typescript@5.7.2))': + dependencies: + '@babel/core': 7.26.0 + '@svgr/babel-preset': 8.1.0(@babel/core@7.26.0) + '@svgr/core': 8.1.0(typescript@5.7.2) + '@svgr/hast-util-to-babel-ast': 8.0.0 + svg-parser: 2.0.4 + transitivePeerDependencies: + - supports-color + + '@svgr/plugin-svgo@8.1.0(@svgr/core@8.1.0(typescript@5.7.2))(typescript@5.7.2)': + dependencies: + '@svgr/core': 8.1.0(typescript@5.7.2) + cosmiconfig: 8.3.6(typescript@5.7.2) + deepmerge: 4.3.1 + svgo: 3.3.2 + transitivePeerDependencies: + - typescript + + '@svgr/webpack@8.1.0(typescript@5.7.2)': + dependencies: + '@babel/core': 7.26.0 + '@babel/plugin-transform-react-constant-elements': 7.25.9(@babel/core@7.26.0) + '@babel/preset-env': 7.26.0(@babel/core@7.26.0) + '@babel/preset-react': 7.26.3(@babel/core@7.26.0) + '@babel/preset-typescript': 7.26.0(@babel/core@7.26.0) + '@svgr/core': 8.1.0(typescript@5.7.2) + '@svgr/plugin-jsx': 8.1.0(@svgr/core@8.1.0(typescript@5.7.2)) + '@svgr/plugin-svgo': 8.1.0(@svgr/core@8.1.0(typescript@5.7.2))(typescript@5.7.2) + transitivePeerDependencies: + - supports-color + - typescript + + '@swc/core-darwin-arm64@1.10.1': + optional: true + + '@swc/core-darwin-x64@1.10.1': + optional: true + + '@swc/core-linux-arm-gnueabihf@1.10.1': + optional: true + + '@swc/core-linux-arm64-gnu@1.10.1': + optional: true + + '@swc/core-linux-arm64-musl@1.10.1': + optional: true + + '@swc/core-linux-x64-gnu@1.10.1': + optional: true + + '@swc/core-linux-x64-musl@1.10.1': + optional: true + + '@swc/core-win32-arm64-msvc@1.10.1': + optional: true + + '@swc/core-win32-ia32-msvc@1.10.1': + optional: true + + '@swc/core-win32-x64-msvc@1.10.1': + optional: true + + '@swc/core@1.10.1': + dependencies: + '@swc/counter': 0.1.3 + '@swc/types': 0.1.17 + optionalDependencies: + '@swc/core-darwin-arm64': 1.10.1 + '@swc/core-darwin-x64': 1.10.1 + '@swc/core-linux-arm-gnueabihf': 1.10.1 + '@swc/core-linux-arm64-gnu': 1.10.1 + '@swc/core-linux-arm64-musl': 1.10.1 + '@swc/core-linux-x64-gnu': 1.10.1 + '@swc/core-linux-x64-musl': 1.10.1 + '@swc/core-win32-arm64-msvc': 1.10.1 + '@swc/core-win32-ia32-msvc': 1.10.1 + '@swc/core-win32-x64-msvc': 1.10.1 + + '@swc/counter@0.1.3': {} + + '@swc/html-darwin-arm64@1.10.1': + optional: true + + '@swc/html-darwin-x64@1.10.1': + optional: true + + '@swc/html-linux-arm-gnueabihf@1.10.1': + optional: true + + '@swc/html-linux-arm64-gnu@1.10.1': + optional: true + + '@swc/html-linux-arm64-musl@1.10.1': + optional: true + + '@swc/html-linux-x64-gnu@1.10.1': + optional: true + + '@swc/html-linux-x64-musl@1.10.1': + optional: true + + '@swc/html-win32-arm64-msvc@1.10.1': + optional: true + + '@swc/html-win32-ia32-msvc@1.10.1': + optional: true + + '@swc/html-win32-x64-msvc@1.10.1': + optional: true + + '@swc/html@1.10.1': + dependencies: + '@swc/counter': 0.1.3 + optionalDependencies: + '@swc/html-darwin-arm64': 1.10.1 + '@swc/html-darwin-x64': 1.10.1 + '@swc/html-linux-arm-gnueabihf': 1.10.1 + '@swc/html-linux-arm64-gnu': 1.10.1 + '@swc/html-linux-arm64-musl': 1.10.1 + '@swc/html-linux-x64-gnu': 1.10.1 + '@swc/html-linux-x64-musl': 1.10.1 + '@swc/html-win32-arm64-msvc': 1.10.1 + '@swc/html-win32-ia32-msvc': 1.10.1 + '@swc/html-win32-x64-msvc': 1.10.1 + + '@swc/types@0.1.17': + dependencies: + '@swc/counter': 0.1.3 + + '@szmarczak/http-timer@5.0.1': + dependencies: + defer-to-connect: 2.0.1 + + '@trysound/sax@0.2.0': {} + + '@types/acorn@4.0.6': + dependencies: + '@types/estree': 1.0.6 + + '@types/body-parser@1.19.5': + dependencies: + '@types/connect': 3.4.38 + '@types/node': 22.10.1 + + '@types/bonjour@3.5.13': + dependencies: + '@types/node': 22.10.1 + + '@types/connect-history-api-fallback@1.5.4': + dependencies: + '@types/express-serve-static-core': 5.0.2 + '@types/node': 22.10.1 + + '@types/connect@3.4.38': + dependencies: + '@types/node': 22.10.1 + + '@types/debug@4.1.12': + dependencies: + '@types/ms': 0.7.34 + + '@types/eslint-scope@3.7.7': + dependencies: + '@types/eslint': 9.6.1 + '@types/estree': 1.0.6 + + '@types/eslint@9.6.1': + dependencies: + '@types/estree': 1.0.6 + '@types/json-schema': 7.0.15 + + '@types/estree-jsx@1.0.5': + dependencies: + '@types/estree': 1.0.6 + + '@types/estree@1.0.6': {} + + '@types/express-serve-static-core@4.19.6': + dependencies: + '@types/node': 22.10.1 + '@types/qs': 6.9.17 + '@types/range-parser': 1.2.7 + '@types/send': 0.17.4 + + '@types/express-serve-static-core@5.0.2': + dependencies: + '@types/node': 22.10.1 + '@types/qs': 6.9.17 + '@types/range-parser': 1.2.7 + '@types/send': 0.17.4 + + '@types/express@4.17.21': + dependencies: + '@types/body-parser': 1.19.5 + '@types/express-serve-static-core': 4.19.6 + '@types/qs': 6.9.17 + '@types/serve-static': 1.15.7 + + '@types/gtag.js@0.0.12': {} + + '@types/hast@3.0.4': + dependencies: + '@types/unist': 3.0.3 + + '@types/history@4.7.11': {} + + '@types/html-minifier-terser@6.1.0': {} + + '@types/http-cache-semantics@4.0.4': {} + + '@types/http-errors@2.0.4': {} + + '@types/http-proxy@1.17.15': + dependencies: + '@types/node': 22.10.1 + + '@types/istanbul-lib-coverage@2.0.6': {} + + '@types/istanbul-lib-report@3.0.3': + dependencies: + '@types/istanbul-lib-coverage': 2.0.6 + + '@types/istanbul-reports@3.0.4': + dependencies: + '@types/istanbul-lib-report': 3.0.3 + + '@types/json-schema@7.0.15': {} + + '@types/mdast@4.0.4': + dependencies: + '@types/unist': 3.0.3 + + '@types/mdx@2.0.13': {} + + '@types/mime@1.3.5': {} + + '@types/ms@0.7.34': {} + + '@types/node-forge@1.3.11': + dependencies: + '@types/node': 22.10.1 + + '@types/node@17.0.45': {} + + '@types/node@22.10.1': + dependencies: + undici-types: 6.20.0 + + '@types/parse-json@4.0.2': {} + + '@types/prismjs@1.26.5': {} + + '@types/qs@6.9.17': {} + + '@types/range-parser@1.2.7': {} + + '@types/react-router-config@5.0.11': + dependencies: + '@types/history': 4.7.11 + '@types/react': 19.0.1 + '@types/react-router': 5.1.20 + + '@types/react-router-dom@5.3.3': + dependencies: + '@types/history': 4.7.11 + '@types/react': 19.0.1 + '@types/react-router': 5.1.20 + + '@types/react-router@5.1.20': + dependencies: + '@types/history': 4.7.11 + '@types/react': 19.0.1 + + '@types/react@19.0.1': + dependencies: + csstype: 3.1.3 + + '@types/retry@0.12.0': {} + + '@types/sax@1.2.7': + dependencies: + '@types/node': 17.0.45 + + '@types/send@0.17.4': + dependencies: + '@types/mime': 1.3.5 + '@types/node': 22.10.1 + + '@types/serve-index@1.9.4': + dependencies: + '@types/express': 4.17.21 + + '@types/serve-static@1.15.7': + dependencies: + '@types/http-errors': 2.0.4 + '@types/node': 22.10.1 + '@types/send': 0.17.4 + + '@types/sockjs@0.3.36': + dependencies: + '@types/node': 22.10.1 + + '@types/unist@2.0.11': {} + + '@types/unist@3.0.3': {} + + '@types/ws@8.5.13': + dependencies: + '@types/node': 22.10.1 + + '@types/yargs-parser@21.0.3': {} + + '@types/yargs@17.0.33': + dependencies: + '@types/yargs-parser': 21.0.3 + + '@ungap/structured-clone@1.2.1': {} + + '@webassemblyjs/ast@1.14.1': + dependencies: + '@webassemblyjs/helper-numbers': 1.13.2 + '@webassemblyjs/helper-wasm-bytecode': 1.13.2 + + '@webassemblyjs/floating-point-hex-parser@1.13.2': {} + + '@webassemblyjs/helper-api-error@1.13.2': {} + + '@webassemblyjs/helper-buffer@1.14.1': {} + + '@webassemblyjs/helper-numbers@1.13.2': + dependencies: + '@webassemblyjs/floating-point-hex-parser': 1.13.2 + '@webassemblyjs/helper-api-error': 1.13.2 + '@xtuc/long': 4.2.2 + + '@webassemblyjs/helper-wasm-bytecode@1.13.2': {} + + '@webassemblyjs/helper-wasm-section@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/helper-buffer': 1.14.1 + '@webassemblyjs/helper-wasm-bytecode': 1.13.2 + '@webassemblyjs/wasm-gen': 1.14.1 + + '@webassemblyjs/ieee754@1.13.2': + dependencies: + '@xtuc/ieee754': 1.2.0 + + '@webassemblyjs/leb128@1.13.2': + dependencies: + '@xtuc/long': 4.2.2 + + '@webassemblyjs/utf8@1.13.2': {} + + '@webassemblyjs/wasm-edit@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/helper-buffer': 1.14.1 + '@webassemblyjs/helper-wasm-bytecode': 1.13.2 + '@webassemblyjs/helper-wasm-section': 1.14.1 + '@webassemblyjs/wasm-gen': 1.14.1 + '@webassemblyjs/wasm-opt': 1.14.1 + '@webassemblyjs/wasm-parser': 1.14.1 + '@webassemblyjs/wast-printer': 1.14.1 + + '@webassemblyjs/wasm-gen@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/helper-wasm-bytecode': 1.13.2 + '@webassemblyjs/ieee754': 1.13.2 + '@webassemblyjs/leb128': 1.13.2 + '@webassemblyjs/utf8': 1.13.2 + + '@webassemblyjs/wasm-opt@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/helper-buffer': 1.14.1 + '@webassemblyjs/wasm-gen': 1.14.1 + '@webassemblyjs/wasm-parser': 1.14.1 + + '@webassemblyjs/wasm-parser@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/helper-api-error': 1.13.2 + '@webassemblyjs/helper-wasm-bytecode': 1.13.2 + '@webassemblyjs/ieee754': 1.13.2 + '@webassemblyjs/leb128': 1.13.2 + '@webassemblyjs/utf8': 1.13.2 + + '@webassemblyjs/wast-printer@1.14.1': + dependencies: + '@webassemblyjs/ast': 1.14.1 + '@xtuc/long': 4.2.2 + + '@xtuc/ieee754@1.2.0': {} + + '@xtuc/long@4.2.2': {} + + accepts@1.3.8: + dependencies: + mime-types: 2.1.35 + negotiator: 0.6.3 + + acorn-jsx@5.3.2(acorn@8.14.0): + dependencies: + acorn: 8.14.0 + + acorn-walk@8.3.4: + dependencies: + acorn: 8.14.0 + + acorn@8.14.0: {} + + address@1.2.2: {} + + aggregate-error@3.1.0: + dependencies: + clean-stack: 2.2.0 + indent-string: 4.0.0 + + ajv-formats@2.1.1(ajv@8.17.1): + optionalDependencies: + ajv: 8.17.1 + + ajv-keywords@3.5.2(ajv@6.12.6): + dependencies: + ajv: 6.12.6 + + ajv-keywords@5.1.0(ajv@8.17.1): + dependencies: + ajv: 8.17.1 + fast-deep-equal: 3.1.3 + + ajv@6.12.6: + dependencies: + fast-deep-equal: 3.1.3 + fast-json-stable-stringify: 2.1.0 + json-schema-traverse: 0.4.1 + uri-js: 4.4.1 + + ajv@8.17.1: + dependencies: + fast-deep-equal: 3.1.3 + fast-uri: 3.0.3 + json-schema-traverse: 1.0.0 + require-from-string: 2.0.2 + + algoliasearch-helper@3.22.6(algoliasearch@4.24.0): + dependencies: + '@algolia/events': 4.0.1 + algoliasearch: 4.24.0 + + algoliasearch@4.24.0: + dependencies: + '@algolia/cache-browser-local-storage': 4.24.0 + '@algolia/cache-common': 4.24.0 + '@algolia/cache-in-memory': 4.24.0 + '@algolia/client-account': 4.24.0 + '@algolia/client-analytics': 4.24.0 + '@algolia/client-common': 4.24.0 + '@algolia/client-personalization': 4.24.0 + '@algolia/client-search': 4.24.0 + '@algolia/logger-common': 4.24.0 + '@algolia/logger-console': 4.24.0 + '@algolia/recommend': 4.24.0 + '@algolia/requester-browser-xhr': 4.24.0 + '@algolia/requester-common': 4.24.0 + '@algolia/requester-node-http': 4.24.0 + '@algolia/transporter': 4.24.0 + + algoliasearch@5.17.0: + dependencies: + '@algolia/client-abtesting': 5.17.0 + '@algolia/client-analytics': 5.17.0 + '@algolia/client-common': 5.17.0 + '@algolia/client-insights': 5.17.0 + '@algolia/client-personalization': 5.17.0 + '@algolia/client-query-suggestions': 5.17.0 + '@algolia/client-search': 5.17.0 + '@algolia/ingestion': 1.17.0 + '@algolia/monitoring': 1.17.0 + '@algolia/recommend': 5.17.0 + '@algolia/requester-browser-xhr': 5.17.0 + '@algolia/requester-fetch': 5.17.0 + '@algolia/requester-node-http': 5.17.0 + + ansi-align@3.0.1: + dependencies: + string-width: 4.2.3 + + ansi-escapes@4.3.2: + dependencies: + type-fest: 0.21.3 + + ansi-html-community@0.0.8: {} + + ansi-regex@5.0.1: {} + + ansi-regex@6.1.0: {} + + ansi-styles@4.3.0: + dependencies: + color-convert: 2.0.1 + + ansi-styles@6.2.1: {} + + anymatch@3.1.3: + dependencies: + normalize-path: 3.0.0 + picomatch: 2.3.1 + + arg@5.0.2: {} + + argparse@1.0.10: + dependencies: + sprintf-js: 1.0.3 + + argparse@2.0.1: {} + + array-flatten@1.1.1: {} + + array-union@2.1.0: {} + + astring@1.9.0: {} + + at-least-node@1.0.0: {} + + autoprefixer@10.4.20(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + caniuse-lite: 1.0.30001687 + fraction.js: 4.3.7 + normalize-range: 0.1.2 + picocolors: 1.1.1 + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + b4a@1.6.7: {} + + babel-loader@9.2.1(@babel/core@7.26.0)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@babel/core': 7.26.0 + find-cache-dir: 4.0.0 + schema-utils: 4.2.0 + webpack: 5.97.1(@swc/core@1.10.1) + + babel-plugin-dynamic-import-node@2.3.3: + dependencies: + object.assign: 4.1.5 + + babel-plugin-polyfill-corejs2@0.4.12(@babel/core@7.26.0): + dependencies: + '@babel/compat-data': 7.26.3 + '@babel/core': 7.26.0 + '@babel/helper-define-polyfill-provider': 0.6.3(@babel/core@7.26.0) + semver: 6.3.1 + transitivePeerDependencies: + - supports-color + + babel-plugin-polyfill-corejs3@0.10.6(@babel/core@7.26.0): + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-define-polyfill-provider': 0.6.3(@babel/core@7.26.0) + core-js-compat: 3.39.0 + transitivePeerDependencies: + - supports-color + + babel-plugin-polyfill-regenerator@0.6.3(@babel/core@7.26.0): + dependencies: + '@babel/core': 7.26.0 + '@babel/helper-define-polyfill-provider': 0.6.3(@babel/core@7.26.0) + transitivePeerDependencies: + - supports-color + + bail@2.0.2: {} + + balanced-match@1.0.2: {} + + bare-events@2.5.0: + optional: true + + bare-fs@2.3.5: + dependencies: + bare-events: 2.5.0 + bare-path: 2.1.3 + bare-stream: 2.4.2 + optional: true + + bare-os@2.4.4: + optional: true + + bare-path@2.1.3: + dependencies: + bare-os: 2.4.4 + optional: true + + bare-stream@2.4.2: + dependencies: + streamx: 2.21.0 + optional: true + + base64-js@1.5.1: {} + + batch@0.6.1: {} + + big.js@5.2.2: {} + + binary-extensions@2.3.0: {} + + bl@4.1.0: + dependencies: + buffer: 5.7.1 + inherits: 2.0.4 + readable-stream: 3.6.2 + + body-parser@1.20.3: + dependencies: + bytes: 3.1.2 + content-type: 1.0.5 + debug: 2.6.9 + depd: 2.0.0 + destroy: 1.2.0 + http-errors: 2.0.0 + iconv-lite: 0.4.24 + on-finished: 2.4.1 + qs: 6.13.0 + raw-body: 2.5.2 + type-is: 1.6.18 + unpipe: 1.0.0 + transitivePeerDependencies: + - supports-color + + bonjour-service@1.3.0: + dependencies: + fast-deep-equal: 3.1.3 + multicast-dns: 7.2.5 + + boolbase@1.0.0: {} + + boxen@6.2.1: + dependencies: + ansi-align: 3.0.1 + camelcase: 6.3.0 + chalk: 4.1.2 + cli-boxes: 3.0.0 + string-width: 5.1.2 + type-fest: 2.19.0 + widest-line: 4.0.1 + wrap-ansi: 8.1.0 + + boxen@7.1.1: + dependencies: + ansi-align: 3.0.1 + camelcase: 7.0.1 + chalk: 5.3.0 + cli-boxes: 3.0.0 + string-width: 5.1.2 + type-fest: 2.19.0 + widest-line: 4.0.1 + wrap-ansi: 8.1.0 + + brace-expansion@1.1.11: + dependencies: + balanced-match: 1.0.2 + concat-map: 0.0.1 + + braces@3.0.3: + dependencies: + fill-range: 7.1.1 + + browserslist@4.24.2: + dependencies: + caniuse-lite: 1.0.30001687 + electron-to-chromium: 1.5.72 + node-releases: 2.0.19 + update-browserslist-db: 1.1.1(browserslist@4.24.2) + + buffer-from@1.1.2: {} + + buffer@5.7.1: + dependencies: + base64-js: 1.5.1 + ieee754: 1.2.1 + + bytes@3.0.0: {} + + bytes@3.1.2: {} + + cacheable-lookup@7.0.0: {} + + cacheable-request@10.2.14: + dependencies: + '@types/http-cache-semantics': 4.0.4 + get-stream: 6.0.1 + http-cache-semantics: 4.1.1 + keyv: 4.5.4 + mimic-response: 4.0.0 + normalize-url: 8.0.1 + responselike: 3.0.0 + + call-bind-apply-helpers@1.0.1: + dependencies: + es-errors: 1.3.0 + function-bind: 1.1.2 + + call-bind@1.0.8: + dependencies: + call-bind-apply-helpers: 1.0.1 + es-define-property: 1.0.1 + get-intrinsic: 1.2.5 + set-function-length: 1.2.2 + + callsites@3.1.0: {} + + camel-case@4.1.2: + dependencies: + pascal-case: 3.1.2 + tslib: 2.8.1 + + camelcase@6.3.0: {} + + camelcase@7.0.1: {} + + caniuse-api@3.0.0: + dependencies: + browserslist: 4.24.2 + caniuse-lite: 1.0.30001687 + lodash.memoize: 4.1.2 + lodash.uniq: 4.5.0 + + caniuse-lite@1.0.30001687: {} + + ccount@2.0.1: {} + + chalk@4.1.2: + dependencies: + ansi-styles: 4.3.0 + supports-color: 7.2.0 + + chalk@5.3.0: {} + + char-regex@1.0.2: {} + + character-entities-html4@2.1.0: {} + + character-entities-legacy@3.0.0: {} + + character-entities@2.0.2: {} + + character-reference-invalid@2.0.1: {} + + cheerio-select@2.1.0: + dependencies: + boolbase: 1.0.0 + css-select: 5.1.0 + css-what: 6.1.0 + domelementtype: 2.3.0 + domhandler: 5.0.3 + domutils: 3.1.0 + + cheerio@1.0.0: + dependencies: + cheerio-select: 2.1.0 + dom-serializer: 2.0.0 + domhandler: 5.0.3 + domutils: 3.1.0 + encoding-sniffer: 0.2.0 + htmlparser2: 9.1.0 + parse5: 7.2.1 + parse5-htmlparser2-tree-adapter: 7.1.0 + parse5-parser-stream: 7.1.2 + undici: 6.21.0 + whatwg-mimetype: 4.0.0 + + cheerio@1.0.0-rc.12: + dependencies: + cheerio-select: 2.1.0 + dom-serializer: 2.0.0 + domhandler: 5.0.3 + domutils: 3.1.0 + htmlparser2: 8.0.2 + parse5: 7.2.1 + parse5-htmlparser2-tree-adapter: 7.1.0 + + chokidar@3.6.0: + dependencies: + anymatch: 3.1.3 + braces: 3.0.3 + glob-parent: 5.1.2 + is-binary-path: 2.1.0 + is-glob: 4.0.3 + normalize-path: 3.0.0 + readdirp: 3.6.0 + optionalDependencies: + fsevents: 2.3.3 + + chownr@1.1.4: {} + + chrome-trace-event@1.0.4: {} + + ci-info@3.9.0: {} + + clean-css@5.3.3: + dependencies: + source-map: 0.6.1 + + clean-stack@2.2.0: {} + + cli-boxes@3.0.0: {} + + cli-table3@0.6.5: + dependencies: + string-width: 4.2.3 + optionalDependencies: + '@colors/colors': 1.5.0 + + clone-deep@4.0.1: + dependencies: + is-plain-object: 2.0.4 + kind-of: 6.0.3 + shallow-clone: 3.0.1 + + clsx@1.2.1: {} + + clsx@2.1.1: {} + + collapse-white-space@2.1.0: {} + + color-convert@2.0.1: + dependencies: + color-name: 1.1.4 + + color-name@1.1.4: {} + + color-string@1.9.1: + dependencies: + color-name: 1.1.4 + simple-swizzle: 0.2.2 + + color@4.2.3: + dependencies: + color-convert: 2.0.1 + color-string: 1.9.1 + + colord@2.9.3: {} + + colorette@2.0.20: {} + + combine-promises@1.2.0: {} + + comma-separated-tokens@2.0.3: {} + + commander@10.0.1: {} + + commander@2.20.3: {} + + commander@5.1.0: {} + + commander@7.2.0: {} + + commander@8.3.0: {} + + common-path-prefix@3.0.0: {} + + compressible@2.0.18: + dependencies: + mime-db: 1.53.0 + + compression@1.7.5: + dependencies: + bytes: 3.1.2 + compressible: 2.0.18 + debug: 2.6.9 + negotiator: 0.6.4 + on-headers: 1.0.2 + safe-buffer: 5.2.1 + vary: 1.1.2 + transitivePeerDependencies: + - supports-color + + concat-map@0.0.1: {} + + config-chain@1.1.13: + dependencies: + ini: 1.3.8 + proto-list: 1.2.4 + + configstore@6.0.0: + dependencies: + dot-prop: 6.0.1 + graceful-fs: 4.2.11 + unique-string: 3.0.0 + write-file-atomic: 3.0.3 + xdg-basedir: 5.1.0 + + connect-history-api-fallback@2.0.0: {} + + consola@3.2.3: {} + + consolidated-events@2.0.2: {} + + content-disposition@0.5.2: {} + + content-disposition@0.5.4: + dependencies: + safe-buffer: 5.2.1 + + content-type@1.0.5: {} + + convert-source-map@2.0.0: {} + + cookie-signature@1.0.6: {} + + cookie@0.7.1: {} + + copy-text-to-clipboard@3.2.0: {} + + copy-webpack-plugin@11.0.0(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + fast-glob: 3.3.2 + glob-parent: 6.0.2 + globby: 13.2.2 + normalize-path: 3.0.0 + schema-utils: 4.2.0 + serialize-javascript: 6.0.2 + webpack: 5.97.1(@swc/core@1.10.1) + + core-js-compat@3.39.0: + dependencies: + browserslist: 4.24.2 + + core-js-pure@3.39.0: {} + + core-js@3.39.0: {} + + core-util-is@1.0.3: {} + + cosmiconfig@6.0.0: + dependencies: + '@types/parse-json': 4.0.2 + import-fresh: 3.3.0 + parse-json: 5.2.0 + path-type: 4.0.0 + yaml: 1.10.2 + + cosmiconfig@8.3.6(typescript@5.7.2): + dependencies: + import-fresh: 3.3.0 + js-yaml: 4.1.0 + parse-json: 5.2.0 + path-type: 4.0.0 + optionalDependencies: + typescript: 5.7.2 + + cross-spawn@7.0.6: + dependencies: + path-key: 3.1.1 + shebang-command: 2.0.0 + which: 2.0.2 + + crypto-random-string@4.0.0: + dependencies: + type-fest: 1.4.0 + + css-blank-pseudo@7.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + css-declaration-sorter@7.2.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + css-has-pseudo@7.0.1(postcss@8.4.49): + dependencies: + '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.0.0) + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + postcss-value-parser: 4.2.0 + + css-loader@6.11.0(@rspack/core@1.1.6)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + icss-utils: 5.1.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-modules-extract-imports: 3.1.0(postcss@8.4.49) + postcss-modules-local-by-default: 4.1.0(postcss@8.4.49) + postcss-modules-scope: 3.2.1(postcss@8.4.49) + postcss-modules-values: 4.0.0(postcss@8.4.49) + postcss-value-parser: 4.2.0 + semver: 7.6.3 + optionalDependencies: + '@rspack/core': 1.1.6 + webpack: 5.97.1(@swc/core@1.10.1) + + css-minimizer-webpack-plugin@5.0.1(clean-css@5.3.3)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@jridgewell/trace-mapping': 0.3.25 + cssnano: 6.1.2(postcss@8.4.49) + jest-worker: 29.7.0 + postcss: 8.4.49 + schema-utils: 4.2.0 + serialize-javascript: 6.0.2 + webpack: 5.97.1(@swc/core@1.10.1) + optionalDependencies: + clean-css: 5.3.3 + + css-prefers-color-scheme@10.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + css-select@4.3.0: + dependencies: + boolbase: 1.0.0 + css-what: 6.1.0 + domhandler: 4.3.1 + domutils: 2.8.0 + nth-check: 2.1.1 + + css-select@5.1.0: + dependencies: + boolbase: 1.0.0 + css-what: 6.1.0 + domhandler: 5.0.3 + domutils: 3.1.0 + nth-check: 2.1.1 + + css-tree@2.2.1: + dependencies: + mdn-data: 2.0.28 + source-map-js: 1.2.1 + + css-tree@2.3.1: + dependencies: + mdn-data: 2.0.30 + source-map-js: 1.2.1 + + css-what@6.1.0: {} + + cssdb@8.2.3: {} + + cssesc@3.0.0: {} + + cssnano-preset-advanced@6.1.2(postcss@8.4.49): + dependencies: + autoprefixer: 10.4.20(postcss@8.4.49) + browserslist: 4.24.2 + cssnano-preset-default: 6.1.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-discard-unused: 6.0.5(postcss@8.4.49) + postcss-merge-idents: 6.0.3(postcss@8.4.49) + postcss-reduce-idents: 6.0.3(postcss@8.4.49) + postcss-zindex: 6.0.2(postcss@8.4.49) + + cssnano-preset-default@6.1.2(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + css-declaration-sorter: 7.2.0(postcss@8.4.49) + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-calc: 9.0.1(postcss@8.4.49) + postcss-colormin: 6.1.0(postcss@8.4.49) + postcss-convert-values: 6.1.0(postcss@8.4.49) + postcss-discard-comments: 6.0.2(postcss@8.4.49) + postcss-discard-duplicates: 6.0.3(postcss@8.4.49) + postcss-discard-empty: 6.0.3(postcss@8.4.49) + postcss-discard-overridden: 6.0.2(postcss@8.4.49) + postcss-merge-longhand: 6.0.5(postcss@8.4.49) + postcss-merge-rules: 6.1.1(postcss@8.4.49) + postcss-minify-font-values: 6.1.0(postcss@8.4.49) + postcss-minify-gradients: 6.0.3(postcss@8.4.49) + postcss-minify-params: 6.1.0(postcss@8.4.49) + postcss-minify-selectors: 6.0.4(postcss@8.4.49) + postcss-normalize-charset: 6.0.2(postcss@8.4.49) + postcss-normalize-display-values: 6.0.2(postcss@8.4.49) + postcss-normalize-positions: 6.0.2(postcss@8.4.49) + postcss-normalize-repeat-style: 6.0.2(postcss@8.4.49) + postcss-normalize-string: 6.0.2(postcss@8.4.49) + postcss-normalize-timing-functions: 6.0.2(postcss@8.4.49) + postcss-normalize-unicode: 6.1.0(postcss@8.4.49) + postcss-normalize-url: 6.0.2(postcss@8.4.49) + postcss-normalize-whitespace: 6.0.2(postcss@8.4.49) + postcss-ordered-values: 6.0.2(postcss@8.4.49) + postcss-reduce-initial: 6.1.0(postcss@8.4.49) + postcss-reduce-transforms: 6.0.2(postcss@8.4.49) + postcss-svgo: 6.0.3(postcss@8.4.49) + postcss-unique-selectors: 6.0.4(postcss@8.4.49) + + cssnano-utils@4.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + cssnano@6.1.2(postcss@8.4.49): + dependencies: + cssnano-preset-default: 6.1.2(postcss@8.4.49) + lilconfig: 3.1.3 + postcss: 8.4.49 + + csso@5.0.5: + dependencies: + css-tree: 2.2.1 + + csstype@3.1.3: {} + + debounce@1.2.1: {} + + debug@2.6.9: + dependencies: + ms: 2.0.0 + + debug@4.4.0: + dependencies: + ms: 2.1.3 + + decode-named-character-reference@1.0.2: + dependencies: + character-entities: 2.0.2 + + decompress-response@6.0.0: + dependencies: + mimic-response: 3.1.0 + + deep-extend@0.6.0: {} + + deepmerge@4.3.1: {} + + default-gateway@6.0.3: + dependencies: + execa: 5.1.1 + + defer-to-connect@2.0.1: {} + + define-data-property@1.1.4: + dependencies: + es-define-property: 1.0.1 + es-errors: 1.3.0 + gopd: 1.2.0 + + define-lazy-prop@2.0.0: {} + + define-properties@1.2.1: + dependencies: + define-data-property: 1.1.4 + has-property-descriptors: 1.0.2 + object-keys: 1.1.1 + + del@6.1.1: + dependencies: + globby: 11.1.0 + graceful-fs: 4.2.11 + is-glob: 4.0.3 + is-path-cwd: 2.2.0 + is-path-inside: 3.0.3 + p-map: 4.0.0 + rimraf: 3.0.2 + slash: 3.0.0 + + depd@1.1.2: {} + + depd@2.0.0: {} + + dequal@2.0.3: {} + + destroy@1.2.0: {} + + detect-libc@1.0.3: {} + + detect-libc@2.0.3: {} + + detect-node@2.1.0: {} + + detect-port-alt@1.1.6: + dependencies: + address: 1.2.2 + debug: 2.6.9 + transitivePeerDependencies: + - supports-color + + detect-port@1.6.1: + dependencies: + address: 1.2.2 + debug: 4.4.0 + transitivePeerDependencies: + - supports-color + + devlop@1.1.0: + dependencies: + dequal: 2.0.3 + + dir-glob@3.0.1: + dependencies: + path-type: 4.0.0 + + dns-packet@5.6.1: + dependencies: + '@leichtgewicht/ip-codec': 2.0.5 + + docusaurus-plugin-image-zoom@2.0.0(@docusaurus/theme-classic@3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2)): + dependencies: + '@docusaurus/theme-classic': 3.6.3(@docusaurus/faster@3.6.3(@docusaurus/types@3.6.3(@swc/core@1.10.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)))(@rspack/core@1.1.6)(@swc/core@1.10.1)(@types/react@19.0.1)(acorn@8.14.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(typescript@5.7.2) + medium-zoom: 1.1.0 + validate-peer-dependencies: 2.2.0 + + dom-converter@0.2.0: + dependencies: + utila: 0.4.0 + + dom-serializer@1.4.1: + dependencies: + domelementtype: 2.3.0 + domhandler: 4.3.1 + entities: 2.2.0 + + dom-serializer@2.0.0: + dependencies: + domelementtype: 2.3.0 + domhandler: 5.0.3 + entities: 4.5.0 + + domelementtype@2.3.0: {} + + domhandler@4.3.1: + dependencies: + domelementtype: 2.3.0 + + domhandler@5.0.3: + dependencies: + domelementtype: 2.3.0 + + domutils@2.8.0: + dependencies: + dom-serializer: 1.4.1 + domelementtype: 2.3.0 + domhandler: 4.3.1 + + domutils@3.1.0: + dependencies: + dom-serializer: 2.0.0 + domelementtype: 2.3.0 + domhandler: 5.0.3 + + dot-case@3.0.4: + dependencies: + no-case: 3.0.4 + tslib: 2.8.1 + + dot-prop@6.0.1: + dependencies: + is-obj: 2.0.0 + + dunder-proto@1.0.0: + dependencies: + call-bind-apply-helpers: 1.0.1 + es-errors: 1.3.0 + gopd: 1.2.0 + + duplexer@0.1.2: {} + + eastasianwidth@0.2.0: {} + + ee-first@1.1.1: {} + + electron-to-chromium@1.5.72: {} + + emoji-regex@8.0.0: {} + + emoji-regex@9.2.2: {} + + emojilib@2.4.0: {} + + emojis-list@3.0.0: {} + + emoticon@4.1.0: {} + + encodeurl@1.0.2: {} + + encodeurl@2.0.0: {} + + encoding-sniffer@0.2.0: + dependencies: + iconv-lite: 0.6.3 + whatwg-encoding: 3.1.1 + + end-of-stream@1.4.4: + dependencies: + once: 1.4.0 + + enhanced-resolve@5.17.1: + dependencies: + graceful-fs: 4.2.11 + tapable: 2.2.1 + + entities@2.2.0: {} + + entities@4.5.0: {} + + error-ex@1.3.2: + dependencies: + is-arrayish: 0.2.1 + + es-define-property@1.0.1: {} + + es-errors@1.3.0: {} + + es-module-lexer@1.5.4: {} + + esast-util-from-estree@2.0.0: + dependencies: + '@types/estree-jsx': 1.0.5 + devlop: 1.1.0 + estree-util-visit: 2.0.0 + unist-util-position-from-estree: 2.0.0 + + esast-util-from-js@2.0.1: + dependencies: + '@types/estree-jsx': 1.0.5 + acorn: 8.14.0 + esast-util-from-estree: 2.0.0 + vfile-message: 4.0.2 + + escalade@3.2.0: {} + + escape-goat@4.0.0: {} + + escape-html@1.0.3: {} + + escape-string-regexp@1.0.5: {} + + escape-string-regexp@4.0.0: {} + + escape-string-regexp@5.0.0: {} + + eslint-scope@5.1.1: + dependencies: + esrecurse: 4.3.0 + estraverse: 4.3.0 + + esprima@4.0.1: {} + + esrecurse@4.3.0: + dependencies: + estraverse: 5.3.0 + + estraverse@4.3.0: {} + + estraverse@5.3.0: {} + + estree-util-attach-comments@3.0.0: + dependencies: + '@types/estree': 1.0.6 + + estree-util-build-jsx@3.0.1: + dependencies: + '@types/estree-jsx': 1.0.5 + devlop: 1.1.0 + estree-util-is-identifier-name: 3.0.0 + estree-walker: 3.0.3 + + estree-util-is-identifier-name@3.0.0: {} + + estree-util-scope@1.0.0: + dependencies: + '@types/estree': 1.0.6 + devlop: 1.1.0 + + estree-util-to-js@2.0.0: + dependencies: + '@types/estree-jsx': 1.0.5 + astring: 1.9.0 + source-map: 0.7.4 + + estree-util-value-to-estree@3.2.1: + dependencies: + '@types/estree': 1.0.6 + + estree-util-visit@2.0.0: + dependencies: + '@types/estree-jsx': 1.0.5 + '@types/unist': 3.0.3 + + estree-walker@3.0.3: + dependencies: + '@types/estree': 1.0.6 + + esutils@2.0.3: {} + + eta@2.2.0: {} + + etag@1.8.1: {} + + eval@0.1.8: + dependencies: + '@types/node': 22.10.1 + require-like: 0.1.2 + + eventemitter3@4.0.7: {} + + events@3.3.0: {} + + execa@5.1.1: + dependencies: + cross-spawn: 7.0.6 + get-stream: 6.0.1 + human-signals: 2.1.0 + is-stream: 2.0.1 + merge-stream: 2.0.0 + npm-run-path: 4.0.1 + onetime: 5.1.2 + signal-exit: 3.0.7 + strip-final-newline: 2.0.0 + + expand-template@2.0.3: {} + + express@4.21.2: + dependencies: + accepts: 1.3.8 + array-flatten: 1.1.1 + body-parser: 1.20.3 + content-disposition: 0.5.4 + content-type: 1.0.5 + cookie: 0.7.1 + cookie-signature: 1.0.6 + debug: 2.6.9 + depd: 2.0.0 + encodeurl: 2.0.0 + escape-html: 1.0.3 + etag: 1.8.1 + finalhandler: 1.3.1 + fresh: 0.5.2 + http-errors: 2.0.0 + merge-descriptors: 1.0.3 + methods: 1.1.2 + on-finished: 2.4.1 + parseurl: 1.3.3 + path-to-regexp: 0.1.12 + proxy-addr: 2.0.7 + qs: 6.13.0 + range-parser: 1.2.1 + safe-buffer: 5.2.1 + send: 0.19.0 + serve-static: 1.16.2 + setprototypeof: 1.2.0 + statuses: 2.0.1 + type-is: 1.6.18 + utils-merge: 1.0.1 + vary: 1.1.2 + transitivePeerDependencies: + - supports-color + + extend-shallow@2.0.1: + dependencies: + is-extendable: 0.1.1 + + extend@3.0.2: {} + + fast-deep-equal@3.1.3: {} + + fast-fifo@1.3.2: {} + + fast-glob@3.3.2: + dependencies: + '@nodelib/fs.stat': 2.0.5 + '@nodelib/fs.walk': 1.2.8 + glob-parent: 5.1.2 + merge2: 1.4.1 + micromatch: 4.0.8 + + fast-json-stable-stringify@2.1.0: {} + + fast-uri@3.0.3: {} + + fastq@1.17.1: + dependencies: + reusify: 1.0.4 + + fault@2.0.1: + dependencies: + format: 0.2.2 + + faye-websocket@0.11.4: + dependencies: + websocket-driver: 0.7.4 + + feed@4.2.2: + dependencies: + xml-js: 1.6.11 + + figures@3.2.0: + dependencies: + escape-string-regexp: 1.0.5 + + file-loader@6.2.0(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + loader-utils: 2.0.4 + schema-utils: 3.3.0 + webpack: 5.97.1(@swc/core@1.10.1) + + filesize@8.0.7: {} + + fill-range@7.1.1: + dependencies: + to-regex-range: 5.0.1 + + finalhandler@1.3.1: + dependencies: + debug: 2.6.9 + encodeurl: 2.0.0 + escape-html: 1.0.3 + on-finished: 2.4.1 + parseurl: 1.3.3 + statuses: 2.0.1 + unpipe: 1.0.0 + transitivePeerDependencies: + - supports-color + + find-cache-dir@4.0.0: + dependencies: + common-path-prefix: 3.0.0 + pkg-dir: 7.0.0 + + find-up@3.0.0: + dependencies: + locate-path: 3.0.0 + + find-up@5.0.0: + dependencies: + locate-path: 6.0.0 + path-exists: 4.0.0 + + find-up@6.3.0: + dependencies: + locate-path: 7.2.0 + path-exists: 5.0.0 + + flat@5.0.2: {} + + follow-redirects@1.15.9: {} + + fork-ts-checker-webpack-plugin@6.5.3(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@babel/code-frame': 7.26.2 + '@types/json-schema': 7.0.15 + chalk: 4.1.2 + chokidar: 3.6.0 + cosmiconfig: 6.0.0 + deepmerge: 4.3.1 + fs-extra: 9.1.0 + glob: 7.2.3 + memfs: 3.5.3 + minimatch: 3.1.2 + schema-utils: 2.7.0 + semver: 7.6.3 + tapable: 1.1.3 + typescript: 5.7.2 + webpack: 5.97.1(@swc/core@1.10.1) + + form-data-encoder@2.1.4: {} + + format@0.2.2: {} + + forwarded@0.2.0: {} + + fraction.js@4.3.7: {} + + fresh@0.5.2: {} + + fs-constants@1.0.0: {} + + fs-extra@11.2.0: + dependencies: + graceful-fs: 4.2.11 + jsonfile: 6.1.0 + universalify: 2.0.1 + + fs-extra@9.1.0: + dependencies: + at-least-node: 1.0.0 + graceful-fs: 4.2.11 + jsonfile: 6.1.0 + universalify: 2.0.1 + + fs-monkey@1.0.6: {} + + fs.realpath@1.0.0: {} + + fsevents@2.3.3: + optional: true + + function-bind@1.1.2: {} + + gensync@1.0.0-beta.2: {} + + get-intrinsic@1.2.5: + dependencies: + call-bind-apply-helpers: 1.0.1 + dunder-proto: 1.0.0 + es-define-property: 1.0.1 + es-errors: 1.3.0 + function-bind: 1.1.2 + gopd: 1.2.0 + has-symbols: 1.1.0 + hasown: 2.0.2 + + get-own-enumerable-property-symbols@3.0.2: {} + + get-stream@6.0.1: {} + + github-from-package@0.0.0: {} + + github-slugger@1.5.0: {} + + glob-parent@5.1.2: + dependencies: + is-glob: 4.0.3 + + glob-parent@6.0.2: + dependencies: + is-glob: 4.0.3 + + glob-to-regexp@0.4.1: {} + + glob@7.2.3: + dependencies: + fs.realpath: 1.0.0 + inflight: 1.0.6 + inherits: 2.0.4 + minimatch: 3.1.2 + once: 1.4.0 + path-is-absolute: 1.0.1 + + global-dirs@3.0.1: + dependencies: + ini: 2.0.0 + + global-modules@2.0.0: + dependencies: + global-prefix: 3.0.0 + + global-prefix@3.0.0: + dependencies: + ini: 1.3.8 + kind-of: 6.0.3 + which: 1.3.1 + + globals@11.12.0: {} + + globby@11.1.0: + dependencies: + array-union: 2.1.0 + dir-glob: 3.0.1 + fast-glob: 3.3.2 + ignore: 5.3.2 + merge2: 1.4.1 + slash: 3.0.0 + + globby@13.2.2: + dependencies: + dir-glob: 3.0.1 + fast-glob: 3.3.2 + ignore: 5.3.2 + merge2: 1.4.1 + slash: 4.0.0 + + gopd@1.2.0: {} + + got@12.6.1: + dependencies: + '@sindresorhus/is': 5.6.0 + '@szmarczak/http-timer': 5.0.1 + cacheable-lookup: 7.0.0 + cacheable-request: 10.2.14 + decompress-response: 6.0.0 + form-data-encoder: 2.1.4 + get-stream: 6.0.1 + http2-wrapper: 2.2.1 + lowercase-keys: 3.0.0 + p-cancelable: 3.0.0 + responselike: 3.0.0 + + graceful-fs@4.2.10: {} + + graceful-fs@4.2.11: {} + + gray-matter@4.0.3: + dependencies: + js-yaml: 3.14.1 + kind-of: 6.0.3 + section-matter: 1.0.0 + strip-bom-string: 1.0.0 + + gzip-size@6.0.0: + dependencies: + duplexer: 0.1.2 + + handle-thing@2.0.1: {} + + has-flag@4.0.0: {} + + has-property-descriptors@1.0.2: + dependencies: + es-define-property: 1.0.1 + + has-symbols@1.1.0: {} + + has-yarn@3.0.0: {} + + hasown@2.0.2: + dependencies: + function-bind: 1.1.2 + + hast-util-from-parse5@8.0.2: + dependencies: + '@types/hast': 3.0.4 + '@types/unist': 3.0.3 + devlop: 1.1.0 + hastscript: 9.0.0 + property-information: 6.5.0 + vfile: 6.0.3 + vfile-location: 5.0.3 + web-namespaces: 2.0.1 + + hast-util-parse-selector@4.0.0: + dependencies: + '@types/hast': 3.0.4 + + hast-util-raw@9.1.0: + dependencies: + '@types/hast': 3.0.4 + '@types/unist': 3.0.3 + '@ungap/structured-clone': 1.2.1 + hast-util-from-parse5: 8.0.2 + hast-util-to-parse5: 8.0.0 + html-void-elements: 3.0.0 + mdast-util-to-hast: 13.2.0 + parse5: 7.2.1 + unist-util-position: 5.0.0 + unist-util-visit: 5.0.0 + vfile: 6.0.3 + web-namespaces: 2.0.1 + zwitch: 2.0.4 + + hast-util-to-estree@3.1.0: + dependencies: + '@types/estree': 1.0.6 + '@types/estree-jsx': 1.0.5 + '@types/hast': 3.0.4 + comma-separated-tokens: 2.0.3 + devlop: 1.1.0 + estree-util-attach-comments: 3.0.0 + estree-util-is-identifier-name: 3.0.0 + hast-util-whitespace: 3.0.0 + mdast-util-mdx-expression: 2.0.1 + mdast-util-mdx-jsx: 3.1.3 + mdast-util-mdxjs-esm: 2.0.1 + property-information: 6.5.0 + space-separated-tokens: 2.0.2 + style-to-object: 0.4.4 + unist-util-position: 5.0.0 + zwitch: 2.0.4 + transitivePeerDependencies: + - supports-color + + hast-util-to-jsx-runtime@2.3.2: + dependencies: + '@types/estree': 1.0.6 + '@types/hast': 3.0.4 + '@types/unist': 3.0.3 + comma-separated-tokens: 2.0.3 + devlop: 1.1.0 + estree-util-is-identifier-name: 3.0.0 + hast-util-whitespace: 3.0.0 + mdast-util-mdx-expression: 2.0.1 + mdast-util-mdx-jsx: 3.1.3 + mdast-util-mdxjs-esm: 2.0.1 + property-information: 6.5.0 + space-separated-tokens: 2.0.2 + style-to-object: 1.0.8 + unist-util-position: 5.0.0 + vfile-message: 4.0.2 + transitivePeerDependencies: + - supports-color + + hast-util-to-parse5@8.0.0: + dependencies: + '@types/hast': 3.0.4 + comma-separated-tokens: 2.0.3 + devlop: 1.1.0 + property-information: 6.5.0 + space-separated-tokens: 2.0.2 + web-namespaces: 2.0.1 + zwitch: 2.0.4 + + hast-util-whitespace@3.0.0: + dependencies: + '@types/hast': 3.0.4 + + hastscript@9.0.0: + dependencies: + '@types/hast': 3.0.4 + comma-separated-tokens: 2.0.3 + hast-util-parse-selector: 4.0.0 + property-information: 6.5.0 + space-separated-tokens: 2.0.2 + + he@1.2.0: {} + + history@4.10.1: + dependencies: + '@babel/runtime': 7.26.0 + loose-envify: 1.4.0 + resolve-pathname: 3.0.0 + tiny-invariant: 1.3.3 + tiny-warning: 1.0.3 + value-equal: 1.0.1 + + hoist-non-react-statics@3.3.2: + dependencies: + react-is: 16.13.1 + + hpack.js@2.1.6: + dependencies: + inherits: 2.0.4 + obuf: 1.1.2 + readable-stream: 2.3.8 + wbuf: 1.7.3 + + htm@3.1.1: {} + + html-entities@2.5.2: {} + + html-escaper@2.0.2: {} + + html-minifier-terser@6.1.0: + dependencies: + camel-case: 4.1.2 + clean-css: 5.3.3 + commander: 8.3.0 + he: 1.2.0 + param-case: 3.0.4 + relateurl: 0.2.7 + terser: 5.37.0 + + html-minifier-terser@7.2.0: + dependencies: + camel-case: 4.1.2 + clean-css: 5.3.3 + commander: 10.0.1 + entities: 4.5.0 + param-case: 3.0.4 + relateurl: 0.2.7 + terser: 5.37.0 + + html-tags@3.3.1: {} + + html-void-elements@3.0.0: {} + + html-webpack-plugin@5.6.3(@rspack/core@1.1.6)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@types/html-minifier-terser': 6.1.0 + html-minifier-terser: 6.1.0 + lodash: 4.17.21 + pretty-error: 4.0.0 + tapable: 2.2.1 + optionalDependencies: + '@rspack/core': 1.1.6 + webpack: 5.97.1(@swc/core@1.10.1) + + htmlparser2@6.1.0: + dependencies: + domelementtype: 2.3.0 + domhandler: 4.3.1 + domutils: 2.8.0 + entities: 2.2.0 + + htmlparser2@8.0.2: + dependencies: + domelementtype: 2.3.0 + domhandler: 5.0.3 + domutils: 3.1.0 + entities: 4.5.0 + + htmlparser2@9.1.0: + dependencies: + domelementtype: 2.3.0 + domhandler: 5.0.3 + domutils: 3.1.0 + entities: 4.5.0 + + http-cache-semantics@4.1.1: {} + + http-deceiver@1.2.7: {} + + http-errors@1.6.3: + dependencies: + depd: 1.1.2 + inherits: 2.0.3 + setprototypeof: 1.1.0 + statuses: 1.5.0 + + http-errors@2.0.0: + dependencies: + depd: 2.0.0 + inherits: 2.0.4 + setprototypeof: 1.2.0 + statuses: 2.0.1 + toidentifier: 1.0.1 + + http-parser-js@0.5.8: {} + + http-proxy-middleware@2.0.7(@types/express@4.17.21): + dependencies: + '@types/http-proxy': 1.17.15 + http-proxy: 1.18.1 + is-glob: 4.0.3 + is-plain-obj: 3.0.0 + micromatch: 4.0.8 + optionalDependencies: + '@types/express': 4.17.21 + transitivePeerDependencies: + - debug + + http-proxy@1.18.1: + dependencies: + eventemitter3: 4.0.7 + follow-redirects: 1.15.9 + requires-port: 1.0.0 + transitivePeerDependencies: + - debug + + http2-wrapper@2.2.1: + dependencies: + quick-lru: 5.1.1 + resolve-alpn: 1.2.1 + + human-signals@2.1.0: {} + + iconv-lite@0.4.24: + dependencies: + safer-buffer: 2.1.2 + + iconv-lite@0.6.3: + dependencies: + safer-buffer: 2.1.2 + + icss-utils@5.1.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + ieee754@1.2.1: {} + + ignore@5.3.2: {} + + image-size@1.1.1: + dependencies: + queue: 6.0.2 + + immer@9.0.21: {} + + import-fresh@3.3.0: + dependencies: + parent-module: 1.0.1 + resolve-from: 4.0.0 + + import-lazy@4.0.0: {} + + imurmurhash@0.1.4: {} + + indent-string@4.0.0: {} + + infima@0.2.0-alpha.45: {} + + inflight@1.0.6: + dependencies: + once: 1.4.0 + wrappy: 1.0.2 + + inherits@2.0.3: {} + + inherits@2.0.4: {} + + ini@1.3.8: {} + + ini@2.0.0: {} + + inline-style-parser@0.1.1: {} + + inline-style-parser@0.2.4: {} + + interpret@1.4.0: {} + + invariant@2.2.4: + dependencies: + loose-envify: 1.4.0 + + ipaddr.js@1.9.1: {} + + ipaddr.js@2.2.0: {} + + is-alphabetical@2.0.1: {} + + is-alphanumerical@2.0.1: + dependencies: + is-alphabetical: 2.0.1 + is-decimal: 2.0.1 + + is-arrayish@0.2.1: {} + + is-arrayish@0.3.2: {} + + is-binary-path@2.1.0: + dependencies: + binary-extensions: 2.3.0 + + is-ci@3.0.1: + dependencies: + ci-info: 3.9.0 + + is-core-module@2.15.1: + dependencies: + hasown: 2.0.2 + + is-decimal@2.0.1: {} + + is-docker@2.2.1: {} + + is-extendable@0.1.1: {} + + is-extglob@2.1.1: {} + + is-fullwidth-code-point@3.0.0: {} + + is-glob@4.0.3: + dependencies: + is-extglob: 2.1.1 + + is-hexadecimal@2.0.1: {} + + is-installed-globally@0.4.0: + dependencies: + global-dirs: 3.0.1 + is-path-inside: 3.0.3 + + is-npm@6.0.0: {} + + is-number@7.0.0: {} + + is-obj@1.0.1: {} + + is-obj@2.0.0: {} + + is-path-cwd@2.2.0: {} + + is-path-inside@3.0.3: {} + + is-plain-obj@3.0.0: {} + + is-plain-obj@4.1.0: {} + + is-plain-object@2.0.4: + dependencies: + isobject: 3.0.1 + + is-regexp@1.0.0: {} + + is-root@2.1.0: {} + + is-stream@2.0.1: {} + + is-typedarray@1.0.0: {} + + is-wsl@2.2.0: + dependencies: + is-docker: 2.2.1 + + is-yarn-global@0.4.1: {} + + isarray@0.0.1: {} + + isarray@1.0.0: {} + + isexe@2.0.0: {} + + isobject@3.0.1: {} + + jest-util@29.7.0: + dependencies: + '@jest/types': 29.6.3 + '@types/node': 22.10.1 + chalk: 4.1.2 + ci-info: 3.9.0 + graceful-fs: 4.2.11 + picomatch: 2.3.1 + + jest-worker@27.5.1: + dependencies: + '@types/node': 22.10.1 + merge-stream: 2.0.0 + supports-color: 8.1.1 + + jest-worker@29.7.0: + dependencies: + '@types/node': 22.10.1 + jest-util: 29.7.0 + merge-stream: 2.0.0 + supports-color: 8.1.1 + + jiti@1.21.6: {} + + joi@17.13.3: + dependencies: + '@hapi/hoek': 9.3.0 + '@hapi/topo': 5.1.0 + '@sideway/address': 4.1.5 + '@sideway/formula': 3.0.1 + '@sideway/pinpoint': 2.0.0 + + js-tokens@4.0.0: {} + + js-yaml@3.14.1: + dependencies: + argparse: 1.0.10 + esprima: 4.0.1 + + js-yaml@4.1.0: + dependencies: + argparse: 2.0.1 + + jsesc@3.0.2: {} + + jsesc@3.1.0: {} + + json-buffer@3.0.1: {} + + json-parse-even-better-errors@2.3.1: {} + + json-schema-traverse@0.4.1: {} + + json-schema-traverse@1.0.0: {} + + json5@2.2.3: {} + + jsonfile@6.1.0: + dependencies: + universalify: 2.0.1 + optionalDependencies: + graceful-fs: 4.2.11 + + keyv@4.5.4: + dependencies: + json-buffer: 3.0.1 + + kind-of@6.0.3: {} + + kleur@3.0.3: {} + + latest-version@7.0.0: + dependencies: + package-json: 8.1.1 + + launch-editor@2.9.1: + dependencies: + picocolors: 1.1.1 + shell-quote: 1.8.2 + + leven@3.1.0: {} + + lightningcss-darwin-arm64@1.28.2: + optional: true + + lightningcss-darwin-x64@1.28.2: + optional: true + + lightningcss-freebsd-x64@1.28.2: + optional: true + + lightningcss-linux-arm-gnueabihf@1.28.2: + optional: true + + lightningcss-linux-arm64-gnu@1.28.2: + optional: true + + lightningcss-linux-arm64-musl@1.28.2: + optional: true + + lightningcss-linux-x64-gnu@1.28.2: + optional: true + + lightningcss-linux-x64-musl@1.28.2: + optional: true + + lightningcss-win32-arm64-msvc@1.28.2: + optional: true + + lightningcss-win32-x64-msvc@1.28.2: + optional: true + + lightningcss@1.28.2: + dependencies: + detect-libc: 1.0.3 + optionalDependencies: + lightningcss-darwin-arm64: 1.28.2 + lightningcss-darwin-x64: 1.28.2 + lightningcss-freebsd-x64: 1.28.2 + lightningcss-linux-arm-gnueabihf: 1.28.2 + lightningcss-linux-arm64-gnu: 1.28.2 + lightningcss-linux-arm64-musl: 1.28.2 + lightningcss-linux-x64-gnu: 1.28.2 + lightningcss-linux-x64-musl: 1.28.2 + lightningcss-win32-arm64-msvc: 1.28.2 + lightningcss-win32-x64-msvc: 1.28.2 + + lilconfig@3.1.3: {} + + lines-and-columns@1.2.4: {} + + loader-runner@4.3.0: {} + + loader-utils@2.0.4: + dependencies: + big.js: 5.2.2 + emojis-list: 3.0.0 + json5: 2.2.3 + + loader-utils@3.3.1: {} + + locate-path@3.0.0: + dependencies: + p-locate: 3.0.0 + path-exists: 3.0.0 + + locate-path@6.0.0: + dependencies: + p-locate: 5.0.0 + + locate-path@7.2.0: + dependencies: + p-locate: 6.0.0 + + lodash.debounce@4.0.8: {} + + lodash.memoize@4.1.2: {} + + lodash.uniq@4.5.0: {} + + lodash@4.17.21: {} + + longest-streak@3.1.0: {} + + loose-envify@1.4.0: + dependencies: + js-tokens: 4.0.0 + + lower-case@2.0.2: + dependencies: + tslib: 2.8.1 + + lowercase-keys@3.0.0: {} + + lru-cache@5.1.1: + dependencies: + yallist: 3.1.1 + + lunr-languages@1.14.0: {} + + mark.js@8.11.1: {} + + markdown-extensions@2.0.0: {} + + markdown-table@2.0.0: + dependencies: + repeat-string: 1.6.1 + + markdown-table@3.0.4: {} + + mdast-util-directive@3.0.0: + dependencies: + '@types/mdast': 4.0.4 + '@types/unist': 3.0.3 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + parse-entities: 4.0.1 + stringify-entities: 4.0.4 + unist-util-visit-parents: 6.0.1 + transitivePeerDependencies: + - supports-color + + mdast-util-find-and-replace@3.0.1: + dependencies: + '@types/mdast': 4.0.4 + escape-string-regexp: 5.0.0 + unist-util-is: 6.0.0 + unist-util-visit-parents: 6.0.1 + + mdast-util-from-markdown@2.0.2: + dependencies: + '@types/mdast': 4.0.4 + '@types/unist': 3.0.3 + decode-named-character-reference: 1.0.2 + devlop: 1.1.0 + mdast-util-to-string: 4.0.0 + micromark: 4.0.1 + micromark-util-decode-numeric-character-reference: 2.0.2 + micromark-util-decode-string: 2.0.1 + micromark-util-normalize-identifier: 2.0.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + unist-util-stringify-position: 4.0.0 + transitivePeerDependencies: + - supports-color + + mdast-util-frontmatter@2.0.1: + dependencies: + '@types/mdast': 4.0.4 + devlop: 1.1.0 + escape-string-regexp: 5.0.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + micromark-extension-frontmatter: 2.0.0 + transitivePeerDependencies: + - supports-color + + mdast-util-gfm-autolink-literal@2.0.1: + dependencies: + '@types/mdast': 4.0.4 + ccount: 2.0.1 + devlop: 1.1.0 + mdast-util-find-and-replace: 3.0.1 + micromark-util-character: 2.1.1 + + mdast-util-gfm-footnote@2.0.0: + dependencies: + '@types/mdast': 4.0.4 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + micromark-util-normalize-identifier: 2.0.1 + transitivePeerDependencies: + - supports-color + + mdast-util-gfm-strikethrough@2.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-gfm-table@2.0.0: + dependencies: + '@types/mdast': 4.0.4 + devlop: 1.1.0 + markdown-table: 3.0.4 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-gfm-task-list-item@2.0.0: + dependencies: + '@types/mdast': 4.0.4 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-gfm@3.0.0: + dependencies: + mdast-util-from-markdown: 2.0.2 + mdast-util-gfm-autolink-literal: 2.0.1 + mdast-util-gfm-footnote: 2.0.0 + mdast-util-gfm-strikethrough: 2.0.0 + mdast-util-gfm-table: 2.0.0 + mdast-util-gfm-task-list-item: 2.0.0 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-mdx-expression@2.0.1: + dependencies: + '@types/estree-jsx': 1.0.5 + '@types/hast': 3.0.4 + '@types/mdast': 4.0.4 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-mdx-jsx@3.1.3: + dependencies: + '@types/estree-jsx': 1.0.5 + '@types/hast': 3.0.4 + '@types/mdast': 4.0.4 + '@types/unist': 3.0.3 + ccount: 2.0.1 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + parse-entities: 4.0.1 + stringify-entities: 4.0.4 + unist-util-stringify-position: 4.0.0 + vfile-message: 4.0.2 + transitivePeerDependencies: + - supports-color + + mdast-util-mdx@3.0.0: + dependencies: + mdast-util-from-markdown: 2.0.2 + mdast-util-mdx-expression: 2.0.1 + mdast-util-mdx-jsx: 3.1.3 + mdast-util-mdxjs-esm: 2.0.1 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-mdxjs-esm@2.0.1: + dependencies: + '@types/estree-jsx': 1.0.5 + '@types/hast': 3.0.4 + '@types/mdast': 4.0.4 + devlop: 1.1.0 + mdast-util-from-markdown: 2.0.2 + mdast-util-to-markdown: 2.1.2 + transitivePeerDependencies: + - supports-color + + mdast-util-phrasing@4.1.0: + dependencies: + '@types/mdast': 4.0.4 + unist-util-is: 6.0.0 + + mdast-util-to-hast@13.2.0: + dependencies: + '@types/hast': 3.0.4 + '@types/mdast': 4.0.4 + '@ungap/structured-clone': 1.2.1 + devlop: 1.1.0 + micromark-util-sanitize-uri: 2.0.1 + trim-lines: 3.0.1 + unist-util-position: 5.0.0 + unist-util-visit: 5.0.0 + vfile: 6.0.3 + + mdast-util-to-markdown@2.1.2: + dependencies: + '@types/mdast': 4.0.4 + '@types/unist': 3.0.3 + longest-streak: 3.1.0 + mdast-util-phrasing: 4.1.0 + mdast-util-to-string: 4.0.0 + micromark-util-classify-character: 2.0.1 + micromark-util-decode-string: 2.0.1 + unist-util-visit: 5.0.0 + zwitch: 2.0.4 + + mdast-util-to-string@4.0.0: + dependencies: + '@types/mdast': 4.0.4 + + mdn-data@2.0.28: {} + + mdn-data@2.0.30: {} + + media-typer@0.3.0: {} + + medium-zoom@1.1.0: {} + + memfs@3.5.3: + dependencies: + fs-monkey: 1.0.6 + + merge-descriptors@1.0.3: {} + + merge-stream@2.0.0: {} + + merge2@1.4.1: {} + + methods@1.1.2: {} + + micromark-core-commonmark@2.0.2: + dependencies: + decode-named-character-reference: 1.0.2 + devlop: 1.1.0 + micromark-factory-destination: 2.0.1 + micromark-factory-label: 2.0.1 + micromark-factory-space: 2.0.1 + micromark-factory-title: 2.0.1 + micromark-factory-whitespace: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-chunked: 2.0.1 + micromark-util-classify-character: 2.0.1 + micromark-util-html-tag-name: 2.0.1 + micromark-util-normalize-identifier: 2.0.1 + micromark-util-resolve-all: 2.0.1 + micromark-util-subtokenize: 2.0.3 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-directive@3.0.2: + dependencies: + devlop: 1.1.0 + micromark-factory-space: 2.0.1 + micromark-factory-whitespace: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + parse-entities: 4.0.1 + + micromark-extension-frontmatter@2.0.0: + dependencies: + fault: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm-autolink-literal@2.1.0: + dependencies: + micromark-util-character: 2.1.1 + micromark-util-sanitize-uri: 2.0.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm-footnote@2.1.0: + dependencies: + devlop: 1.1.0 + micromark-core-commonmark: 2.0.2 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-normalize-identifier: 2.0.1 + micromark-util-sanitize-uri: 2.0.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm-strikethrough@2.1.0: + dependencies: + devlop: 1.1.0 + micromark-util-chunked: 2.0.1 + micromark-util-classify-character: 2.0.1 + micromark-util-resolve-all: 2.0.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm-table@2.1.0: + dependencies: + devlop: 1.1.0 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm-tagfilter@2.0.0: + dependencies: + micromark-util-types: 2.0.1 + + micromark-extension-gfm-task-list-item@2.1.0: + dependencies: + devlop: 1.1.0 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-gfm@3.0.0: + dependencies: + micromark-extension-gfm-autolink-literal: 2.1.0 + micromark-extension-gfm-footnote: 2.1.0 + micromark-extension-gfm-strikethrough: 2.1.0 + micromark-extension-gfm-table: 2.1.0 + micromark-extension-gfm-tagfilter: 2.0.0 + micromark-extension-gfm-task-list-item: 2.1.0 + micromark-util-combine-extensions: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-mdx-expression@3.0.0: + dependencies: + '@types/estree': 1.0.6 + devlop: 1.1.0 + micromark-factory-mdx-expression: 2.0.2 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-events-to-acorn: 2.0.2 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-extension-mdx-jsx@3.0.1: + dependencies: + '@types/acorn': 4.0.6 + '@types/estree': 1.0.6 + devlop: 1.1.0 + estree-util-is-identifier-name: 3.0.0 + micromark-factory-mdx-expression: 2.0.2 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-events-to-acorn: 2.0.2 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + vfile-message: 4.0.2 + + micromark-extension-mdx-md@2.0.0: + dependencies: + micromark-util-types: 2.0.1 + + micromark-extension-mdxjs-esm@3.0.0: + dependencies: + '@types/estree': 1.0.6 + devlop: 1.1.0 + micromark-core-commonmark: 2.0.2 + micromark-util-character: 2.1.1 + micromark-util-events-to-acorn: 2.0.2 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + unist-util-position-from-estree: 2.0.0 + vfile-message: 4.0.2 + + micromark-extension-mdxjs@3.0.0: + dependencies: + acorn: 8.14.0 + acorn-jsx: 5.3.2(acorn@8.14.0) + micromark-extension-mdx-expression: 3.0.0 + micromark-extension-mdx-jsx: 3.0.1 + micromark-extension-mdx-md: 2.0.0 + micromark-extension-mdxjs-esm: 3.0.0 + micromark-util-combine-extensions: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-factory-destination@2.0.1: + dependencies: + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-factory-label@2.0.1: + dependencies: + devlop: 1.1.0 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-factory-mdx-expression@2.0.2: + dependencies: + '@types/estree': 1.0.6 + devlop: 1.1.0 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-events-to-acorn: 2.0.2 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + unist-util-position-from-estree: 2.0.0 + vfile-message: 4.0.2 + + micromark-factory-space@1.1.0: + dependencies: + micromark-util-character: 1.2.0 + micromark-util-types: 1.1.0 + + micromark-factory-space@2.0.1: + dependencies: + micromark-util-character: 2.1.1 + micromark-util-types: 2.0.1 + + micromark-factory-title@2.0.1: + dependencies: + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-factory-whitespace@2.0.1: + dependencies: + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-util-character@1.2.0: + dependencies: + micromark-util-symbol: 1.1.0 + micromark-util-types: 1.1.0 + + micromark-util-character@2.1.1: + dependencies: + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-util-chunked@2.0.1: + dependencies: + micromark-util-symbol: 2.0.1 + + micromark-util-classify-character@2.0.1: + dependencies: + micromark-util-character: 2.1.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-util-combine-extensions@2.0.1: + dependencies: + micromark-util-chunked: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-util-decode-numeric-character-reference@2.0.2: + dependencies: + micromark-util-symbol: 2.0.1 + + micromark-util-decode-string@2.0.1: + dependencies: + decode-named-character-reference: 1.0.2 + micromark-util-character: 2.1.1 + micromark-util-decode-numeric-character-reference: 2.0.2 + micromark-util-symbol: 2.0.1 + + micromark-util-encode@2.0.1: {} + + micromark-util-events-to-acorn@2.0.2: + dependencies: + '@types/acorn': 4.0.6 + '@types/estree': 1.0.6 + '@types/unist': 3.0.3 + devlop: 1.1.0 + estree-util-visit: 2.0.0 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + vfile-message: 4.0.2 + + micromark-util-html-tag-name@2.0.1: {} + + micromark-util-normalize-identifier@2.0.1: + dependencies: + micromark-util-symbol: 2.0.1 + + micromark-util-resolve-all@2.0.1: + dependencies: + micromark-util-types: 2.0.1 + + micromark-util-sanitize-uri@2.0.1: + dependencies: + micromark-util-character: 2.1.1 + micromark-util-encode: 2.0.1 + micromark-util-symbol: 2.0.1 + + micromark-util-subtokenize@2.0.3: + dependencies: + devlop: 1.1.0 + micromark-util-chunked: 2.0.1 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + + micromark-util-symbol@1.1.0: {} + + micromark-util-symbol@2.0.1: {} + + micromark-util-types@1.1.0: {} + + micromark-util-types@2.0.1: {} + + micromark@4.0.1: + dependencies: + '@types/debug': 4.1.12 + debug: 4.4.0 + decode-named-character-reference: 1.0.2 + devlop: 1.1.0 + micromark-core-commonmark: 2.0.2 + micromark-factory-space: 2.0.1 + micromark-util-character: 2.1.1 + micromark-util-chunked: 2.0.1 + micromark-util-combine-extensions: 2.0.1 + micromark-util-decode-numeric-character-reference: 2.0.2 + micromark-util-encode: 2.0.1 + micromark-util-normalize-identifier: 2.0.1 + micromark-util-resolve-all: 2.0.1 + micromark-util-sanitize-uri: 2.0.1 + micromark-util-subtokenize: 2.0.3 + micromark-util-symbol: 2.0.1 + micromark-util-types: 2.0.1 + transitivePeerDependencies: + - supports-color + + micromatch@4.0.8: + dependencies: + braces: 3.0.3 + picomatch: 2.3.1 + + mime-db@1.33.0: {} + + mime-db@1.52.0: {} + + mime-db@1.53.0: {} + + mime-types@2.1.18: + dependencies: + mime-db: 1.33.0 + + mime-types@2.1.35: + dependencies: + mime-db: 1.52.0 + + mime@1.6.0: {} + + mimic-fn@2.1.0: {} + + mimic-response@3.1.0: {} + + mimic-response@4.0.0: {} + + mini-css-extract-plugin@2.9.2(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + schema-utils: 4.2.0 + tapable: 2.2.1 + webpack: 5.97.1(@swc/core@1.10.1) + + minimalistic-assert@1.0.1: {} + + minimatch@3.1.2: + dependencies: + brace-expansion: 1.1.11 + + minimist@1.2.8: {} + + mkdirp-classic@0.5.3: {} + + mrmime@2.0.0: {} + + ms@2.0.0: {} + + ms@2.1.3: {} + + multicast-dns@7.2.5: + dependencies: + dns-packet: 5.6.1 + thunky: 1.1.0 + + nanoid@3.3.8: {} + + napi-build-utils@1.0.2: {} + + negotiator@0.6.3: {} + + negotiator@0.6.4: {} + + neo-async@2.6.2: {} + + no-case@3.0.4: + dependencies: + lower-case: 2.0.2 + tslib: 2.8.1 + + node-abi@3.71.0: + dependencies: + semver: 7.6.3 + + node-addon-api@6.1.0: {} + + node-emoji@2.2.0: + dependencies: + '@sindresorhus/is': 4.6.0 + char-regex: 1.0.2 + emojilib: 2.4.0 + skin-tone: 2.0.0 + + node-forge@1.3.1: {} + + node-releases@2.0.19: {} + + normalize-path@3.0.0: {} + + normalize-range@0.1.2: {} + + normalize-url@8.0.1: {} + + npm-run-path@4.0.1: + dependencies: + path-key: 3.1.1 + + nprogress@0.2.0: {} + + nth-check@2.1.1: + dependencies: + boolbase: 1.0.0 + + null-loader@4.0.1(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + loader-utils: 2.0.4 + schema-utils: 3.3.0 + webpack: 5.97.1(@swc/core@1.10.1) + + object-assign@4.1.1: {} + + object-inspect@1.13.3: {} + + object-keys@1.1.1: {} + + object.assign@4.1.5: + dependencies: + call-bind: 1.0.8 + define-properties: 1.2.1 + has-symbols: 1.1.0 + object-keys: 1.1.1 + + obuf@1.1.2: {} + + on-finished@2.4.1: + dependencies: + ee-first: 1.1.1 + + on-headers@1.0.2: {} + + once@1.4.0: + dependencies: + wrappy: 1.0.2 + + onetime@5.1.2: + dependencies: + mimic-fn: 2.1.0 + + open@8.4.2: + dependencies: + define-lazy-prop: 2.0.0 + is-docker: 2.2.1 + is-wsl: 2.2.0 + + opener@1.5.2: {} + + p-cancelable@3.0.0: {} + + p-limit@2.3.0: + dependencies: + p-try: 2.2.0 + + p-limit@3.1.0: + dependencies: + yocto-queue: 0.1.0 + + p-limit@4.0.0: + dependencies: + yocto-queue: 1.1.1 + + p-locate@3.0.0: + dependencies: + p-limit: 2.3.0 + + p-locate@5.0.0: + dependencies: + p-limit: 3.1.0 + + p-locate@6.0.0: + dependencies: + p-limit: 4.0.0 + + p-map@4.0.0: + dependencies: + aggregate-error: 3.1.0 + + p-retry@4.6.2: + dependencies: + '@types/retry': 0.12.0 + retry: 0.13.1 + + p-try@2.2.0: {} + + package-json@8.1.1: + dependencies: + got: 12.6.1 + registry-auth-token: 5.0.3 + registry-url: 6.0.1 + semver: 7.6.3 + + param-case@3.0.4: + dependencies: + dot-case: 3.0.4 + tslib: 2.8.1 + + parent-module@1.0.1: + dependencies: + callsites: 3.1.0 + + parse-entities@4.0.1: + dependencies: + '@types/unist': 2.0.11 + character-entities: 2.0.2 + character-entities-legacy: 3.0.0 + character-reference-invalid: 2.0.1 + decode-named-character-reference: 1.0.2 + is-alphanumerical: 2.0.1 + is-decimal: 2.0.1 + is-hexadecimal: 2.0.1 + + parse-json@5.2.0: + dependencies: + '@babel/code-frame': 7.26.2 + error-ex: 1.3.2 + json-parse-even-better-errors: 2.3.1 + lines-and-columns: 1.2.4 + + parse-numeric-range@1.3.0: {} + + parse5-htmlparser2-tree-adapter@7.1.0: + dependencies: + domhandler: 5.0.3 + parse5: 7.2.1 + + parse5-parser-stream@7.1.2: + dependencies: + parse5: 7.2.1 + + parse5@7.2.1: + dependencies: + entities: 4.5.0 + + parseurl@1.3.3: {} + + pascal-case@3.1.2: + dependencies: + no-case: 3.0.4 + tslib: 2.8.1 + + path-exists@3.0.0: {} + + path-exists@4.0.0: {} + + path-exists@5.0.0: {} + + path-is-absolute@1.0.1: {} + + path-is-inside@1.0.2: {} + + path-key@3.1.1: {} + + path-parse@1.0.7: {} + + path-root-regex@0.1.2: {} + + path-root@0.1.1: + dependencies: + path-root-regex: 0.1.2 + + path-to-regexp@0.1.12: {} + + path-to-regexp@1.9.0: + dependencies: + isarray: 0.0.1 + + path-to-regexp@3.3.0: {} + + path-type@4.0.0: {} + + picocolors@1.1.1: {} + + picomatch@2.3.1: {} + + pkg-dir@7.0.0: + dependencies: + find-up: 6.3.0 + + pkg-up@3.1.0: + dependencies: + find-up: 3.0.0 + + postcss-attribute-case-insensitive@7.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-calc@9.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + postcss-value-parser: 4.2.0 + + postcss-clamp@4.1.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-color-functional-notation@7.0.6(postcss@8.4.49): + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + postcss-color-hex-alpha@10.0.0(postcss@8.4.49): + dependencies: + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-color-rebeccapurple@10.0.0(postcss@8.4.49): + dependencies: + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-colormin@6.1.0(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + caniuse-api: 3.0.0 + colord: 2.9.3 + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-convert-values@6.1.0(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-custom-media@11.0.5(postcss@8.4.49): + dependencies: + '@csstools/cascade-layer-name-parser': 2.0.4(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/media-query-list-parser': 4.0.2(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + postcss: 8.4.49 + + postcss-custom-properties@14.0.4(postcss@8.4.49): + dependencies: + '@csstools/cascade-layer-name-parser': 2.0.4(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-custom-selectors@8.0.4(postcss@8.4.49): + dependencies: + '@csstools/cascade-layer-name-parser': 2.0.4(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-dir-pseudo-class@9.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-discard-comments@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-discard-duplicates@6.0.3(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-discard-empty@6.0.3(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-discard-overridden@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-discard-unused@6.0.5(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + + postcss-double-position-gradients@6.0.0(postcss@8.4.49): + dependencies: + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-focus-visible@10.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-focus-within@9.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-font-variant@5.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-gap-properties@6.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-image-set-function@7.0.0(postcss@8.4.49): + dependencies: + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-lab-function@7.0.6(postcss@8.4.49): + dependencies: + '@csstools/css-color-parser': 3.0.6(@csstools/css-parser-algorithms@3.0.4(@csstools/css-tokenizer@3.0.3))(@csstools/css-tokenizer@3.0.3) + '@csstools/css-parser-algorithms': 3.0.4(@csstools/css-tokenizer@3.0.3) + '@csstools/css-tokenizer': 3.0.3 + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/utilities': 2.0.0(postcss@8.4.49) + postcss: 8.4.49 + + postcss-loader@7.3.4(postcss@8.4.49)(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + cosmiconfig: 8.3.6(typescript@5.7.2) + jiti: 1.21.6 + postcss: 8.4.49 + semver: 7.6.3 + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - typescript + + postcss-logical@8.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-merge-idents@6.0.3(postcss@8.4.49): + dependencies: + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-merge-longhand@6.0.5(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + stylehacks: 6.1.1(postcss@8.4.49) + + postcss-merge-rules@6.1.1(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + caniuse-api: 3.0.0 + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + + postcss-minify-font-values@6.1.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-minify-gradients@6.0.3(postcss@8.4.49): + dependencies: + colord: 2.9.3 + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-minify-params@6.1.0(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-minify-selectors@6.0.4(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + + postcss-modules-extract-imports@3.1.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-modules-local-by-default@4.1.0(postcss@8.4.49): + dependencies: + icss-utils: 5.1.0(postcss@8.4.49) + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + postcss-value-parser: 4.2.0 + + postcss-modules-scope@3.2.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-modules-values@4.0.0(postcss@8.4.49): + dependencies: + icss-utils: 5.1.0(postcss@8.4.49) + postcss: 8.4.49 + + postcss-nesting@13.0.1(postcss@8.4.49): + dependencies: + '@csstools/selector-resolve-nested': 3.0.0(postcss-selector-parser@7.0.0) + '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.0.0) + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-normalize-charset@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-normalize-display-values@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-positions@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-repeat-style@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-string@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-timing-functions@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-unicode@6.1.0(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-url@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-normalize-whitespace@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-opacity-percentage@3.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-ordered-values@6.0.2(postcss@8.4.49): + dependencies: + cssnano-utils: 4.0.2(postcss@8.4.49) + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-overflow-shorthand@6.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-page-break@3.0.4(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-place@10.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-preset-env@10.1.1(postcss@8.4.49): + dependencies: + '@csstools/postcss-cascade-layers': 5.0.1(postcss@8.4.49) + '@csstools/postcss-color-function': 4.0.6(postcss@8.4.49) + '@csstools/postcss-color-mix-function': 3.0.6(postcss@8.4.49) + '@csstools/postcss-content-alt-text': 2.0.4(postcss@8.4.49) + '@csstools/postcss-exponential-functions': 2.0.5(postcss@8.4.49) + '@csstools/postcss-font-format-keywords': 4.0.0(postcss@8.4.49) + '@csstools/postcss-gamut-mapping': 2.0.6(postcss@8.4.49) + '@csstools/postcss-gradients-interpolation-method': 5.0.6(postcss@8.4.49) + '@csstools/postcss-hwb-function': 4.0.6(postcss@8.4.49) + '@csstools/postcss-ic-unit': 4.0.0(postcss@8.4.49) + '@csstools/postcss-initial': 2.0.0(postcss@8.4.49) + '@csstools/postcss-is-pseudo-class': 5.0.1(postcss@8.4.49) + '@csstools/postcss-light-dark-function': 2.0.7(postcss@8.4.49) + '@csstools/postcss-logical-float-and-clear': 3.0.0(postcss@8.4.49) + '@csstools/postcss-logical-overflow': 2.0.0(postcss@8.4.49) + '@csstools/postcss-logical-overscroll-behavior': 2.0.0(postcss@8.4.49) + '@csstools/postcss-logical-resize': 3.0.0(postcss@8.4.49) + '@csstools/postcss-logical-viewport-units': 3.0.3(postcss@8.4.49) + '@csstools/postcss-media-minmax': 2.0.5(postcss@8.4.49) + '@csstools/postcss-media-queries-aspect-ratio-number-values': 3.0.4(postcss@8.4.49) + '@csstools/postcss-nested-calc': 4.0.0(postcss@8.4.49) + '@csstools/postcss-normalize-display-values': 4.0.0(postcss@8.4.49) + '@csstools/postcss-oklab-function': 4.0.6(postcss@8.4.49) + '@csstools/postcss-progressive-custom-properties': 4.0.0(postcss@8.4.49) + '@csstools/postcss-random-function': 1.0.1(postcss@8.4.49) + '@csstools/postcss-relative-color-syntax': 3.0.6(postcss@8.4.49) + '@csstools/postcss-scope-pseudo-class': 4.0.1(postcss@8.4.49) + '@csstools/postcss-sign-functions': 1.1.0(postcss@8.4.49) + '@csstools/postcss-stepped-value-functions': 4.0.5(postcss@8.4.49) + '@csstools/postcss-text-decoration-shorthand': 4.0.1(postcss@8.4.49) + '@csstools/postcss-trigonometric-functions': 4.0.5(postcss@8.4.49) + '@csstools/postcss-unset-value': 4.0.0(postcss@8.4.49) + autoprefixer: 10.4.20(postcss@8.4.49) + browserslist: 4.24.2 + css-blank-pseudo: 7.0.1(postcss@8.4.49) + css-has-pseudo: 7.0.1(postcss@8.4.49) + css-prefers-color-scheme: 10.0.0(postcss@8.4.49) + cssdb: 8.2.3 + postcss: 8.4.49 + postcss-attribute-case-insensitive: 7.0.1(postcss@8.4.49) + postcss-clamp: 4.1.0(postcss@8.4.49) + postcss-color-functional-notation: 7.0.6(postcss@8.4.49) + postcss-color-hex-alpha: 10.0.0(postcss@8.4.49) + postcss-color-rebeccapurple: 10.0.0(postcss@8.4.49) + postcss-custom-media: 11.0.5(postcss@8.4.49) + postcss-custom-properties: 14.0.4(postcss@8.4.49) + postcss-custom-selectors: 8.0.4(postcss@8.4.49) + postcss-dir-pseudo-class: 9.0.1(postcss@8.4.49) + postcss-double-position-gradients: 6.0.0(postcss@8.4.49) + postcss-focus-visible: 10.0.1(postcss@8.4.49) + postcss-focus-within: 9.0.1(postcss@8.4.49) + postcss-font-variant: 5.0.0(postcss@8.4.49) + postcss-gap-properties: 6.0.0(postcss@8.4.49) + postcss-image-set-function: 7.0.0(postcss@8.4.49) + postcss-lab-function: 7.0.6(postcss@8.4.49) + postcss-logical: 8.0.0(postcss@8.4.49) + postcss-nesting: 13.0.1(postcss@8.4.49) + postcss-opacity-percentage: 3.0.0(postcss@8.4.49) + postcss-overflow-shorthand: 6.0.0(postcss@8.4.49) + postcss-page-break: 3.0.4(postcss@8.4.49) + postcss-place: 10.0.0(postcss@8.4.49) + postcss-pseudo-class-any-link: 10.0.1(postcss@8.4.49) + postcss-replace-overflow-wrap: 4.0.0(postcss@8.4.49) + postcss-selector-not: 8.0.1(postcss@8.4.49) + + postcss-pseudo-class-any-link@10.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-reduce-idents@6.0.3(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-reduce-initial@6.1.0(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + caniuse-api: 3.0.0 + postcss: 8.4.49 + + postcss-reduce-transforms@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + + postcss-replace-overflow-wrap@4.0.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss-selector-not@8.0.1(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 7.0.0 + + postcss-selector-parser@6.1.2: + dependencies: + cssesc: 3.0.0 + util-deprecate: 1.0.2 + + postcss-selector-parser@7.0.0: + dependencies: + cssesc: 3.0.0 + util-deprecate: 1.0.2 + + postcss-sort-media-queries@5.2.0(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + sort-css-media-queries: 2.2.0 + + postcss-svgo@6.0.3(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-value-parser: 4.2.0 + svgo: 3.3.2 + + postcss-unique-selectors@6.0.4(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + + postcss-value-parser@4.2.0: {} + + postcss-zindex@6.0.2(postcss@8.4.49): + dependencies: + postcss: 8.4.49 + + postcss@8.4.49: + dependencies: + nanoid: 3.3.8 + picocolors: 1.1.1 + source-map-js: 1.2.1 + + preact@10.25.1: {} + + prebuild-install@7.1.2: + dependencies: + detect-libc: 2.0.3 + expand-template: 2.0.3 + github-from-package: 0.0.0 + minimist: 1.2.8 + mkdirp-classic: 0.5.3 + napi-build-utils: 1.0.2 + node-abi: 3.71.0 + pump: 3.0.2 + rc: 1.2.8 + simple-get: 4.0.1 + tar-fs: 2.1.1 + tunnel-agent: 0.6.0 + + pretty-error@4.0.0: + dependencies: + lodash: 4.17.21 + renderkid: 3.0.0 + + pretty-time@1.1.0: {} + + prism-react-renderer@2.4.0(react@18.3.1): + dependencies: + '@types/prismjs': 1.26.5 + clsx: 2.1.1 + react: 18.3.1 + + prismjs@1.29.0: {} + + process-nextick-args@2.0.1: {} + + prompts@2.4.2: + dependencies: + kleur: 3.0.3 + sisteransi: 1.0.5 + + prop-types@15.8.1: + dependencies: + loose-envify: 1.4.0 + object-assign: 4.1.1 + react-is: 16.13.1 + + property-information@6.5.0: {} + + proto-list@1.2.4: {} + + proxy-addr@2.0.7: + dependencies: + forwarded: 0.2.0 + ipaddr.js: 1.9.1 + + pump@3.0.2: + dependencies: + end-of-stream: 1.4.4 + once: 1.4.0 + + punycode@2.3.1: {} + + pupa@3.1.0: + dependencies: + escape-goat: 4.0.0 + + qs@6.13.0: + dependencies: + side-channel: 1.0.6 + + queue-microtask@1.2.3: {} + + queue-tick@1.0.1: {} + + queue@6.0.2: + dependencies: + inherits: 2.0.4 + + quick-lru@5.1.1: {} + + randombytes@2.1.0: + dependencies: + safe-buffer: 5.2.1 + + range-parser@1.2.0: {} + + range-parser@1.2.1: {} + + raw-body@2.5.2: + dependencies: + bytes: 3.1.2 + http-errors: 2.0.0 + iconv-lite: 0.4.24 + unpipe: 1.0.0 + + rc@1.2.8: + dependencies: + deep-extend: 0.6.0 + ini: 1.3.8 + minimist: 1.2.8 + strip-json-comments: 2.0.1 + + react-dev-utils@12.0.1(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@babel/code-frame': 7.26.2 + address: 1.2.2 + browserslist: 4.24.2 + chalk: 4.1.2 + cross-spawn: 7.0.6 + detect-port-alt: 1.1.6 + escape-string-regexp: 4.0.0 + filesize: 8.0.7 + find-up: 5.0.0 + fork-ts-checker-webpack-plugin: 6.5.3(typescript@5.7.2)(webpack@5.97.1(@swc/core@1.10.1)) + global-modules: 2.0.0 + globby: 11.1.0 + gzip-size: 6.0.0 + immer: 9.0.21 + is-root: 2.1.0 + loader-utils: 3.3.1 + open: 8.4.2 + pkg-up: 3.1.0 + prompts: 2.4.2 + react-error-overlay: 6.0.11 + recursive-readdir: 2.2.3 + shell-quote: 1.8.2 + strip-ansi: 6.0.1 + text-table: 0.2.0 + webpack: 5.97.1(@swc/core@1.10.1) + optionalDependencies: + typescript: 5.7.2 + transitivePeerDependencies: + - eslint + - supports-color + - vue-template-compiler + + react-dom@18.3.1(react@18.3.1): + dependencies: + loose-envify: 1.4.0 + react: 18.3.1 + scheduler: 0.23.2 + + react-error-overlay@6.0.11: {} + + react-fast-compare@3.2.2: {} + + react-helmet-async@1.3.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1): + dependencies: + '@babel/runtime': 7.26.0 + invariant: 2.2.4 + prop-types: 15.8.1 + react: 18.3.1 + react-dom: 18.3.1(react@18.3.1) + react-fast-compare: 3.2.2 + shallowequal: 1.1.0 + + react-helmet-async@2.0.5(react@18.3.1): + dependencies: + invariant: 2.2.4 + react: 18.3.1 + react-fast-compare: 3.2.2 + shallowequal: 1.1.0 + + react-is@16.13.1: {} + + react-is@18.3.1: {} + + react-json-view-lite@1.5.0(react@18.3.1): + dependencies: + react: 18.3.1 + + react-loadable-ssr-addon-v5-slorber@1.0.1(@docusaurus/react-loadable@6.0.0(react@18.3.1))(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@babel/runtime': 7.26.0 + react-loadable: '@docusaurus/react-loadable@6.0.0(react@18.3.1)' + webpack: 5.97.1(@swc/core@1.10.1) + + react-router-config@5.1.1(react-router@5.3.4(react@18.3.1))(react@18.3.1): + dependencies: + '@babel/runtime': 7.26.0 + react: 18.3.1 + react-router: 5.3.4(react@18.3.1) + + react-router-dom@5.3.4(react@18.3.1): + dependencies: + '@babel/runtime': 7.26.0 + history: 4.10.1 + loose-envify: 1.4.0 + prop-types: 15.8.1 + react: 18.3.1 + react-router: 5.3.4(react@18.3.1) + tiny-invariant: 1.3.3 + tiny-warning: 1.0.3 + + react-router@5.3.4(react@18.3.1): + dependencies: + '@babel/runtime': 7.26.0 + history: 4.10.1 + hoist-non-react-statics: 3.3.2 + loose-envify: 1.4.0 + path-to-regexp: 1.9.0 + prop-types: 15.8.1 + react: 18.3.1 + react-is: 16.13.1 + tiny-invariant: 1.3.3 + tiny-warning: 1.0.3 + + react-waypoint@10.3.0(react@18.3.1): + dependencies: + '@babel/runtime': 7.26.0 + consolidated-events: 2.0.2 + prop-types: 15.8.1 + react: 18.3.1 + react-is: 18.3.1 + + react@18.3.1: + dependencies: + loose-envify: 1.4.0 + + readable-stream@2.3.8: + dependencies: + core-util-is: 1.0.3 + inherits: 2.0.4 + isarray: 1.0.0 + process-nextick-args: 2.0.1 + safe-buffer: 5.1.2 + string_decoder: 1.1.1 + util-deprecate: 1.0.2 + + readable-stream@3.6.2: + dependencies: + inherits: 2.0.4 + string_decoder: 1.3.0 + util-deprecate: 1.0.2 + + readdirp@3.6.0: + dependencies: + picomatch: 2.3.1 + + reading-time@1.5.0: {} + + rechoir@0.6.2: + dependencies: + resolve: 1.22.8 + + recma-build-jsx@1.0.0: + dependencies: + '@types/estree': 1.0.6 + estree-util-build-jsx: 3.0.1 + vfile: 6.0.3 + + recma-jsx@1.0.0(acorn@8.14.0): + dependencies: + acorn-jsx: 5.3.2(acorn@8.14.0) + estree-util-to-js: 2.0.0 + recma-parse: 1.0.0 + recma-stringify: 1.0.0 + unified: 11.0.5 + transitivePeerDependencies: + - acorn + + recma-parse@1.0.0: + dependencies: + '@types/estree': 1.0.6 + esast-util-from-js: 2.0.1 + unified: 11.0.5 + vfile: 6.0.3 + + recma-stringify@1.0.0: + dependencies: + '@types/estree': 1.0.6 + estree-util-to-js: 2.0.0 + unified: 11.0.5 + vfile: 6.0.3 + + recursive-readdir@2.2.3: + dependencies: + minimatch: 3.1.2 + + regenerate-unicode-properties@10.2.0: + dependencies: + regenerate: 1.4.2 + + regenerate@1.4.2: {} + + regenerator-runtime@0.14.1: {} + + regenerator-transform@0.15.2: + dependencies: + '@babel/runtime': 7.26.0 + + regexpu-core@6.2.0: + dependencies: + regenerate: 1.4.2 + regenerate-unicode-properties: 10.2.0 + regjsgen: 0.8.0 + regjsparser: 0.12.0 + unicode-match-property-ecmascript: 2.0.0 + unicode-match-property-value-ecmascript: 2.2.0 + + registry-auth-token@5.0.3: + dependencies: + '@pnpm/npm-conf': 2.3.1 + + registry-url@6.0.1: + dependencies: + rc: 1.2.8 + + regjsgen@0.8.0: {} + + regjsparser@0.12.0: + dependencies: + jsesc: 3.0.2 + + rehype-raw@7.0.0: + dependencies: + '@types/hast': 3.0.4 + hast-util-raw: 9.1.0 + vfile: 6.0.3 + + rehype-recma@1.0.0: + dependencies: + '@types/estree': 1.0.6 + '@types/hast': 3.0.4 + hast-util-to-estree: 3.1.0 + transitivePeerDependencies: + - supports-color + + relateurl@0.2.7: {} + + remark-directive@3.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-directive: 3.0.0 + micromark-extension-directive: 3.0.2 + unified: 11.0.5 + transitivePeerDependencies: + - supports-color + + remark-emoji@4.0.1: + dependencies: + '@types/mdast': 4.0.4 + emoticon: 4.1.0 + mdast-util-find-and-replace: 3.0.1 + node-emoji: 2.2.0 + unified: 11.0.5 + + remark-frontmatter@5.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-frontmatter: 2.0.1 + micromark-extension-frontmatter: 2.0.0 + unified: 11.0.5 + transitivePeerDependencies: + - supports-color + + remark-gfm@4.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-gfm: 3.0.0 + micromark-extension-gfm: 3.0.0 + remark-parse: 11.0.0 + remark-stringify: 11.0.0 + unified: 11.0.5 + transitivePeerDependencies: + - supports-color + + remark-mdx@3.1.0: + dependencies: + mdast-util-mdx: 3.0.0 + micromark-extension-mdxjs: 3.0.0 + transitivePeerDependencies: + - supports-color + + remark-parse@11.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-from-markdown: 2.0.2 + micromark-util-types: 2.0.1 + unified: 11.0.5 + transitivePeerDependencies: + - supports-color + + remark-rehype@11.1.1: + dependencies: + '@types/hast': 3.0.4 + '@types/mdast': 4.0.4 + mdast-util-to-hast: 13.2.0 + unified: 11.0.5 + vfile: 6.0.3 + + remark-stringify@11.0.0: + dependencies: + '@types/mdast': 4.0.4 + mdast-util-to-markdown: 2.1.2 + unified: 11.0.5 + + renderkid@3.0.0: + dependencies: + css-select: 4.3.0 + dom-converter: 0.2.0 + htmlparser2: 6.1.0 + lodash: 4.17.21 + strip-ansi: 6.0.1 + + repeat-string@1.6.1: {} + + require-from-string@2.0.2: {} + + require-like@0.1.2: {} + + requires-port@1.0.0: {} + + resolve-alpn@1.2.1: {} + + resolve-from@4.0.0: {} + + resolve-package-path@4.0.3: + dependencies: + path-root: 0.1.1 + + resolve-pathname@3.0.0: {} + + resolve@1.22.8: + dependencies: + is-core-module: 2.15.1 + path-parse: 1.0.7 + supports-preserve-symlinks-flag: 1.0.0 + + responselike@3.0.0: + dependencies: + lowercase-keys: 3.0.0 + + retry@0.13.1: {} + + reusify@1.0.4: {} + + rimraf@3.0.2: + dependencies: + glob: 7.2.3 + + rtl-detect@1.1.2: {} + + rtlcss@4.3.0: + dependencies: + escalade: 3.2.0 + picocolors: 1.1.1 + postcss: 8.4.49 + strip-json-comments: 3.1.1 + + run-parallel@1.2.0: + dependencies: + queue-microtask: 1.2.3 + + safe-buffer@5.1.2: {} + + safe-buffer@5.2.1: {} + + safer-buffer@2.1.2: {} + + sax@1.4.1: {} + + scheduler@0.23.2: + dependencies: + loose-envify: 1.4.0 + + schema-utils@2.7.0: + dependencies: + '@types/json-schema': 7.0.15 + ajv: 6.12.6 + ajv-keywords: 3.5.2(ajv@6.12.6) + + schema-utils@3.3.0: + dependencies: + '@types/json-schema': 7.0.15 + ajv: 6.12.6 + ajv-keywords: 3.5.2(ajv@6.12.6) + + schema-utils@4.2.0: + dependencies: + '@types/json-schema': 7.0.15 + ajv: 8.17.1 + ajv-formats: 2.1.1(ajv@8.17.1) + ajv-keywords: 5.1.0(ajv@8.17.1) + + search-insights@2.17.3: {} + + section-matter@1.0.0: + dependencies: + extend-shallow: 2.0.1 + kind-of: 6.0.3 + + select-hose@2.0.0: {} + + selfsigned@2.4.1: + dependencies: + '@types/node-forge': 1.3.11 + node-forge: 1.3.1 + + semver-diff@4.0.0: + dependencies: + semver: 7.6.3 + + semver@6.3.1: {} + + semver@7.6.3: {} + + send@0.19.0: + dependencies: + debug: 2.6.9 + depd: 2.0.0 + destroy: 1.2.0 + encodeurl: 1.0.2 + escape-html: 1.0.3 + etag: 1.8.1 + fresh: 0.5.2 + http-errors: 2.0.0 + mime: 1.6.0 + ms: 2.1.3 + on-finished: 2.4.1 + range-parser: 1.2.1 + statuses: 2.0.1 + transitivePeerDependencies: + - supports-color + + serialize-javascript@6.0.2: + dependencies: + randombytes: 2.1.0 + + serve-handler@6.1.6: + dependencies: + bytes: 3.0.0 + content-disposition: 0.5.2 + mime-types: 2.1.18 + minimatch: 3.1.2 + path-is-inside: 1.0.2 + path-to-regexp: 3.3.0 + range-parser: 1.2.0 + + serve-index@1.9.1: + dependencies: + accepts: 1.3.8 + batch: 0.6.1 + debug: 2.6.9 + escape-html: 1.0.3 + http-errors: 1.6.3 + mime-types: 2.1.35 + parseurl: 1.3.3 + transitivePeerDependencies: + - supports-color + + serve-static@1.16.2: + dependencies: + encodeurl: 2.0.0 + escape-html: 1.0.3 + parseurl: 1.3.3 + send: 0.19.0 + transitivePeerDependencies: + - supports-color + + set-function-length@1.2.2: + dependencies: + define-data-property: 1.1.4 + es-errors: 1.3.0 + function-bind: 1.1.2 + get-intrinsic: 1.2.5 + gopd: 1.2.0 + has-property-descriptors: 1.0.2 + + setprototypeof@1.1.0: {} + + setprototypeof@1.2.0: {} + + shallow-clone@3.0.1: + dependencies: + kind-of: 6.0.3 + + shallowequal@1.1.0: {} + + sharp@0.32.6: + dependencies: + color: 4.2.3 + detect-libc: 2.0.3 + node-addon-api: 6.1.0 + prebuild-install: 7.1.2 + semver: 7.6.3 + simple-get: 4.0.1 + tar-fs: 3.0.6 + tunnel-agent: 0.6.0 + + shebang-command@2.0.0: + dependencies: + shebang-regex: 3.0.0 + + shebang-regex@3.0.0: {} + + shell-quote@1.8.2: {} + + shelljs@0.8.5: + dependencies: + glob: 7.2.3 + interpret: 1.4.0 + rechoir: 0.6.2 + + side-channel@1.0.6: + dependencies: + call-bind: 1.0.8 + es-errors: 1.3.0 + get-intrinsic: 1.2.5 + object-inspect: 1.13.3 + + signal-exit@3.0.7: {} + + simple-concat@1.0.1: {} + + simple-get@4.0.1: + dependencies: + decompress-response: 6.0.0 + once: 1.4.0 + simple-concat: 1.0.1 + + simple-swizzle@0.2.2: + dependencies: + is-arrayish: 0.3.2 + + sirv@2.0.4: + dependencies: + '@polka/url': 1.0.0-next.28 + mrmime: 2.0.0 + totalist: 3.0.1 + + sisteransi@1.0.5: {} + + sitemap@7.1.2: + dependencies: + '@types/node': 17.0.45 + '@types/sax': 1.2.7 + arg: 5.0.2 + sax: 1.4.1 + + skin-tone@2.0.0: + dependencies: + unicode-emoji-modifier-base: 1.0.0 + + slash@3.0.0: {} + + slash@4.0.0: {} + + snake-case@3.0.4: + dependencies: + dot-case: 3.0.4 + tslib: 2.8.1 + + sockjs@0.3.24: + dependencies: + faye-websocket: 0.11.4 + uuid: 8.3.2 + websocket-driver: 0.7.4 + + sort-css-media-queries@2.2.0: {} + + source-map-js@1.2.1: {} + + source-map-support@0.5.21: + dependencies: + buffer-from: 1.1.2 + source-map: 0.6.1 + + source-map@0.6.1: {} + + source-map@0.7.4: {} + + space-separated-tokens@2.0.2: {} + + spdy-transport@3.0.0: + dependencies: + debug: 4.4.0 + detect-node: 2.1.0 + hpack.js: 2.1.6 + obuf: 1.1.2 + readable-stream: 3.6.2 + wbuf: 1.7.3 + transitivePeerDependencies: + - supports-color + + spdy@4.0.2: + dependencies: + debug: 4.4.0 + handle-thing: 2.0.1 + http-deceiver: 1.2.7 + select-hose: 2.0.0 + spdy-transport: 3.0.0 + transitivePeerDependencies: + - supports-color + + sprintf-js@1.0.3: {} + + srcset@4.0.0: {} + + statuses@1.5.0: {} + + statuses@2.0.1: {} + + std-env@3.8.0: {} + + streamx@2.21.0: + dependencies: + fast-fifo: 1.3.2 + queue-tick: 1.0.1 + text-decoder: 1.2.2 + optionalDependencies: + bare-events: 2.5.0 + + string-width@4.2.3: + dependencies: + emoji-regex: 8.0.0 + is-fullwidth-code-point: 3.0.0 + strip-ansi: 6.0.1 + + string-width@5.1.2: + dependencies: + eastasianwidth: 0.2.0 + emoji-regex: 9.2.2 + strip-ansi: 7.1.0 + + string_decoder@1.1.1: + dependencies: + safe-buffer: 5.1.2 + + string_decoder@1.3.0: + dependencies: + safe-buffer: 5.2.1 + + stringify-entities@4.0.4: + dependencies: + character-entities-html4: 2.1.0 + character-entities-legacy: 3.0.0 + + stringify-object@3.3.0: + dependencies: + get-own-enumerable-property-symbols: 3.0.2 + is-obj: 1.0.1 + is-regexp: 1.0.0 + + strip-ansi@6.0.1: + dependencies: + ansi-regex: 5.0.1 + + strip-ansi@7.1.0: + dependencies: + ansi-regex: 6.1.0 + + strip-bom-string@1.0.0: {} + + strip-final-newline@2.0.0: {} + + strip-json-comments@2.0.1: {} + + strip-json-comments@3.1.1: {} + + style-to-object@0.4.4: + dependencies: + inline-style-parser: 0.1.1 + + style-to-object@1.0.8: + dependencies: + inline-style-parser: 0.2.4 + + stylehacks@6.1.1(postcss@8.4.49): + dependencies: + browserslist: 4.24.2 + postcss: 8.4.49 + postcss-selector-parser: 6.1.2 + + supports-color@7.2.0: + dependencies: + has-flag: 4.0.0 + + supports-color@8.1.1: + dependencies: + has-flag: 4.0.0 + + supports-preserve-symlinks-flag@1.0.0: {} + + svg-parser@2.0.4: {} + + svgo@3.3.2: + dependencies: + '@trysound/sax': 0.2.0 + commander: 7.2.0 + css-select: 5.1.0 + css-tree: 2.3.1 + css-what: 6.1.0 + csso: 5.0.5 + picocolors: 1.1.1 + + swc-loader@0.2.6(@swc/core@1.10.1)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@swc/core': 1.10.1 + '@swc/counter': 0.1.3 + webpack: 5.97.1(@swc/core@1.10.1) + + tapable@1.1.3: {} + + tapable@2.2.1: {} + + tar-fs@2.1.1: + dependencies: + chownr: 1.1.4 + mkdirp-classic: 0.5.3 + pump: 3.0.2 + tar-stream: 2.2.0 + + tar-fs@3.0.6: + dependencies: + pump: 3.0.2 + tar-stream: 3.1.7 + optionalDependencies: + bare-fs: 2.3.5 + bare-path: 2.1.3 + + tar-stream@2.2.0: + dependencies: + bl: 4.1.0 + end-of-stream: 1.4.4 + fs-constants: 1.0.0 + inherits: 2.0.4 + readable-stream: 3.6.2 + + tar-stream@3.1.7: + dependencies: + b4a: 1.6.7 + fast-fifo: 1.3.2 + streamx: 2.21.0 + + terser-webpack-plugin@5.3.10(@swc/core@1.10.1)(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@jridgewell/trace-mapping': 0.3.25 + jest-worker: 27.5.1 + schema-utils: 3.3.0 + serialize-javascript: 6.0.2 + terser: 5.37.0 + webpack: 5.97.1(@swc/core@1.10.1) + optionalDependencies: + '@swc/core': 1.10.1 + + terser@5.37.0: + dependencies: + '@jridgewell/source-map': 0.3.6 + acorn: 8.14.0 + commander: 2.20.3 + source-map-support: 0.5.21 + + text-decoder@1.2.2: + dependencies: + b4a: 1.6.7 + + text-table@0.2.0: {} + + thunky@1.1.0: {} + + tiny-invariant@1.3.3: {} + + tiny-warning@1.0.3: {} + + to-regex-range@5.0.1: + dependencies: + is-number: 7.0.0 + + toidentifier@1.0.1: {} + + totalist@3.0.1: {} + + trim-lines@3.0.1: {} + + trough@2.2.0: {} + + tslib@2.8.1: {} + + tunnel-agent@0.6.0: + dependencies: + safe-buffer: 5.2.1 + + type-fest@0.21.3: {} + + type-fest@1.4.0: {} + + type-fest@2.19.0: {} + + type-is@1.6.18: + dependencies: + media-typer: 0.3.0 + mime-types: 2.1.35 + + typedarray-to-buffer@3.1.5: + dependencies: + is-typedarray: 1.0.0 + + typeface-roboto@1.1.13: {} + + typescript@5.7.2: {} + + undici-types@6.20.0: {} + + undici@6.21.0: {} + + unicode-canonical-property-names-ecmascript@2.0.1: {} + + unicode-emoji-modifier-base@1.0.0: {} + + unicode-match-property-ecmascript@2.0.0: + dependencies: + unicode-canonical-property-names-ecmascript: 2.0.1 + unicode-property-aliases-ecmascript: 2.1.0 + + unicode-match-property-value-ecmascript@2.2.0: {} + + unicode-property-aliases-ecmascript@2.1.0: {} + + unified@11.0.5: + dependencies: + '@types/unist': 3.0.3 + bail: 2.0.2 + devlop: 1.1.0 + extend: 3.0.2 + is-plain-obj: 4.1.0 + trough: 2.2.0 + vfile: 6.0.3 + + unique-string@3.0.0: + dependencies: + crypto-random-string: 4.0.0 + + unist-util-is@6.0.0: + dependencies: + '@types/unist': 3.0.3 + + unist-util-position-from-estree@2.0.0: + dependencies: + '@types/unist': 3.0.3 + + unist-util-position@5.0.0: + dependencies: + '@types/unist': 3.0.3 + + unist-util-stringify-position@4.0.0: + dependencies: + '@types/unist': 3.0.3 + + unist-util-visit-parents@6.0.1: + dependencies: + '@types/unist': 3.0.3 + unist-util-is: 6.0.0 + + unist-util-visit@5.0.0: + dependencies: + '@types/unist': 3.0.3 + unist-util-is: 6.0.0 + unist-util-visit-parents: 6.0.1 + + universalify@2.0.1: {} + + unpipe@1.0.0: {} + + update-browserslist-db@1.1.1(browserslist@4.24.2): + dependencies: + browserslist: 4.24.2 + escalade: 3.2.0 + picocolors: 1.1.1 + + update-notifier@6.0.2: + dependencies: + boxen: 7.1.1 + chalk: 5.3.0 + configstore: 6.0.0 + has-yarn: 3.0.0 + import-lazy: 4.0.0 + is-ci: 3.0.1 + is-installed-globally: 0.4.0 + is-npm: 6.0.0 + is-yarn-global: 0.4.1 + latest-version: 7.0.0 + pupa: 3.1.0 + semver: 7.6.3 + semver-diff: 4.0.0 + xdg-basedir: 5.1.0 + + uri-js@4.4.1: + dependencies: + punycode: 2.3.1 + + url-loader@4.1.1(file-loader@6.2.0(webpack@5.97.1(@swc/core@1.10.1)))(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + loader-utils: 2.0.4 + mime-types: 2.1.35 + schema-utils: 3.3.0 + webpack: 5.97.1(@swc/core@1.10.1) + optionalDependencies: + file-loader: 6.2.0(webpack@5.97.1(@swc/core@1.10.1)) + + util-deprecate@1.0.2: {} + + utila@0.4.0: {} + + utility-types@3.11.0: {} + + utils-merge@1.0.1: {} + + uuid@8.3.2: {} + + validate-peer-dependencies@2.2.0: + dependencies: + resolve-package-path: 4.0.3 + semver: 7.6.3 + + value-equal@1.0.1: {} + + vary@1.1.2: {} + + vfile-location@5.0.3: + dependencies: + '@types/unist': 3.0.3 + vfile: 6.0.3 + + vfile-message@4.0.2: + dependencies: + '@types/unist': 3.0.3 + unist-util-stringify-position: 4.0.0 + + vfile@6.0.3: + dependencies: + '@types/unist': 3.0.3 + vfile-message: 4.0.2 + + watchpack@2.4.2: + dependencies: + glob-to-regexp: 0.4.1 + graceful-fs: 4.2.11 + + wbuf@1.7.3: + dependencies: + minimalistic-assert: 1.0.1 + + web-namespaces@2.0.1: {} + + webpack-bundle-analyzer@4.10.2: + dependencies: + '@discoveryjs/json-ext': 0.5.7 + acorn: 8.14.0 + acorn-walk: 8.3.4 + commander: 7.2.0 + debounce: 1.2.1 + escape-string-regexp: 4.0.0 + gzip-size: 6.0.0 + html-escaper: 2.0.2 + opener: 1.5.2 + picocolors: 1.1.1 + sirv: 2.0.4 + ws: 7.5.10 + transitivePeerDependencies: + - bufferutil + - utf-8-validate + + webpack-dev-middleware@5.3.4(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + colorette: 2.0.20 + memfs: 3.5.3 + mime-types: 2.1.35 + range-parser: 1.2.1 + schema-utils: 4.2.0 + webpack: 5.97.1(@swc/core@1.10.1) + + webpack-dev-server@4.15.2(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + '@types/bonjour': 3.5.13 + '@types/connect-history-api-fallback': 1.5.4 + '@types/express': 4.17.21 + '@types/serve-index': 1.9.4 + '@types/serve-static': 1.15.7 + '@types/sockjs': 0.3.36 + '@types/ws': 8.5.13 + ansi-html-community: 0.0.8 + bonjour-service: 1.3.0 + chokidar: 3.6.0 + colorette: 2.0.20 + compression: 1.7.5 + connect-history-api-fallback: 2.0.0 + default-gateway: 6.0.3 + express: 4.21.2 + graceful-fs: 4.2.11 + html-entities: 2.5.2 + http-proxy-middleware: 2.0.7(@types/express@4.17.21) + ipaddr.js: 2.2.0 + launch-editor: 2.9.1 + open: 8.4.2 + p-retry: 4.6.2 + rimraf: 3.0.2 + schema-utils: 4.2.0 + selfsigned: 2.4.1 + serve-index: 1.9.1 + sockjs: 0.3.24 + spdy: 4.0.2 + webpack-dev-middleware: 5.3.4(webpack@5.97.1(@swc/core@1.10.1)) + ws: 8.18.0 + optionalDependencies: + webpack: 5.97.1(@swc/core@1.10.1) + transitivePeerDependencies: + - bufferutil + - debug + - supports-color + - utf-8-validate + + webpack-merge@5.10.0: + dependencies: + clone-deep: 4.0.1 + flat: 5.0.2 + wildcard: 2.0.1 + + webpack-merge@6.0.1: + dependencies: + clone-deep: 4.0.1 + flat: 5.0.2 + wildcard: 2.0.1 + + webpack-sources@3.2.3: {} + + webpack@5.97.1(@swc/core@1.10.1): + dependencies: + '@types/eslint-scope': 3.7.7 + '@types/estree': 1.0.6 + '@webassemblyjs/ast': 1.14.1 + '@webassemblyjs/wasm-edit': 1.14.1 + '@webassemblyjs/wasm-parser': 1.14.1 + acorn: 8.14.0 + browserslist: 4.24.2 + chrome-trace-event: 1.0.4 + enhanced-resolve: 5.17.1 + es-module-lexer: 1.5.4 + eslint-scope: 5.1.1 + events: 3.3.0 + glob-to-regexp: 0.4.1 + graceful-fs: 4.2.11 + json-parse-even-better-errors: 2.3.1 + loader-runner: 4.3.0 + mime-types: 2.1.35 + neo-async: 2.6.2 + schema-utils: 3.3.0 + tapable: 2.2.1 + terser-webpack-plugin: 5.3.10(@swc/core@1.10.1)(webpack@5.97.1(@swc/core@1.10.1)) + watchpack: 2.4.2 + webpack-sources: 3.2.3 + transitivePeerDependencies: + - '@swc/core' + - esbuild + - uglify-js + + webpackbar@6.0.1(webpack@5.97.1(@swc/core@1.10.1)): + dependencies: + ansi-escapes: 4.3.2 + chalk: 4.1.2 + consola: 3.2.3 + figures: 3.2.0 + markdown-table: 2.0.0 + pretty-time: 1.1.0 + std-env: 3.8.0 + webpack: 5.97.1(@swc/core@1.10.1) + wrap-ansi: 7.0.0 + + websocket-driver@0.7.4: + dependencies: + http-parser-js: 0.5.8 + safe-buffer: 5.2.1 + websocket-extensions: 0.1.4 + + websocket-extensions@0.1.4: {} + + whatwg-encoding@3.1.1: + dependencies: + iconv-lite: 0.6.3 + + whatwg-mimetype@4.0.0: {} + + which@1.3.1: + dependencies: + isexe: 2.0.0 + + which@2.0.2: + dependencies: + isexe: 2.0.0 + + widest-line@4.0.1: + dependencies: + string-width: 5.1.2 + + wildcard@2.0.1: {} + + wrap-ansi@7.0.0: + dependencies: + ansi-styles: 4.3.0 + string-width: 4.2.3 + strip-ansi: 6.0.1 + + wrap-ansi@8.1.0: + dependencies: + ansi-styles: 6.2.1 + string-width: 5.1.2 + strip-ansi: 7.1.0 + + wrappy@1.0.2: {} + + write-file-atomic@3.0.3: + dependencies: + imurmurhash: 0.1.4 + is-typedarray: 1.0.0 + signal-exit: 3.0.7 + typedarray-to-buffer: 3.1.5 + + ws@7.5.10: {} + + ws@8.18.0: {} + + xdg-basedir@5.1.0: {} + + xml-js@1.6.11: + dependencies: + sax: 1.4.1 + + yallist@3.1.1: {} + + yaml@1.10.2: {} + + yocto-queue@0.1.0: {} + + yocto-queue@1.1.1: {} + + zwitch@2.0.4: {} diff --git a/pp/integrations/plugin-packs/dev-resources/develop-with-centreon-plugins.md b/pp/integrations/plugin-packs/dev-resources/develop-with-centreon-plugins.md index 372b460b5e6c..ba5caac95d2e 100644 --- a/pp/integrations/plugin-packs/dev-resources/develop-with-centreon-plugins.md +++ b/pp/integrations/plugin-packs/dev-resources/develop-with-centreon-plugins.md @@ -507,7 +507,7 @@ sub new { 'port:s' => { name => 'port', default => 443 }, 'timeout:s' => { name => 'timeout' }, # These options are here to defined conditions about which status the plugin will return regarding HTTP response code - 'unknown-status:s' => { name => 'unknown_status', default => '%{http_code} < 200 or %{http_code} >= 300' }, + 'unknown-status:s' => { name => 'unknown_status', default => '%\{http_code\} < 200 or %\{http_code\} >= 300' }, 'warning-status:s' => { name => 'warning_status' }, 'critical-status:s' => { name => 'critical_status', default => '' } }); @@ -529,7 +529,7 @@ sub check_options { $self->SUPER::check_options(%options); # Check if the user provided a value for --hostname option. If not, display a message and exit - if (!defined($self->{option_results}->{hostname}) || $self->{option_results}->{hostname} eq '') { + if (!defined($self->{option_results}-\{hostname\}) || $self->{option_results}-\{hostname\} eq '') { $self->{output}->add_option_msg(short_msg => 'Please set hostname option'); $self->{output}->option_exit(); } @@ -584,8 +584,8 @@ sub set_counters { # All properties below (before et) are related to the catalog_status_ng catalog function imported at the top of our mode type => 2, # These properties allow you to define default thresholds for each status but not mandatory. - warning_default => '%{health} =~ /yellow/', - critical_default => '%{health} =~ /red/', + warning_default => '%\{health\} =~ /yellow/', + critical_default => '%\{health\} =~ /red/', # To simplify, manage things related to how get value in the counter, what to display and specific threshold # check because of the type of the data (string) set => { @@ -981,7 +981,7 @@ sub manage_selection { # Initialize an empty app_metrics counter. $self->{app_metrics} = {}; # Loop in the connections array of hashes - foreach my $entry (@{ $decoded_content->{connections} }) { + foreach my $entry (@\{ $decoded_content->{connections\} }) { # Same logic than type => 0 counters but an extra key $entry->{component} to associate the value # with a specific instance $self->{app_metrics}->{ $entry->{component} }->{display} = $entry->{component}; @@ -989,7 +989,7 @@ sub manage_selection { }; # Exactly the same thing with errors - foreach my $entry (@{ $decoded_content->{errors} }) { + foreach my $entry (@\{ $decoded_content->{errors\} }) { # Don't need to redefine the display key, just assign a value to the error key_value while # keeping the $entry->{component} key to associate the value with the good instance $self->{app_metrics}->{ $entry->{component} }->{errors} = $entry->{value}; @@ -1066,7 +1066,7 @@ Check my-awesome-app metrics exposed through its API Warning and critical threshold for application health string. -Defaults values are: --warning-health='%{health} eq "yellow"' --critical-health='%{health} eq "red"' +Defaults values are: --warning-health='%\{health\} eq "yellow"' --critical-health='%\{health\} eq "red"' =item B<--warning/critical-select> @@ -1106,8 +1106,8 @@ Mode: --warning/critical-health Warning and critical threshold for application health string. - Defaults are: --warning-health='%{health} eq "yellow"' & - --critical-health='%{health} eq "red"' + Defaults are: --warning-health='%\{health\} eq "yellow"' & + --critical-health='%\{health\} eq "red"' --warning/critical-select Warning and critical threshold for select queries diff --git a/pp/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md b/pp/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md index 8e8ee2704a7f..413030c4f73f 100644 --- a/pp/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md +++ b/pp/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins.md @@ -29,7 +29,7 @@ the binary it uses exists or doesn't contain a typo. On RPM-based systems, you can use the following command to identify what's the package is providing the missing binary: `yum whatprovides "*/the_binary_name"` -### UNKNOWN: Cannot write statefile '/var/lib/centreon/centplugins/' +### UNKNOWN: Cannot write statefile '/var/lib/centreon/centplugins/\' The most common cause is inappropriate rights on the cache directory (`/var/lib/centreon/centplugins`) or the cache file itself. It can also be the result of an inconsistent installation @@ -49,7 +49,7 @@ If directory rights are ok, check also the rights of the cache file: `stat /var/lib/centreon/centplugins/`. The expected result is: ```bash -File: '/var/lib/centreon/centplugins/' +File: '/var/lib/centreon/centplugins/\' [...] Access: (0664/-rw-rw-r--) Uid: ( 994/centreon-engine) Gid: ( 991/centreon-engine) [...] @@ -250,9 +250,9 @@ A proxy connection may also be necessary to connect to the API. This can be done ## SSH and CLI checks -### UNKNOWN: Command error: ``: : command not found +### UNKNOWN: Command error: ``: \: command not found -This error warns that the Plugin is not able to execute the because it +This error warns that the Plugin is not able to execute the \ because it doesn't exist in PATH or is not installed. Depending on how the check is performed (locally or remotely), make sure that the @@ -288,7 +288,7 @@ allows your monitoring server to send remote command execution. Do not forget to restart your NRPE daemon to update the configuration. -### NRPE: Command not defined +### NRPE: Command \ not defined The NRPE Server throws this error when the client asks to run a command it doesn't understand. diff --git a/pp/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md b/pp/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md index 163725526458..d1f67770e17f 100644 --- a/pp/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md +++ b/pp/integrations/plugin-packs/getting-started/how-to-guides/windows-winrm-wsman-tutorial.md @@ -176,8 +176,9 @@ wmic useraccount where name="@USERNAME@" get name,sid ``` Output: ->

                                                    Name          SID

                                                    ->@USRNAME@  S-1-5-21-3051596711-3341658857-577043467-1000 +> Name          SID +> +> @USRNAME@  S-1-5-21-3051596711-3341658857-577043467-1000 #### Retrieve current SDDL for Service Control Manager @@ -399,17 +400,17 @@ $Thumbprint=Invoke-Command -ComputerName $FQDN ` Set-WSManInstance -ResourceURI winrm/config/Listener ` - -SelectorSet @{Address="*";Transport="HTTPS"} ` + -SelectorSet @\{Address="*";Transport="HTTPS"\} ` -ComputerName $FQDN ` - -ValueSet @{CertificateThumbprint=$Thumbprint} + -ValueSet @\{CertificateThumbprint=$Thumbprint\} -winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@{Hostname=".$FQDN.".;CertificateThumbprint=".$Thumbprint."}" +winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@\{Hostname=".$FQDN.".;CertificateThumbprint=".$Thumbprint."\}" ``` * Copy this script in the following location to be able to deploy it massively: ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` In our case it looks like this: @@ -625,7 +626,7 @@ $RootSecurity.PsBase.InvokeMethod("SetSd",$SdList) * Copy this script to the following location to be able to deploy this script massively. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` * Go back to your **Enable WinRM** policy. @@ -718,7 +719,7 @@ Invoke-Expression -Command:$SetPermissionsCommand * Copy this script to the following location to be able to massively deploy it. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` * Go back to your **Enable WinRM** policy. @@ -818,7 +819,7 @@ Set-Item -Path WSMan:\localhost\Service\RootSDDL -Value $new_sddl -Force * Copy this script to the following location to be able to deploy it massively. ``` bash -\\\SYSVOL\\scripts +\SYSVOL\scripts ``` * Go back to the **Enable WinRM** policy. diff --git a/pp/integrations/plugin-packs/procedures/applications-ansible-tower.md b/pp/integrations/plugin-packs/procedures/applications-ansible-tower.md index 2d2be91ffa4d..2036ab0fef8c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-ansible-tower.md +++ b/pp/integrations/plugin-packs/procedures/applications-ansible-tower.md @@ -222,12 +222,12 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Default value | Mandatory | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /default/ | | | FILTERNAME | Filter host name (can use regexp) | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -261,7 +261,7 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Default value | Mandatory | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /default/ | | | FILTERNAME | Filter job template name (can use regexp) | | | | WARNINGCANCELED | Threshold | | | | CRITICALCANCELED | Threshold | | | @@ -269,8 +269,8 @@ yum install centreon-plugin-Applications-Ansible-Tower | CRITICALDEFAULT | Threshold | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGNEVER | Threshold | | | | CRITICALNEVER | Threshold | | | | WARNINGPENDING | Threshold | | | @@ -310,7 +310,7 @@ yum install centreon-plugin-Applications-Ansible-Tower | Macro | Description | Default value | Mandatory | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /default/ | | +| UNKNOWNJOBSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /default/ | | | FILTERNAME | Filter schedule name (can use regexp) | | | | WARNINGCANCELED | Threshold | | | | CRITICALCANCELED | Threshold | | | @@ -318,8 +318,8 @@ yum install centreon-plugin-Applications-Ansible-Tower | CRITICALDEFAULT | Threshold | | | | WARNINGFAILED | Threshold | | | | CRITICALFAILED | Threshold | | | -| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | %{last\_job\_status} =~ /failed/ | | -| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | | | +| CRITICALJOBSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | %\{last_job_status\} =~ /failed/ | | +| WARNINGJOBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | | | | WARNINGNEVER | Threshold | | | | CRITICALNEVER | Threshold | | | | WARNINGPENDING | Threshold | | | @@ -354,9 +354,9 @@ is able to monitor a resource using a command like this one (replace the sample --password='' \ --custommode='api' \ --filter-name='' \ - --unknown-job-status='%{last\_job\_status} =~ /default/' \ + --unknown-job-status='%\{last_job_status\} =~ /default/' \ --warning-job-status='' \ - --critical-job-status='%{last\_job\_status} =~ /failed/' \ + --critical-job-status='%\{last_job_status\} =~ /failed/' \ --warning-total='' \ --critical-total='' \ --warning-failed='' \ @@ -440,7 +440,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -486,9 +486,9 @@ All available options for each service template are listed below: |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter host name (can use regexp). | | --display-failed-hosts | Display failed hosts list in verbose output. | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'failed'. |                                                     @@ -513,9 +513,9 @@ All available options for each service template are listed below: | --launch-extra-vars | yaml format text that contains extra variables to pass on. | | --launch-max-retries | Number of retries to get job result once launched (default: 5). | | --launch-retry-interval | Number of seconds between retries (default : 10). | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'successful', 'failed', 'running', 'canceled', 'pending', 'default', 'never'. | @@ -560,9 +560,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter schedule name (can use regexp). | -| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%{last\_job\_status} =~ /default/'). You can use the following variables: %{last\_job\_status}, %{display} | -| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_job\_status}, %{display} | -| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_job\_status} =~ /failed/'). You can use the following variables: %{last\_job\_status}, %{display} | +| --unknown-job-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{last_job_status\} =~ /default/'). You can use the following variables: %\{last_job_status\}, %\{display\} | +| --warning-job-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_job_status\}, %\{display\} | +| --critical-job-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_job_status\} =~ /failed/'). You can use the following variables: %\{last_job_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'successful', 'failed', 'running', 'canceled', 'pending', 'default', 'never', 'start-last-time' (s). | diff --git a/pp/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md b/pp/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md index f885a2404907..696263560ecd 100644 --- a/pp/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-antivirus-clamav-ssh.md @@ -171,12 +171,12 @@ yum install centreon-plugin-Applications-Clamav-Ssh | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------|:-----------:| -| CRITICALDAILYDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | %{last\_dailydb\_version} ne %{current\_dailydb\_version} \|\| %{current\_dailydb\_timediff} \> 432000 | | -| WARNINGDAILYDBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | | | -| WARNINGENGINESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | | | -| CRITICALENGINESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{last\_engine\_version} ne %{current\_engine\_version}'). You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | | | -| CRITICALMAINDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | %{last\_maindb\_version} ne %{current\_maindb\_version} | | -| WARNINGMAINDBSTATUS | Define the conditions to match for the status to be WARNING.You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | | | +| CRITICALDAILYDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | %\{last_dailydb_version\} ne %\{current_dailydb_version\} \|\| %\{current_dailydb_timediff\} \> 432000 | | +| WARNINGDAILYDBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | | | +| WARNINGENGINESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | | | +| CRITICALENGINESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{last_engine_version\} ne %\{current_engine_version\}'). You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | | | +| CRITICALMAINDBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | %\{last_maindb_version\} ne %\{current_maindb_version\} | | +| WARNINGMAINDBSTATUS | Define the conditions to match for the status to be WARNING.You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -202,9 +202,9 @@ is able to monitor a resource using a command like this one (replace the sample --warning-engine-status='' \ --critical-engine-status='' \ --warning-maindb-status='' \ - --critical-maindb-status='%{last_maindb_version} ne %{current_maindb_version}' \ + --critical-maindb-status='%\{last_maindb_version\} ne %\{current_maindb_version\}' \ --warning-dailydb-status='' \ - --critical-dailydb-status='%{last_dailydb_version} ne %{current_dailydb_version} || %{current_dailydb_timediff} > 432000' + --critical-dailydb-status='%\{last_dailydb_version\} ne %\{current_dailydb_version\} || %\{current_dailydb_timediff\} > 432000' ``` The expected command output is shown below: @@ -263,7 +263,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -304,12 +304,12 @@ All available options for each service template are listed below: | --nameservers | Set nameserver to query (can be multiple). The system configuration is used by default. | | --maindb-file | Antivirus main.cvd file (default: '/var/lib/clamav/main.cvd'). | | --dailydb-file | Antivirus daily.cvd file (default: '/var/lib/clamav/daily.cvd'). | -| --warning-engine-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | -| --critical-engine-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_engine\_version} ne %{current\_engine\_version}'). You can use the following variables: %{last\_engine\_version}, %{current\_engine\_version} | -| --warning-maindb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | -| --critical-maindb-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_maindb\_version} ne %{current\_maindb\_version}'). You can use the following variables: %{last\_maindb\_version}, %{current\_maindb\_version}, %{current\_maindb\_timediff} | -| --warning-dailydb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | -| --critical-dailydb-status | Define the conditions to match for the status to be CRITICAL (default: '%{last\_dailydb\_version} ne %{current\_dailydb\_version} \|\| %{current\_dailydb\_timediff} \> 432000'). You can use the following variables: %{last\_dailydb\_version}, %{current\_dailydb\_version}, %{current\_dailydb\_timediff} | +| --warning-engine-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | +| --critical-engine-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_engine_version\} ne %\{current_engine_version\}'). You can use the following variables: %\{last_engine_version\}, %\{current_engine_version\} | +| --warning-maindb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | +| --critical-maindb-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_maindb_version\} ne %\{current_maindb_version\}'). You can use the following variables: %\{last_maindb_version\}, %\{current_maindb_version\}, %\{current_maindb_timediff\} | +| --warning-dailydb-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | +| --critical-dailydb-status | Define the conditions to match for the status to be CRITICAL (default: '%\{last_dailydb_version\} ne %\{current_dailydb_version\} \|\| %\{current_dailydb_timediff\} \> 432000'). You can use the following variables: %\{last_dailydb_version\}, %\{current_dailydb_version\}, %\{current_dailydb_timediff\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md b/pp/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md index 33cbec659560..58188f1cdeea 100644 --- a/pp/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-antivirus-kaspersky-snmp.md @@ -148,7 +148,7 @@ user: /usr/lib/centreon/plugins//centreon_kaspersky_snmp.pl \ --plugin=apps::antivirus::kaspersky::snmp::plugin --mode=protection \ --hostname=10.0.0.1 --snmp-version='2c' --snmp-community='kaseprsky_ro' \ - --warning-status='%{status} =~ /Warning/i' --critical-status='%{status} =~ /Critical/i' + --warning-status='%\{status\} =~ /Warning/i' --critical-status='%\{status\} =~ /Critical/i' --warning-no-antivirus='0' --critical-no-antivirus='' --warning-no-real-time='0' --critical-no-real-time='' \ --warning-not-acceptable-level='0' --critical-not-acceptable-level='' \ --warning-not-cured-objects='0' --critical-not-cured-objects='' \ diff --git a/pp/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md b/pp/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md index bdcce3700dc2..25975207467f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-antivirus-skyhigh-webgateway-snmp.md @@ -490,7 +490,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/applications-awa-jmx.md b/pp/integrations/plugin-packs/procedures/applications-awa-jmx.md index 9e675d8fa1cc..53c441140be4 100644 --- a/pp/integrations/plugin-packs/procedures/applications-awa-jmx.md +++ b/pp/integrations/plugin-packs/procedures/applications-awa-jmx.md @@ -114,7 +114,7 @@ command: --password='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /GREEN/i' \ + --critical-status='%\{status\} !~ /GREEN/i' \ --use-new-perfdata ``` diff --git a/pp/integrations/plugin-packs/procedures/applications-bluemind-ssh.md b/pp/integrations/plugin-packs/procedures/applications-bluemind-ssh.md index b14933ca4fea..f128cd4ee734 100644 --- a/pp/integrations/plugin-packs/procedures/applications-bluemind-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-bluemind-ssh.md @@ -497,7 +497,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md b/pp/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md index faedcd33854a..f9cc15532a6d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-cisco-ssms-restapi.md @@ -198,8 +198,8 @@ yum install centreon-plugin-Applications-Cisco-Ssms-Restapi | ACCOUNT | Check account name (required. Multiple option) | | X | | FILTERCOUNTERS | Only display some counters (regexp can be used). Example: --filter-counters='status' | | | | FILTERLICENSENAME | Filter license name (can be a regexp) | | | -| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in compliance/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /in compliance/i | | -| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in compliance/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /in compliance/i | | +| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -232,7 +232,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-counters= \ --filter-license-name='' \ --warning-license-status='' \ - --critical-license-status='%{status} !~ /in compliance/i' \ + --critical-license-status='%\{status\} !~ /in compliance/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -296,7 +296,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -363,9 +363,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --account | Check account name (required. Multiple option). | | --filter-license-name | Filter license name (can be a regexp). | -| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-license-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-license-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in compliance/i'). You can use the following variables: %{status}, %{display} | +| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-license-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-license-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in compliance/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/pp/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md b/pp/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md index 23b9a3d42c73..589d04c1f11f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-commvault-commserve-restapi.md @@ -234,8 +234,8 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | CRITICALALERTSINFO | Threshold | | | | WARNINGALERTSTOTAL | Threshold | | | | CRITICALALERTSTOTAL | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | %{severity} =~ /warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | %{severity} =~ /critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | %\{severity\} =~ /warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | %\{severity\} =~ /critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -251,10 +251,10 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | TIMEFRAME | Set timeframe in seconds (E.g '3600' to check last 60 minutes) | | | | WARNINGJOBSTOTAL | Threshold | | | | CRITICALJOBSTOTAL | Threshold | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type} | %{status} =~ /abnormal/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status}, %{type} | %{status} =~ /errors\|failed/i | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\} | %\{status\} =~ /abnormal/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\}, %\{type\} | %\{status\} =~ /errors\|failed/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -264,15 +264,15 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| | FILTERMEDIAAGENTID | Filter media agents by ID (can be a regexp) | | | | FILTERMEDIAAGENTNAME | Filter media agents by name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | | | WARNINGMEDIAAGENTSOFFLINE | Threshold | | | | CRITICALMEDIAAGENTSOFFLINE | Threshold | | | | WARNINGMEDIAAGENTSONLINE | Threshold | | | | CRITICALMEDIAAGENTSONLINE | Threshold | | | | WARNINGMEDIAAGENTSTOTAL | Threshold | | | | CRITICALMEDIAAGENTSTOTAL | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | %{is\_maintenance} eq "no" and %{status} eq "offline" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | %\{is_maintenance\} eq "no" and %\{status\} eq "offline" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -281,8 +281,8 @@ yum install centreon-plugin-Applications-Commvault-Commserve-Restapi | Macro | Description | Default value | Mandatory | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter storage pools by name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Threshold | | | | CRITICALUSAGE | Threshold | | | | WARNINGUSAGEFREE | Threshold | | | @@ -313,7 +313,7 @@ is able to monitor a resource using a command like this one (replace the sample --proto='https' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /online/i' \ + --critical-status='%\{status\} !~ /online/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -383,7 +383,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -445,8 +445,8 @@ All available options for each service template are listed below: |:--------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-alert-name | Filter alerts by name (can be a regexp). | | --filter-alert-type | Filter alerts by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning/') You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical/'). You can use the following variables: %{severity}, %{status}, %{type}, %{name}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning/') You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical/'). You can use the following variables: %\{severity\}, %\{status\}, %\{type\}, %\{name\}, %\{since\} | | --memory | Only check new alerts. | @@ -460,10 +460,10 @@ All available options for each service template are listed below: | --filter-client-name | Filter jobs by client name (can be a regexp). | | --filter-client-group | Filter jobs by client groups (can be a regexp). | | --timeframe | Set timeframe in seconds (E.g '3600' to check last 60 minutes). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /abnormal/i') You can use the following variables: %{display}, %{status}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /errors\|failed/i'). You can use the following variables: %{display}, %{status}, %{type} | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{elapsed}, %{type} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /abnormal/i') You can use the following variables: %\{display\}, %\{status\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /errors\|failed/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\} | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{elapsed\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-total'. | @@ -473,9 +473,9 @@ All available options for each service template are listed below: |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-media-agent-id | Filter media agents by ID (can be a regexp). | | --filter-media-agent-name | Filter media agents by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_maintenance} eq "no" and %{status} eq "offline"'). You can use the following variables: %{status}, %{is\_maintenance}, %{offline\_reason}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_maintenance\} eq "no" and %\{status\} eq "offline"'). You can use the following variables: %\{status\}, %\{is_maintenance\}, %\{offline_reason\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'media-agents-total', 'media-agents-online', 'media-agents-offline'. | @@ -485,9 +485,9 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter storage pools by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /online/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /online/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md b/pp/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md index 6ade4fb5301e..ae20208a9982 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-elasticsearch.md @@ -255,8 +255,8 @@ yum install centreon-plugin-Applications-Databases-Elasticsearch | CRITICALSHARDSTOTAL | Critical threshold | | | | WARNINGSHARDSUNASSIGNED | Warning threshold | | | | CRITICALSHARDSUNASSIGNED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{status} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{status} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{status\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\} | %\{status\} =~ /red/i | | | WARNINGTASKSPENDING | Warning threshold | | | | CRITICALTASKSPENDING | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -284,8 +284,8 @@ yum install centreon-plugin-Applications-Databases-Elasticsearch | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds} | %{status} !~ /active/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\} | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -438,8 +438,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* | Warning threshold. Can be: 'nodes-total', 'nodes-data', 'nodes-coordinating', 'nodes-master', 'nodes-ingest', 'indices-total', 'shards-total', 'shards-active-count', 'shards-active-percentage', 'shards-unassigned', 'shards-relocating', 'shards-initializing', 'tasks-pending', 'documents-total', 'data-size'. | | --critical-* | Critical threshold. Can be: 'nodes-total', 'nodes-data', 'nodes-coordinating', 'nodes-master', 'nodes-ingest', 'indices-total', 'shards-total', 'shards-active-count', 'shards-active-percentage', 'shards-unassigned', 'shards-relocating', 'shards-initializing', 'tasks-pending', 'documents-total', 'data-size'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}. | @@ -450,16 +450,16 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* | Warning threshold. Can be: 'documents-total', 'data-size-primaries', 'data-size-total', 'shards-active', 'shards-unassigned'. | | --critical-* | Critical threshold. Can be: 'documents-total', 'data-size-primaries', 'data-size-total', 'shards-active', 'shards-unassigned'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i') You can use the following variables: %{display}, %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red/i'). You can use the following variables: %{display}, %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i') You can use the following variables: %\{display\}, %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red/i'). You can use the following variables: %\{display\}, %\{status\}. | | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{type}, %{issued\_to}, %{expiry\_date\_in\_seconds}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{type\}, %\{issued_to\}, %\{expiry_date_in_seconds\}. | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-firebird.md b/pp/integrations/plugin-packs/procedures/applications-databases-firebird.md index c25e00924ffb..02708d1487e4 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-firebird.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-firebird.md @@ -16,7 +16,7 @@ yum install centreon-plugin-Applications-Databases-Firebird ### Dependencies Please install perl module DBD::Firebird: - Follow the readme, because you need +\ Follow the readme, because you need to install the Firebird C library also. ## Centreon Configuration diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-influxdb.md b/pp/integrations/plugin-packs/procedures/applications-databases-influxdb.md index b285f38dfc60..152a85d8c83f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-influxdb.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-influxdb.md @@ -280,10 +280,10 @@ yum install centreon-plugin-Applications-Databases-Influxdb | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | INSTANCE | Set the instance label for which the results should be calculated (Example: --instance='name'). The instance label must be the same label as the "GROUP BY" keyword | | X | -| OUTPUT | Set the output for each instance (Example: --output='Object %{instance} value is {label}') | | X | +| OUTPUT | Set the output for each instance (Example: --output='Object %\{instance\} value is \{label\}') | | X | | MULTIPLEOUTPUT | Set the global output in case everything is fine for multiple instances (Example: --multiple-output='All instance values are ok') | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %{instance} and any other labels you set through --query | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %{instance} and any other labels you set through --query | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -418,7 +418,7 @@ All generic options are listed here: | --username | Specify username for authentication. | | --password | Specify password for authentication. | | --timeout | Set timeout in seconds (Default: 10). | -| --unknown-http-status | Threshold unknown for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-http-status | Threshold unknown for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-http-status | Warning threshold for http response code. | | --critical-http-status | Critical threshold for http response code. | | --http-peer-addr | Set the address you want to connect to. Useful if hostname is only a vhost, to avoid IP resolution. | @@ -477,10 +477,10 @@ All available options for each service template are listed below: |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --query | Set a InfluxQL query. Query option must be like--query='label,query'. Query must contain an "AS" keyword to rename the column of the selected data, and must match the label. (Example: --query='mymetric,SELECT the\_data AS "mymetric" FROM "database"."retention"."measurement" GROUP BY "instance"') | | --instance | Set the instance label on which the results should be calculate for (Example: --instance='name'). The instance label must be the same label as the "GROUP BY" keyword. | -| --output | Set the output for each instances (Example: --output='Object %{instance} value is {label}'). | +| --output | Set the output for each instances (Example: --output='Object %\{instance\} value is \{label\}'). | | --multiple-output | Set the global output in case everything is fine for multiple instances (Example: --multiple-output='All instance values are ok'). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %{instance} and any other labels you set through --query. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %{instance} and any other labels you set through --query. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). Can use special variables like %\{instance\} and any other labels you set through --query. | | --aggregation | Set the aggregation on metric values (Can be: 'average', 'min', 'max', 'sum') (Default: 'average'). | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md b/pp/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md index 4068cbe3c6e9..7a86369ee366 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-informix-snmp.md @@ -256,9 +256,9 @@ yum install centreon-plugin-Applications-Databases-Informix-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERNAME | Filter chunk name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /inconsistent/'). You can use the following variables: %{status}, %{display} | %{status} =~ /inconsistent/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /inconsistent/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /inconsistent/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -396,7 +396,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -460,9 +460,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter chunk name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /inconsistent/'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /inconsistent/'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-informix.md b/pp/integrations/plugin-packs/procedures/applications-databases-informix.md index 7aa36513fbe1..eaa90e1a8655 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-informix.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-informix.md @@ -44,7 +44,7 @@ To compile DBD Informix, you need an access to an Informix Database, run: # cd DBD-Informix-2013.0521 # export INFORMIXDIR=/home/informix/sdkclient # export LD\_LIBRARY\_PATH=$ORACLE\_HOME/lib - # export PATH=${PATH}:/home/informix/sdkclient/bin + # export PATH=$\{PATH\}:/home/informix/sdkclient/bin # export LD\_LIBRARY\_PATH=/home/informix/sdkclient/lib/esql/:/home/informix/sdkclient/lib/ # export DBD\_INFORMIX\_USERNAME=root # export DBD\_INFORMIX\_PASSWORD=xxxx # export DBD\_INFORMIX\_DATABASE=xxxx diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-mongodb.md b/pp/integrations/plugin-packs/procedures/applications-databases-mongodb.md index 377e7c39da9b..af5325713b0d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-mongodb.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-mongodb.md @@ -358,12 +358,12 @@ yum install centreon-plugin-Applications-Databases-Mongodb | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority} | %{state} !~ /PRIMARY\|SECONDARY/ | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /up/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority} | %{health} !~ /up/ | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\} | %\{state\} !~ /PRIMARY\|SECONDARY/ | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /up/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\} | %\{health\} !~ /up/ | | | WARNINGREPLICATIONLAG | Thresholds | | | | CRITICALREPLICATIONLAG | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{sync\_host} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{sync\_host} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{sync_host\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{sync_host\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -451,7 +451,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -554,10 +554,10 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{sync\_host}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{sync\_host}. | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{state} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority}. | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /up/'). You can use the following variables: %{name}, %{state}, %{health}, %{slave\_delay}, %{priority}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{sync_host\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{sync_host\}. | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} !~ /PRIMARY\|SECONDARY/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\}. | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /up/'). You can use the following variables: %\{name\}, %\{state\}, %\{health\}, %\{slave_delay\}, %\{priority\}. | | --warning-* --critical-* | Thresholds. Can be: 'members-primary', 'members-secondary', 'members-arbiter', 'replication-lag'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-mssql.md b/pp/integrations/plugin-packs/procedures/applications-databases-mssql.md index 777bbb5ac8d7..669317d49530 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-mssql.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-mssql.md @@ -419,8 +419,8 @@ yum install centreon-plugin-Applications-Databases-Mssql | CRITICALJOBSSUCCESS | Thresholds | | | | WARNINGJOBSTOTAL | Thresholds | | | | CRITICALJOBSTOTAL | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{duration} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{duration} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -461,8 +461,8 @@ yum install centreon-plugin-Applications-Databases-Mssql |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -577,7 +577,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -689,8 +689,8 @@ All available options for each service template are listed below: | --filter | Filter job. | | --lookback | Check job history in minutes. | | --add-duration-perfdata | Display job duration time. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{duration} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{duration} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{duration\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-total', 'jobs-failed', 'jobs-success', 'jobs-canceled', 'jobs-running', 'jobs-retry'. | @@ -732,9 +732,9 @@ All available options for each service template are listed below: | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-mysql.md b/pp/integrations/plugin-packs/procedures/applications-databases-mysql.md index 55c47d23189a..8996cea7b169 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-mysql.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-mysql.md @@ -333,8 +333,8 @@ yum install centreon-plugin-Applications-Databases-Mysql | Macro | Description | Default value | Mandatory | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|:-----------:| | FILTERTYPE | Filter backups by type (regexp can be used) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR"'). You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | %{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR"'). You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | %\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | | | | WARNINGTIMELASTEXECUTION | Thresholds | | | | CRITICALTIMELASTEXECUTION | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -411,13 +411,13 @@ yum install centreon-plugin-Applications-Databases-Mysql | PEERPORT | | 3306 | | | PEERUSERNAME | | USERNAME | | | PEERPASSWORD | | PASSWORD | | -| UNKNOWNREPLICATIONSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{replication\_status} =~ /configurationIssue/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /configurationIssue/i | | +| UNKNOWNREPLICATIONSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{replication_status\} =~ /configurationIssue/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /configurationIssue/i | | | PEERHOST | | | | -| UNKNOWNCONNECTIONSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{error\_message}, %{display} | | | -| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "ok"'). You can use the following variables: %{status}, %{error\_message}, %{display} | %{status} ne "ok" | | -| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{error\_message}, %{display} | | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{replication\_status} =~ /inProgress/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /inProgress/i | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{replication\_status} =~ /connectIssueToMaster/i'). You can use the following variables: %{replication\_status}, %{display} | %{replication\_status} =~ /connectIssueToMaster/i | | +| UNKNOWNCONNECTIONSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | | | +| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "ok"'). You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | %\{status\} ne "ok" | | +| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{replication_status\} =~ /inProgress/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /inProgress/i | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{replication_status\} =~ /connectIssueToMaster/i'). You can use the following variables: %\{replication_status\}, %\{display\} | %\{replication_status\} =~ /connectIssueToMaster/i | | | WARNINGSLAVELATENCY | Thresholds | | | | CRITICALSLAVELATENCY | Thresholds | | | | CRITICALSLAVESRUNNING | Thresholds | 1:1 | | @@ -451,8 +451,8 @@ yum install centreon-plugin-Applications-Databases-Mysql | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{expire} ne "never" and %{expire\_time} == 0'). You can use the following variables: %{user}, %{expire}, %{expire\_time} | %{expire} ne "never" and %{expire\_time} == 0 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{user}, %{expire}, %{expire\_time} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{expire\} ne "never" and %\{expire_time\} == 0'). You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | %\{expire\} ne "never" and %\{expire_time\} == 0 | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -499,8 +499,8 @@ yum install centreon-plugin-Applications-Databases-Mysql |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -606,7 +606,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -644,9 +644,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-type | Filter backups by type (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{has\_backup} eq "yes" and %{exit\_state} ne "SUCCESS" and %{last\_error} ne "NO\_ERROR"'). You can use the following variables: %{has\_backup}, %{last\_error}, %{exit\_state}, %{type} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{has_backup\} eq "yes" and %\{exit_state\} ne "SUCCESS" and %\{last_error\} ne "NO\_ERROR"'). You can use the following variables: %\{has_backup\}, %\{last_error\}, %\{exit_state\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'time-last-execution'. | @@ -711,12 +711,12 @@ All available options for each service template are listed below: | Option | Description | |:------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-connection-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{error\_message}, %{display} | -| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{error\_message}, %{display} | -| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "ok"'). You can use the following variables: %{status}, %{error\_message}, %{display} | -| --unknown-replication-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{replication\_status} =~ /configurationIssue/i'). You can use the following variables: %{replication\_status}, %{display} | -| --warning-replication-status | Define the conditions to match for the status to be WARNING (Default: '%{replication\_status} =~ /inProgress/i'). You can use the following variables: %{replication\_status}, %{display} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (Default: '%{replication\_status} =~ /connectIssueToMaster/i'). You can use the following variables: %{replication\_status}, %{display} | +| --unknown-connection-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "ok"'). You can use the following variables: %\{status\}, %\{error_message\}, %\{display\} | +| --unknown-replication-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{replication_status\} =~ /configurationIssue/i'). You can use the following variables: %\{replication_status\}, %\{display\} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING (Default: '%\{replication_status\} =~ /inProgress/i'). You can use the following variables: %\{replication_status\}, %\{display\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{replication_status\} =~ /connectIssueToMaster/i'). You can use the following variables: %\{replication_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'slaves-running', 'slave-latency' (s). | @@ -753,8 +753,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{user}, %{expire}, %{expire\_time} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{expire} ne "never" and %{expire\_time} == 0'). You can use the following variables: %{user}, %{expire}, %{expire\_time} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{expire\} ne "never" and %\{expire_time\} == 0'). You can use the following variables: %\{user\}, %\{expire\}, %\{expire_time\} | @@ -839,9 +839,9 @@ All available options for each service template are listed below: | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-oracle.md b/pp/integrations/plugin-packs/procedures/applications-databases-oracle.md index 147a07d9c855..c270922f792e 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-oracle.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-oracle.md @@ -678,10 +678,10 @@ yum install centreon-plugin-Applications-Databases-Oracle | Macro | Description | Default value | Mandatory | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------|:-----------:| -| WARNINGONLINESTATUS | Set warning threshold for online status (Default: '%{online\_status} =~ /sysoff/i'). You can use the following variables: %{display}, %{online\_status} | %{online\_status} =~ /sysoff/i | | -| CRITICALONLINESTATUS | Set critical threshold for online status (Default: '%{online\_status} =~ /offline\|recover/i'). You can use the following variables: %{display}, %{online\_status} | %{online\_status} =~ /offline\|recover/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %{display}, %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline\|invalid/i'). You can use the following variables: %{display}, %{status} | | | +| WARNINGONLINESTATUS | Set warning threshold for online status (Default: '%\{online_status\} =~ /sysoff/i'). You can use the following variables: %\{display\}, %\{online_status\} | %\{online_status\} =~ /sysoff/i | | +| CRITICALONLINESTATUS | Set critical threshold for online status (Default: '%\{online_status\} =~ /offline\|recover/i'). You can use the following variables: %\{display\}, %\{online_status\} | %\{online_status\} =~ /offline\|recover/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %\{display\}, %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline\|invalid/i'). You can use the following variables: %\{display\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -771,8 +771,8 @@ yum install centreon-plugin-Applications-Databases-Oracle | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -878,8 +878,8 @@ yum install centreon-plugin-Applications-Databases-Oracle |:-------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | SQLSTATEMENT | SQL statement that returns a string | | X | | VALUE | Value column (must be one of the selected field). MANDATORY | | | -| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | | | -| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | | | +| WARNING | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -1017,7 +1017,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1058,11 +1058,11 @@ All available options for each service template are listed below: | --critical-usage | Critical threshold. | | --warning-usage-failure | Warning threshold. | | --critical-usage-failure | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | -| --warning-offline-disks | Set warning threshold for offline disks (Default: '(%{offline\_disks} \> 0 && %{type} eq "extern") \|\| (%{offline\_disks} \> 1 && %{type} eq "high")'). You can use the following variables: %{offline\_disks}, %{type}, %{display} | -| --critical-offline-disks | Set critical threshold for offline disks (Default: '%{offline\_disks} \> 0 && %{type} =~ /^normal\|high$/'). You can use the following variables: %{offline\_disks}, %{type}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | +| --warning-offline-disks | Set warning threshold for offline disks (Default: '(%\{offline_disks\} \> 0 && %\{type\} eq "extern") \|\| (%\{offline_disks\} \> 1 && %\{type\} eq "high")'). You can use the following variables: %\{offline_disks\}, %\{type\}, %\{display\} | +| --critical-offline-disks | Set critical threshold for offline disks (Default: '%\{offline_disks\} \> 0 && %\{type\} =~ /^normal\|high$/'). You can use the following variables: %\{offline_disks\}, %\{type\}, %\{display\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | | --filter-name | Filter by name (regexp can be used). | @@ -1111,10 +1111,10 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). | | --filter-tablespace | Filter tablespace name (can be a regexp). | | --filter-data-file | Filter data file name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %{display}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline\|invalid/i'). You can use the following variables: %{display}, %{status} | -| --warning-online-status | Set warning threshold for online status (Default: '%{online\_status} =~ /sysoff/i'). You can use the following variables: %{display}, %{online\_status} | -| --critical-online-status | Set critical threshold for online status (Default: '%{online\_status} =~ /offline\|recover/i'). You can use the following variables: %{display}, %{online\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: none). You can use the following variables: %\{display\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline\|invalid/i'). You can use the following variables: %\{display\}, %\{status\} | +| --warning-online-status | Set warning threshold for online status (Default: '%\{online_status\} =~ /sysoff/i'). You can use the following variables: %\{display\}, %\{online_status\} | +| --critical-online-status | Set critical threshold for online status (Default: '%\{online_status\} =~ /offline\|recover/i'). You can use the following variables: %\{display\}, %\{online_status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-traffic'. | @@ -1235,8 +1235,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{username}, %{sql\_text}, %{since}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '') You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{username\}, %\{sql_text\}, %\{since\}, %\{status\} | | --timezone | Timezone of oracle server (If not set, we use current server execution timezone). | | --memory | Only check new queries. | @@ -1346,9 +1346,9 @@ All available options for each service template are listed below: | --key-column | Key column (must be one of the selected field). NOT mandatory if you select only one field | | --value-column | Value column (must be one of the selected field). MANDATORY | | --printf-format | Specify a custom output message relying on printf formatting. If this option is set --printf-value is mandatory. | -| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %{key\_field}, %{value\_field}) | -| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %{key\_field}, %{value\_field}) e.g --warning-string '%{key\_field} eq 'Central' && %{value\_field} =~ /127.0.0.1/' | -| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %{key\_field} or %{value\_field}) | +| --printf-value | Specify scalar used to replace in printf. If this option is set --printf-format is mandatory. (Can be: %\{key_field\}, %\{value_field\}) | +| --warning-string | Define the conditions to match for the status to be WARNING. (Can be: %\{key_field\}, %\{value_field\}) e.g --warning-string '%\{key_field\} eq 'Central' && %\{value_field\} =~ /127.0.0.1/' | +| --critical-string | Define the conditions to match for the status to be CRITICAL (Can be: %\{key_field\} or %\{value_field\}) | | --dual-table | Set this option to ensure compatibility with dual table and Oracle. | | --empty-sql-string | Set this option to change the output message when the sql statement result is empty. (Default: 'No row returned or --key-column/--value-column do not correctly match selected field') | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-postgresql.md b/pp/integrations/plugin-packs/procedures/applications-databases-postgresql.md index dd6d8a79643c..d98647ec59e2 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-postgresql.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-postgresql.md @@ -523,7 +523,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-redis.md b/pp/integrations/plugin-packs/procedures/applications-databases-redis.md index 317192857ba2..3df304617b9b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-redis.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-redis.md @@ -337,8 +337,8 @@ yum install centreon-plugin-Applications-Databases-Redis | CRITICALLASTSAVEDURATION | Critical threshold | | | | WARNINGSAVESIZE | Warning threshold | | | | CRITICALSAVESIZE | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{progress\_status} =~ /in progress/i'). You can use the following variables: %{progress\_status}, %{status} | %{sync\_status} =~ /in progress/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /fail/i'). You can use the following variables: %{progress\_status}, %{status} | %{link\_status} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{progress_status\} =~ /in progress/i'). You can use the following variables: %\{progress_status\}, %\{status\} | %\{sync_status\} =~ /in progress/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /fail/i'). You can use the following variables: %\{progress_status\}, %\{status\} | %\{link_status\} =~ /down/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -358,8 +358,8 @@ yum install centreon-plugin-Applications-Databases-Redis | CRITICALSLAVEREADONLY | Critical threshold | | | | WARNINGSLAVEREPLOFFSET | | | | | CRITICALSLAVEREPLOFFSET | | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{sync\_status} =~ /in progress/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | %{sync\_status} =~ /in progress/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /down/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | %{link\_status} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{sync_status\} =~ /in progress/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | %\{sync_status\} =~ /in progress/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /down/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | %\{link_status\} =~ /down/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -471,7 +471,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -658,8 +658,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{progress\_status} =~ /in progress/i'). You can use the following variables: %{progress\_status}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /fail/i'). You can use the following variables: %{progress\_status}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{progress_status\} =~ /in progress/i'). You can use the following variables: %\{progress_status\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /fail/i'). You can use the following variables: %\{progress_status\}, %\{status\} | | --warning-* | Warning threshold. Can be: 'changes', 'last-save', 'save-size', 'last-save-duration', 'current-save-duration'. | | --critical-* | Critical threshold. Can be: 'changes', 'last-save', 'save-size', 'last-save-duration', 'current-save-duration'. | @@ -668,8 +668,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{sync\_status} =~ /in progress/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /down/i'). You can use the following variables: %{sync\_status}, %{link\_status}, %{cluster\_state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{sync_status\} =~ /in progress/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /down/i'). You can use the following variables: %\{sync_status\}, %\{link_status\}, %\{cluster_state\} | | --warning-* | Warning threshold. Can be: 'connected-slaves', 'master-repl-offset', 'master-last-io', 'slave-priority', 'slave-read-only'. | | --critical-* | Critical threshold. Can be: 'connected-slaves', 'master-repl-offset', 'master-last-io', 'slave-priority', 'slave-read-only'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-sap-hana.md b/pp/integrations/plugin-packs/procedures/applications-databases-sap-hana.md index 82e298498d6b..31cd6c445401 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-sap-hana.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-sap-hana.md @@ -438,7 +438,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md b/pp/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md index f9e1faf2198d..1f8fe5b6e5f0 100644 --- a/pp/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md +++ b/pp/integrations/plugin-packs/procedures/applications-databases-warp10-sensision.md @@ -373,7 +373,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-docker-restapi.md b/pp/integrations/plugin-packs/procedures/applications-docker-restapi.md index fb71269f0adf..a6e366f8c0dc 100644 --- a/pp/integrations/plugin-packs/procedures/applications-docker-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-docker-restapi.md @@ -221,8 +221,8 @@ yum install centreon-plugin-Applications-Docker-Restapi | CONTAINERID | Exact container ID | | | | CONTAINERNAME | Exact container name (if multiple names: names separated by ':') | | | | FILTERNAME | Filter by container name (can be a regexp) | | | -| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{state}, %{health} | | | -| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{state}, %{health} | | | +| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{state\}, %\{health\} | | | +| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{state\}, %\{health\} | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGMEMORY | Warning threshold | | | @@ -248,8 +248,8 @@ yum install centreon-plugin-Applications-Docker-Restapi | CRITICALCONTAINERSRUNNING | Critical threshold | | | | WARNINGCONTAINERSSTOPPED | Warning threshold | | | | CRITICALCONTAINERSSTOPPED | Critical threshold | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/'). You can use the following variables: %{display}, %{status}, %{manager\_status} | %{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/ | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %{display}, %{status}, %{manager\_status} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/'). You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\} | %\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/ | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -270,7 +270,7 @@ is able to monitor a resource using a command like this one (replace the sample --hostname='10.0.0.1' \ --port='' \ --warning-node-status='' \ - --critical-node-status='%{status} !~ /ready/ || %{manager_status} !~ /reachable|-/' \ + --critical-node-status='%\{status\} !~ /ready/ || %\{manager_status\} !~ /reachable|-/' \ --verbose ``` @@ -331,7 +331,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -403,8 +403,8 @@ All available options for each service template are listed below: | --no-stats | Don't get container statistics. | | --filter-name | Filter by container name (can be a regexp). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^container-status$' | -| --warning-container-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{state}, %{health}. | -| --critical-container-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{state}, %{health}. | +| --warning-container-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{state\}, %\{health\}. | +| --critical-container-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{state\}, %\{health\}. | | --warning-* --critical-* | Thresholds. Can be: 'read-iops', 'write-iops', 'traffic-in', 'traffic-out', 'cpu' (%), 'memory' (%). | @@ -412,8 +412,8 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-node-status | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %{display}, %{status}, %{manager\_status}. | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ready/ \|\| %{manager\_status} !~ /reachable\|-/'). You can use the following variables: %{display}, %{status}, %{manager\_status}. | +| --warning-node-status | Define the conditions to match for the status to be WARNING (default: -) You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\}. | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ready/ \|\| %\{manager_status\} !~ /reachable\|-/'). You can use the following variables: %\{display\}, %\{status\}, %\{manager_status\}. | | --warning-* | Warning threshold. Can be: 'containers-running', 'containers-paused', 'containers-stopped'. | | --critical-* | Critical threshold. Can be: 'containers-running', 'containers-paused', 'containers-stopped'., | diff --git a/pp/integrations/plugin-packs/procedures/applications-docker-ssh.md b/pp/integrations/plugin-packs/procedures/applications-docker-ssh.md index 0ee2748dd686..64b392c581a8 100644 --- a/pp/integrations/plugin-packs/procedures/applications-docker-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-docker-ssh.md @@ -196,8 +196,8 @@ yum install centreon-plugin-Applications-Docker-Ssh |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | FILTERID | Filter by container ID (can be a regexp) | | | | FILTERNAME | Filter by container name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -299,7 +299,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -348,8 +348,8 @@ All available options for each service template are listed below: |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by container name (can be a regexp). | | --filter-id | Filter by container ID (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{name} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{name\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md b/pp/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md index 7bde92ebdf3e..8f9781ad1886 100644 --- a/pp/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md +++ b/pp/integrations/plugin-packs/procedures/applications-dynamics-ax-mssql.md @@ -279,7 +279,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md b/pp/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md index 5ad70e465ba0..0ae2e88b001a 100644 --- a/pp/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md +++ b/pp/integrations/plugin-packs/procedures/applications-eclipse-mosquitto-mqtt.md @@ -259,13 +259,13 @@ yum install centreon-plugin-Applications-Eclipse-Mosquitto-MQTT | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------|:------------------|:---------:| -| FORMATOK | Threshold | value: %{value} | | -| FORMATUNKNOWN | Threshold | value: %{value} | | +| FORMATOK | Threshold | value: %\{value\} | | +| FORMATUNKNOWN | Threshold | value: %\{value\} | | | TOPIC | Topic value to check | | X | | FORMATCUSTOM | Apply a custom change on the value | | | | UNKNOWNREGEXP | | | | -| FORMATWARNING | Threshold | value: %{value} | | -| FORMATCRITICAL | Threshold | value: %{value} | | +| FORMATWARNING | Threshold | value: %\{value\} | | +| FORMATCRITICAL | Threshold | value: %\{value\} | | | WARNINGREGEXP | Return Warning if the topic value match the regexp | | | | CRITICALREGEXP | Return Critical if the topic value match the regexp | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -365,7 +365,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp.Example: adding --filter-perfdata='avg' will remove all metrics that do not contain'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables:label, value, unit, warning, critical, min, max.Variables must be written either %{variable} or %(variable).Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' willremove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables:label, value, unit, warning, critical, min, max.Variables must be written either %\{variable\} or %(variable).Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' willremove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The newmetric will be named identically with a '\_max' suffix).Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata.Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\]Common examples:=over 4Convert storage free perfdata into used: --change-perfdata='free,used,invert()'Convert storage free perfdata into used: --change-perfdata='used,free,invert()'Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)'Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps'Change traffic values in percent: --change-perfdata='traffic\_in,,percent()'=back | | --change-perfdata | Change or extend perfdata.Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\]Common examples:=over 4Convert storage free perfdata into used: --change-perfdata='free,used,invert()'Convert storage free perfdata into used: --change-perfdata='used,free,invert()'Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)'Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps'Change traffic values in percent: --change-perfdata='traffic\_in,,percent()'=back | @@ -458,7 +458,7 @@ All available options for each service template are listed below: | --warning-regexp | Return Warning if the topic value match the regexp. | | --critical-regexp | Return Critical if the topic value match the regexp. | | --regexp-insensitive | Allows to use case-insensitive regexp. | -| --format-* | Output format according to the threshold.Can be:'ok' (default: 'value: %{value}'),'warning' (default: 'value: %{value}'),'critical' (default: 'value: %{value}'),'unknown' (default: 'value: %{value}'). | +| --format-* | Output format according to the threshold.Can be:'ok' (default: 'value: %\{value\}'),'warning' (default: 'value: %\{value\}'),'critical' (default: 'value: %\{value\}'),'unknown' (default: 'value: %\{value\}'). | diff --git a/pp/integrations/plugin-packs/procedures/applications-google-workspace-api.md b/pp/integrations/plugin-packs/procedures/applications-google-workspace-api.md index 3b2f394c02a2..0df5f0ae524d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-google-workspace-api.md +++ b/pp/integrations/plugin-packs/procedures/applications-google-workspace-api.md @@ -121,8 +121,8 @@ by running the following command (Some of the parameters such as ```proxyurl``` --port='443' \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-name='mail|drive|meet' \ - --warning-status='%{status} eq "disruption"' \ - --critical-status='%{status} eq "outage"' \ + --warning-status='%\{status\} eq "disruption"' \ + --critical-status='%\{status\} eq "outage"' \ --verbose ``` diff --git a/pp/integrations/plugin-packs/procedures/applications-gorgone-restapi.md b/pp/integrations/plugin-packs/procedures/applications-gorgone-restapi.md index 9139110bf03e..8eee0313d66c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-gorgone-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-gorgone-restapi.md @@ -291,7 +291,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-grafana-api.md b/pp/integrations/plugin-packs/procedures/applications-grafana-api.md index 3ba5ec167b47..f2280bb6aff9 100644 --- a/pp/integrations/plugin-packs/procedures/applications-grafana-api.md +++ b/pp/integrations/plugin-packs/procedures/applications-grafana-api.md @@ -161,8 +161,8 @@ yum install centreon-plugin-Applications-Grafana-Api | Macro | Description | Default value | Mandatory | |:---------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "ok"'). You can use the following variables: %{state}, %{version} | %{state} ne "ok" | | -| WARNING | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{version} | | | +| CRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "ok"'). You can use the following variables: %\{state\}, %\{version\} | %\{state\} ne "ok" | | +| WARNING | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{version\} | | | @@ -185,7 +185,7 @@ is able to monitor a resource using a command like this one (replace the sample --username='' \ --password='' \ --warning-status='' \ - --critical-status='%{state} ne "ok"' + --critical-status='%\{state\} ne "ok"' ``` The expected command output is shown below: @@ -244,7 +244,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -276,8 +276,8 @@ All available options for each service template are listed below: | --http-backend | Perl library to use for HTTP transactions. Possible values are: lwp (default) and curl. | | --ssl-opt | Set SSL Options (--ssl-opt="SSL\_version =\> TLSv1" --ssl-opt="SSL\_verify\_mode =\> SSL\_VERIFY\_NONE"). | | --curl-opt | Set CURL Options (--curl-opt="CURLOPT\_SSL\_VERIFYPEER =\> 0" --curl-opt="CURLOPT\_SSLVERSION =\> CURL\_SSLVERSION\_TLSv1\_1" ). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{version} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "ok"'). You can use the following variables: %{state}, %{version} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{version\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "ok"'). You can use the following variables: %\{state\}, %\{version\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-haproxy-snmp.md b/pp/integrations/plugin-packs/procedures/applications-haproxy-snmp.md index 05e386bf89b4..69df23f8a93c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-haproxy-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-haproxy-snmp.md @@ -119,7 +119,7 @@ I> When using SNMP v3, use the SNMPEXTRAOPTIONS Macro to add specific authentica --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /OPEN/i' \ + --critical-status='%\{status\} !~ /OPEN/i' \ --warning-total-sessions='' \ --critical-total-sessions='' \ --warning-current-sessions='' \ diff --git a/pp/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md b/pp/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md index eed8b76b06ef..12393bc79fd5 100644 --- a/pp/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-hashicorp-vault-restapi.md @@ -195,9 +195,9 @@ yum install centreon-plugin-Applications-HashiCorp-Vault-Restapi | Macro | Description | Default value | Mandatory | |:-------------------|:---------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| CRITICALINITSTATUS | Set critical threshold for initialization status (default: '%{init} ne "initialized"') | %{init} ne "initialized" | | +| CRITICALINITSTATUS | Set critical threshold for initialization status (default: '%\{init\} ne "initialized"') | %\{init\} ne "initialized" | | | WARNINGINITSTATUS | Set warning threshold for initialization status (default: none) | | | -| CRITICALSEALSTATUS | Set critical threshold for seal status (default: '%{sealed} ne "unsealed"') | %{sealed} ne "unsealed" | | +| CRITICALSEALSTATUS | Set critical threshold for seal status (default: '%\{sealed\} ne "unsealed"') | %\{sealed\} ne "unsealed" | | | WARNINGSEALSTATUS | Set warning threshold for seal status (default: none) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -302,7 +302,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -360,9 +360,9 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:-------------------------------------------------------------------------------------------| | --warning-seal-status | Set warning threshold for seal status (default: none). | -| --critical-seal-status | Set critical threshold for seal status (default: '%{sealed} ne "unsealed"'). | +| --critical-seal-status | Set critical threshold for seal status (default: '%\{sealed\} ne "unsealed"'). | | --warning-init-status | Set warning threshold for initialization status (default: none). | -| --critical-init-status | Set critical threshold for initialization status (default: '%{init} ne "initialized"'). | +| --critical-init-status | Set critical threshold for initialization status (default: '%\{init\} ne "initialized"'). | diff --git a/pp/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md b/pp/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md index b24eb79108cb..00fa023b8c82 100644 --- a/pp/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md +++ b/pp/integrations/plugin-packs/procedures/applications-hddtemp-tcp.md @@ -27,7 +27,7 @@ It brings the following Service Template: | Metric Name | Unit | |:-----------------------------------------|:------------------------| | status | string | -| drive_name#drive.temperature. | celsius or fahrenheit | +| drive_name#drive.temperature.\ | celsius or fahrenheit | @@ -100,7 +100,7 @@ command: --filter-name='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /ok/i' \ + --critical-status='%\{status\} !~ /ok/i' \ --warning-temperature='30' \ --critical-temperature='50' \ --verbose \ diff --git a/pp/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md b/pp/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md index 0f13dd25980a..ac97dd08d3d9 100644 --- a/pp/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-infor-ion-grid-restapi.md @@ -192,8 +192,8 @@ yum install centreon-plugin-Applications-Infor-Ion-Grid-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| | FILTERNAME | Filter by application name (regexp can be used). Example: --filter-name='^application1$' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{online} =~ /true/ && %{state} !~ /^(OK)/i'). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --critical-status='%{started} ne "true"' | %{online} =~ /true/ && %{state} !~ /^(OK)/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --warning-status='%{state} ne "OK"' | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i'). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --critical-status='%\{started\} ne "true"' | %\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --warning-status='%\{state\} ne "OK"' | | | | WARNINGTOTAL | Define the conditions to match for the total to be WARNING (default: ''). | | | | CRITICALTOTAL | Define the conditions to match for the total to be CRITICAL (default: ''). | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -215,8 +215,8 @@ yum install centreon-plugin-Applications-Infor-Ion-Grid-Restapi | CRITICALLOGWARNING | Set critical thresholds on log-warning | | | | WARNINGLOGERROR | Set warning thresholds on log-error | | | | CRITICALLOGERROR | Set critical thresholds on log-error | | | -| CRITICALSTATUS | Set critical threshold for status. Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type} | '%{state} !~ /online/' | | -| WARNINGSTATUS | Set warning threshold for status (Default: "%{state} !~ /online/"). Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status. Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\} | '%\{state\} !~ /online/' | | +| WARNINGSTATUS | Set warning threshold for status (Default: "%\{state\} !~ /online/"). Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\} | | | | WARNINGUPTIME | Set warning thresholds on uptime | | | | CRITICALUPTIME |Set critical thresholds on uptime | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -245,8 +245,8 @@ is able to monitor a resource using a command like this one (replace the sample --filter-type='' \ --filter-application-name='^SYSTEM$' \ --filter-host-name='^THEHOST$' \ - --warning-status='%{state} !~ /online/' \ - --critical-status=''%{state} !~ /online/'' \ + --warning-status='%\{state\} !~ /online/' \ + --critical-status=''%\{state\} !~ /online/'' \ --warning-log-error='' \ --critical-log-error='' \ --warning-log-warning='' \ @@ -316,7 +316,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -359,8 +359,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by application name (regexp can be used). Example: --filter-name='^application1$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --warning-status='%{state} ne "OK"' | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{online} =~ /true/ && %{state} !~ /^(OK)/i'). Threshold can be matched on special variables like %{state}, %{online}, %{started}, %{name} or %{description} and Regexp can be used. Typical syntax: --critical-status='%{started} ne "true"' | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --warning-status='%\{state\} ne "OK"' | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{online\} =~ /true/ && %\{state\} !~ /^(OK)/i'). Threshold can be matched on special variables like %\{state\}, %\{online\}, %\{started\}, %\{name\} or %\{description\} and Regexp can be used. Typical syntax: --critical-status='%\{started\} ne "true"' | | --warning-total | Define the conditions to match for the total to be WARNING (default: ''). | | --critical-total | Define the conditions to match for the total to be CRITICAL (default: ''). | @@ -373,8 +373,8 @@ All available options for each service template are listed below: | --filter-name | Filter by node name. | | --filter-application-name | Filter by application name. | | --filter-host-name | Filter by host name. | -| --warning-status | Set warning threshold for status (Default: "%{state} !~ /online/"). Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type}. | -| --critical-status | Set critical threshold for status. Can use special variables like: %{state}, %{name}, %{host\_name}, %{application\_name}, %{type}. | +| --warning-status | Set warning threshold for status (Default: "%\{state\} !~ /online/"). Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\}. | +| --critical-status | Set critical threshold for status. Can use special variables like: %\{state\}, %\{name\}, %\{host_name\}, %\{application_name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'log-error', 'log-warning', 'uptime' (s), 'cpu-usage', 'heap-usage' (%). | diff --git a/pp/integrations/plugin-packs/procedures/applications-ipfabric-api.md b/pp/integrations/plugin-packs/procedures/applications-ipfabric-api.md index 676fe0feec35..3b5c302b4093 100644 --- a/pp/integrations/plugin-packs/procedures/applications-ipfabric-api.md +++ b/pp/integrations/plugin-packs/procedures/applications-ipfabric-api.md @@ -192,8 +192,8 @@ yum install centreon-plugin-Applications-Ipfabric-Api | CRITICALPATHSSTATENONE | Thresholds | | | | WARNINGPATHSSTATEPART | Thresholds | | | | CRITICALPATHSSTATEPART | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%{expected\_state} ne %{state}'). Can use special variables like: %{state}, %{expected\_state} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%{state} eq 'all'" | %{expected\_state} ne %{state} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{state}, %{expected\_state} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%{state} eq 'all'" | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expected_state\} ne %\{state\}'). Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%\{state\} eq 'all'" | %\{expected_state\} ne %\{state\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%\{state\} eq 'all'" | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --http-backend=curl | | @@ -317,7 +317,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -353,8 +353,8 @@ All available options for each service template are listed below: | --filter-src-port | Filter paths by source port (regexp can be used). | | --filter-dst-ip | Filter paths by destionation ip (regexp can be used). | | --filter-dst-port | Filter paths by destionation port (regexp can be used). | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{state}, %{expected\_state} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%{state} eq 'all'" | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{expected\_state} ne %{state}'). Can use special variables like: %{state}, %{expected\_state} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%{state} eq 'all'" | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a warning alert when the path state is in 'error' then the option would be: --warning-status="%\{state\} eq 'all'" | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expected_state\} ne %\{state\}'). Can use special variables like: %\{state\}, %\{expected_state\} For example, if you want a critical alert when the path state is in 'error' then the option would be: --critical-status="%\{state\} eq 'all'" | | --warning-* --critical-* | Thresholds. Can be: 'paths-detected', 'paths-mismatch', 'paths-state-all', 'paths-state-part', 'paths-state-none', 'paths-state-error'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-jmeter.md b/pp/integrations/plugin-packs/procedures/applications-jmeter.md index d2843c35307d..93fd36fbfcb4 100644 --- a/pp/integrations/plugin-packs/procedures/applications-jmeter.md +++ b/pp/integrations/plugin-packs/procedures/applications-jmeter.md @@ -253,7 +253,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/applications-keepalived-snmp.md b/pp/integrations/plugin-packs/procedures/applications-keepalived-snmp.md index 0f5b94bff290..00fdd834d806 100644 --- a/pp/integrations/plugin-packs/procedures/applications-keepalived-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-keepalived-snmp.md @@ -179,8 +179,8 @@ yum install centreon-plugin-Applications-Keepalived-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{instanceState} ne %{instanceWantedState} or %{instanceState} ne %{instanceStateLast}'). You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{instanceState\} ne %\{instanceWantedState\} or %\{instanceState\} ne %\{instanceStateLast\}'). You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -259,7 +259,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -315,8 +315,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{instanceState} ne %{instanceWantedState} or %{instanceState} ne %{instanceStateLast}'). You can use the following variables: %{instanceWantedState}, %{instanceStateLast}, %{instanceState}, %{instancePrimaryInterface} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{instanceState\} ne %\{instanceWantedState\} or %\{instanceState\} ne %\{instanceStateLast\}'). You can use the following variables: %\{instanceWantedState\}, %\{instanceStateLast\}, %\{instanceState\}, %\{instancePrimaryInterface\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md b/pp/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md index 26d61141a713..86c3277075c1 100644 --- a/pp/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-lmsensors-snmp.md @@ -258,7 +258,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md b/pp/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md index c75c72c75f27..3221525705b9 100644 --- a/pp/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-microsoft-dhcp-snmp.md @@ -286,7 +286,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -332,9 +332,9 @@ All available options for each service template are listed below: | --snmp-tls-trust-cert | A trusted CA certificate used to verify a remote host's certificate. If you use this option, you must also define --snmp-tls-their-hostname. | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='pending' | | --filter-subnet-address | Filter subnets by address (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'addresses-usage', 'addresses-usage-free', 'addresses-usage-prct', 'pending-offers'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md index b61030eeee7a..bc4a434f60f9 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-alyvix-restapi.md @@ -138,8 +138,8 @@ by running the following command (some of the parameters such as ```--proxyurl`` --port='80' \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-testcase='case_app1|case_app2' \ - --critical-testcase-state='%{state} eq "FAILED"' \ - --critical-transaction-state='%{state} eq "FAILED"' \ + --critical-testcase-state='%\{state\} eq "FAILED"' \ + --critical-transaction-state='%\{state\} eq "FAILED"' \ --warning-testcase-duration='40000' \ --critical-testcase-duration='60000' \ --critical-testcase-freshness='600' \ diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md index bb69273fda7e..1c8eb6bfd5f3 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-central.md @@ -359,8 +359,8 @@ yum install centreon-plugin-Applications-Monitoring-Centreon-Central | CRITICALQUEUEDEVENTS | Thresholds | | | | WARNINGSPEEDEVENTS | Thresholds | | | | CRITICALSPEEDEVENTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | %{type} eq "output" and %{queue\_file\_enabled} =~ /true\|yes/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{type\} eq "output" and %\{queue_file_enabled\} =~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | %\{type\} eq "output" and %\{queue_file_enabled\} =~ /true\|yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | | | | WARNINGUNACKNOWLEDGEDEVENTS | Thresholds | | | | CRITICALUNACKNOWLEDGEDEVENTS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -607,7 +607,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -654,8 +654,8 @@ All available options for each service template are listed below: | --broker-stats-file | Specify the centreon-broker json stats file (Required). Can be multiple. | | --filter-name | Filter endpoint name. | | --warning-* --critical-* | Thresholds. Can be: 'speed-events', 'queued-events', 'unacknowledged-events'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{type\} eq "output" and %\{queue_file_enabled\} =~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md index 1b61fc24e6b9..2c964f8744d4 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-database.md @@ -303,7 +303,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md index 7a0e6d36bfe5..71d259a1815f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-map-engine-actuator.md @@ -404,7 +404,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md index c986beed6fb0..e01e860d2ae9 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi.md @@ -77,11 +77,11 @@ With the `root` user, install the following package and its dependencies: Try to execute this command: - $ snmpwalk -v 1 -c .1.3.6.1.2.1.1.1 + $ snmpwalk -v 1 -c \ \ .1.3.6.1.2.1.1.1 You should get a response looking like the following: - SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 + SNMPv2-MIB::sysDescr.0 = STRING: Linux \ 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 ### SNMP Permissions diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md index fc6a101892ea..f296dff524cf 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-poller.md @@ -239,8 +239,8 @@ yum install centreon-plugin-Applications-Monitoring-Centreon-Poller | CRITICALQUEUEDEVENTS | Thresholds | | | | WARNINGSPEEDEVENTS | Thresholds | | | | CRITICALSPEEDEVENTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | %{type} eq "output" and %{queue\_file\_enabled} =~ /true\|yes/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "output" and %\{queue_file_enabled\} =~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | %\{type\} eq "output" and %\{queue_file_enabled\} =~ /true\|yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | | | | WARNINGUNACKNOWLEDGEDEVENTS | Thresholds | | | | CRITICALUNACKNOWLEDGEDEVENTS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --ssh-username='centreon' | | @@ -318,7 +318,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-unacknowledged-events='' \ --critical-unacknowledged-events='' \ --warning-status='' \ - --critical-status='%{type} eq "output" and %{queue_file_enabled} =~ /true|yes/i' \ + --critical-status='%\{type\} eq "output" and %\{queue_file_enabled\} =~ /true|yes/i' \ --verbose \ --ssh-username='centreon' ``` @@ -402,7 +402,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale"Mbps",mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -449,8 +449,8 @@ All available options for each service template are listed below: | --broker-stats-file | Specify the centreon-broker json stats file (required). Can be multiple. | | --filter-name | Filter endpoint name. | | --warning-* --critical-* | Thresholds. Can be: 'speed-events', 'queued-events', 'unacknowledged-events'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "output" and %{queue\_file\_enabled} =~ /yes/i'). You can use the following variables: %{queue\_file\_enabled}, %{state}, %{status}, %{type}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "output" and %\{queue_file_enabled\} =~ /yes/i'). You can use the following variables: %\{queue_file_enabled\}, %\{state\}, %\{status\}, %\{type\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md index eb252dc987d8..4c9fd12b6131 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-sql-metrics.md @@ -451,7 +451,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale"Mbps",mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md index 13bbfe85112b..1a4154533fb7 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-iplabel-newtest-restapi.md @@ -316,7 +316,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md index 751bb531ea89..7410e1e32122 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-kadiska-restapi.md @@ -733,7 +733,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md index 9299537f01f1..29d8f220f178 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-loggly-restapi.md @@ -283,7 +283,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md index c6dbe406152d..675bc2abc00b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-linux.md @@ -384,7 +384,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md index 051479f027fd..8e6c3d53c43d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-node-exporter-windows.md @@ -256,8 +256,8 @@ yum install centreon-plugin-Applications-Monitoring-Nodeexporter-Windows | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------|:-----------:| | SERVICENAME | Specify which service to monitor. Can be a regex. Default: all services are monitored | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{start\_mode} =~ /auto/ && %{status} !~ /^running$/'). You can use the following variables: %{status}, %{start\_mode} | %{start\_mode} =~ /auto/ && %{status} !~ /^running$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{start\_mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/'). You can use the following variables: %\{status\}, %\{start_mode\} | %\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{start_mode\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -381,7 +381,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -456,8 +456,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --service | Specify which service to monitor. Can be a regex. Default: all services are monitored. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{start\_mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{start\_mode} =~ /auto/ && %{status} !~ /^running$/'). You can use the following variables: %{status}, %{start\_mode} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{start_mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{start_mode\} =~ /auto/ && %\{status\} !~ /^running$/'). You can use the following variables: %\{status\}, %\{start_mode\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md index 6d1e32f97170..0550caa64930 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-quanta-restapi.md @@ -262,7 +262,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md index 86f3f36ff322..08c5e696a7f2 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-scom-restapi.md @@ -184,8 +184,8 @@ yum install centreon-plugin-Applications-Monitoring-Scom-Restapi | CRITICALRESOLVED | Threshold | | | | WARNINGSCHEDULED | Threshold | | | | CRITICALSCHEDULED | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | %{severity} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | %{severity} =~ /critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -210,8 +210,8 @@ is able to monitor a resource using a command like this one (replace the sample --port='80' \ --proto='http' \ --filter-host='' \ - --warning-status='%{severity} =~ /warning/i' \ - --critical-status='%{severity} =~ /critical/i' \ + --warning-status='%\{severity\} =~ /warning/i' \ + --critical-status='%\{severity\} =~ /critical/i' \ --warning-new='' \ --critical-new='' \ --warning-closed='' \ @@ -287,8 +287,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-host | Filter by host name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning/i') You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical/i'). You can use the following variables: %{severity}, %{host}, %{name}, %{timeraised} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning/i') You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical/i'). You can use the following variables: %\{severity\}, %\{host\}, %\{name\}, %\{timeraised\} | | --warning-* --critical-* | Thresholds. Can be: 'new', 'closed', 'resolved', 'scheduled', 'awaiting-evidence', 'assigned-to-engineering', 'acknowledge'. | | --memory | Only check new alarms. | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | @@ -303,7 +303,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md index 0510af628199..1cda438d41ff 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-speedtest.md @@ -248,7 +248,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md b/pp/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md index 6b2c91a3e876..1237c4770072 100644 --- a/pp/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md +++ b/pp/integrations/plugin-packs/procedures/applications-monitoring-splunk-api.md @@ -213,16 +213,16 @@ yum install centreon-plugin-Applications-Monitoring-Splunk-Api | Macro | Description | Default value | Mandatory | |:---------------------------------|:---------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGFILEMONITORINPUTSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALFILEMONITORINPUTSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGINDEXPROCESSORSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALINDEXPROCESSORSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGRESOURCEUSAGESTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALRESOURCEUSAGESTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGSEARCHSCHEDULERSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALSEARCHSCHEDULERSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | -| WARNINGWORKLOADMANAGEMENTSTATUS | Warning thresholds for features status. (default: '%{status} =~ /yellow/') | | | -| CRITICALWORKLOADMANAGEMENTSTATUS | Critical thresholds for features status. (default: '%{status} =~ /red/') | | | +| WARNINGFILEMONITORINPUTSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALFILEMONITORINPUTSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGINDEXPROCESSORSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALINDEXPROCESSORSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGRESOURCEUSAGESTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALRESOURCEUSAGESTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGSEARCHSCHEDULERSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALSEARCHSCHEDULERSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | +| WARNINGWORKLOADMANAGEMENTSTATUS | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/') | | | +| CRITICALWORKLOADMANAGEMENTSTATUS | Critical thresholds for features status. (default: '%\{status\} =~ /red/') | | | @@ -304,7 +304,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,8 +378,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Warning thresholds for features status. (default: '%{status} =~ /yellow/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | -| --critical-* | Critical thresholds for features status. (default: '%{status} =~ /red/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | +| --warning-* | Warning thresholds for features status. (default: '%\{status\} =~ /yellow/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | +| --critical-* | Critical thresholds for features status. (default: '%\{status\} =~ /red/'). Can be: 'file-monitor-input-status', 'index-processor-status', 'resource-usage-status', 'search-scheduler-status', 'workload-management-status' | diff --git a/pp/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md b/pp/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md index e0bef87e9360..a180d5591cb8 100644 --- a/pp/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-mulesoft-restapi.md @@ -155,8 +155,8 @@ Once the Plugin installed, log into your poller using the *centreon-engine* user --api-username='myapiuser' \ --api-password='myapipassword' \ --filter-name='myapplication1' \ - --warning-status='%{status} =~ /STOPPED/' \ - --critical-status='%{status} =~ /FAILED/' \ + --warning-status='%\{status\} =~ /STOPPED/' \ + --critical-status='%\{status\} =~ /FAILED/' \ --verbose diff --git a/pp/integrations/plugin-packs/procedures/applications-netbackup-ssh.md b/pp/integrations/plugin-packs/procedures/applications-netbackup-ssh.md index c16d84f18ee3..ee0ac2fb1017 100644 --- a/pp/integrations/plugin-packs/procedures/applications-netbackup-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-netbackup-ssh.md @@ -187,7 +187,7 @@ Once the Plugin is installed, log into your Poller using the **centreon-engine** --ssh-username=centreon \ --ssh-password='centreon-password' \ --ssh-backend=sshcli \ - --critical-status='%{status} !~ /up/i' \ + --critical-status='%\{status\} !~ /up/i' \ --verbose ``` diff --git a/pp/integrations/plugin-packs/procedures/applications-openldap-ldap.md b/pp/integrations/plugin-packs/procedures/applications-openldap-ldap.md index ba2ddb4acffe..daa522946c84 100644 --- a/pp/integrations/plugin-packs/procedures/applications-openldap-ldap.md +++ b/pp/integrations/plugin-packs/procedures/applications-openldap-ldap.md @@ -280,7 +280,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-openvpn-omi.md b/pp/integrations/plugin-packs/procedures/applications-openvpn-omi.md index 747c0e882957..6bc9954ac830 100644 --- a/pp/integrations/plugin-packs/procedures/applications-openvpn-omi.md +++ b/pp/integrations/plugin-packs/procedures/applications-openvpn-omi.md @@ -255,7 +255,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md b/pp/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md index 282aa0804d27..4ccf71167bba 100644 --- a/pp/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-openweathermap-restapi.md @@ -16,7 +16,7 @@ yum install centreon-plugin-Applications-Openweathermap-Restapi ### API token A token is mandatory to access the API. More information can be found on the -official OpenWeatherMap website : . +official OpenWeatherMap website : \. ## Centreon Configuration diff --git a/pp/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md b/pp/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md index aa00a45b9246..5436ec35dc1f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md +++ b/pp/integrations/plugin-packs/procedures/applications-oracle-ovm-api.md @@ -231,8 +231,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCEEDED | Thresholds | | | | CRITICALJOBSSUCCEEDED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /running/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /running/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -273,8 +273,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | CRITICALSERVERSRUNNING | Thresholds | | | | WARNINGSERVERSSTOPPED | Thresholds | | | | CRITICALSERVERSSTOPPED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -283,8 +283,8 @@ yum install centreon-plugin-Applications-Oracle-Ovm-Api | Macro | Description | Default value | Mandatory | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter virtual machines by name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{name\} | | | | WARNINGVMRUNNING | Thresholds | | | | CRITICALVMRUNNING | Thresholds | | | | WARNINGVMSTOPPED | Thresholds | | | @@ -386,7 +386,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -439,9 +439,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-succeeded', 'jobs-failed'. | @@ -460,9 +460,9 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | | --filter-name | Filter servers by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{is\_maintenance}, %{up2date}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{is_maintenance\}, %\{up2date\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'servers-running', 'servers-stopped', 'memory-usage' (B), 'memory-usage-free' (B), 'memory-usage-prct' (%). | @@ -472,9 +472,9 @@ All available options for each service template are listed below: |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter virtual machines by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{running\_status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{running_status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'vm-running', 'vm-stopped'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md b/pp/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md index 925b7617dff8..c071f378ad2f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-pacemaker-ssh.md @@ -220,26 +220,26 @@ yum install centreon-plugin-Applications-Pacemaker-Ssh | CRITICALCLONERESOURCEACTIONSFAILED | Thresholds | | | | WARNINGCLONERESOURCEMIGRATIONFAILED | Thresholds | | | | CRITICALCLONERESOURCEMIGRATIONFAILED | Thresholds | | | -| CRITICALCLONERESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | %{status} =~ /failed/i | | -| WARNINGCLONERESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | | | +| CRITICALCLONERESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | %\{status\} =~ /failed/i | | +| WARNINGCLONERESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | | | | CRITICALCLUSTERACTIONSFAILED | Thresholds | 0 | | | WARNINGCLUSTERACTIONSFAILED | Thresholds | | | -| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /failed/i'). You can use the following variables: %{connection\_status}, %{connection\_error} | %{connection\_status} =~ /failed/i | | -| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_status}, %{connection\_error} | | | +| CRITICALCONNECTIONSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /failed/i'). You can use the following variables: %\{connection_status\}, %\{connection_error\} | %\{connection_status\} =~ /failed/i | | +| WARNINGCONNECTIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_status\}, %\{connection_error\} | | | | CRITICALNODESOFFLINE | Thresholds | 0 | | | WARNINGNODESOFFLINE | Thresholds | | | | WARNINGNODESONLINE | Thresholds | | | | CRITICALNODESONLINE | Thresholds | | | | WARNINGNODESSTANDBY | Thresholds | | | | CRITICALNODESSTANDBY | Thresholds | | | -| CRITICALQUORUMSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{quorum\_status} =~ /noQuorum/i'). You can use the following variables: %{quorum\_status} | %{quorum\_status} =~ /noQuorum/i | | -| WARNINGQUORUMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{quorum\_status} | | | +| CRITICALQUORUMSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{quorum_status\} =~ /noQuorum/i'). You can use the following variables: %\{quorum_status\} | %\{quorum_status\} =~ /noQuorum/i | | +| WARNINGQUORUMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{quorum_status\} | | | | WARNINGRESOURCEACTIONSFAILED | Thresholds | | | | CRITICALRESOURCEACTIONSFAILED | Thresholds | | | | CRITICALRESOURCEMIGRATIONFAILED | Thresholds | 0 | | | WARNINGRESOURCEMIGRATIONFAILED | Thresholds | | | -| CRITICALRESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /stopped\|failed/i'). You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | %{status} =~ /stopped\|failed/i | | -| WARNINGRESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | | | +| CRITICALRESOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /stopped\|failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | %\{status\} =~ /stopped\|failed/i | | +| WARNINGRESOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -287,23 +287,23 @@ is able to monitor a resource using a command like this one (replace the sample --warning-nodes-standby='' \ --critical-nodes-standby='' \ --warning-clone-resource-status='' \ - --critical-clone-resource-status='%{status} =~ /failed/i' \ + --critical-clone-resource-status='%\{status\} =~ /failed/i' \ --warning-clone-resource-actions-failed='' \ --critical-clone-resource-actions-failed='' \ --warning-clone-resource-migration-failed='' \ --critical-clone-resource-migration-failed='' \ --warning-connection-status='' \ - --critical-connection-status='%{connection_status} =~ /failed/i' \ + --critical-connection-status='%\{connection_status\} =~ /failed/i' \ --warning-cluster-actions-failed='' \ --critical-cluster-actions-failed='0' \ --warning-resource-status='' \ - --critical-resource-status='%{status} =~ /stopped|failed/i' \ + --critical-resource-status='%\{status\} =~ /stopped|failed/i' \ --warning-resource-actions-failed='' \ --critical-resource-actions-failed='' \ --warning-resource-migration-failed='' \ --critical-resource-migration-failed='0' \ --warning-quorum-status='' \ - --critical-quorum-status='%{quorum_status} =~ /noQuorum/i' \ + --critical-quorum-status='%\{quorum_status\} =~ /noQuorum/i' \ --verbose ``` @@ -362,7 +362,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -410,14 +410,14 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-resource-name | Filter resource (also clone resource) by name (can be a regexp). | -| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_status}, %{connection\_error} | -| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /failed/i'). You can use the following variables: %{connection\_status}, %{connection\_error} | -| --warning-quorum-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{quorum\_status} | -| --critical-quorum-status | Define the conditions to match for the status to be CRITICAL (default: '%{quorum\_status} =~ /noQuorum/i'). You can use the following variables: %{quorum\_status} | -| --warning-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | -| --critical-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /stopped\|failed/i'). You can use the following variables: %{name}, %{status}, %{node}, %{is\_unmanaged} | -| --warning-clone-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | -| --critical-clone-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{name}, %{status}, %{masters\_nodes\_name}, %{slaves\_nodes\_name}, %{is\_unmanaged} | +| --warning-connection-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_status\}, %\{connection_error\} | +| --critical-connection-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /failed/i'). You can use the following variables: %\{connection_status\}, %\{connection_error\} | +| --warning-quorum-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{quorum_status\} | +| --critical-quorum-status | Define the conditions to match for the status to be CRITICAL (default: '%\{quorum_status\} =~ /noQuorum/i'). You can use the following variables: %\{quorum_status\} | +| --warning-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | +| --critical-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /stopped\|failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{node\}, %\{is_unmanaged\} | +| --warning-clone-resource-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | +| --critical-clone-resource-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{name\}, %\{status\}, %\{masters_nodes_name\}, %\{slaves_nodes_name\}, %\{is_unmanaged\} | | --ignore-failed-actions | Failed actions errors (that match) are skipped. | | --resources | If resources not started on the node specified, send a warning message: (format: \:\,\:\,...) | | --warning-* --critical-* | Thresholds. Can be: 'cluster-actions-failed', 'clone-resource-actions-failed', 'clone-resource-migration-failed', 'nodes-online', 'nodes-offline', 'nodes-standby', 'resource-actions-failed', 'resource-migration-failed'. | @@ -428,7 +428,7 @@ All available options for each service template are listed below: | Option | Description | |:-------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* | Can be ('group','node') Define the conditions to match for the status to be WARNING. | -| --critical-* | Can be ('group','node') Define the conditions to match for the status to be CRITICAL. (default: --critical-node '%{state} !~ /up\|clean/' --critical-group '%{state} !~ /started\|starting/') | +| --critical-* | Can be ('group','node') Define the conditions to match for the status to be CRITICAL. (default: --critical-node '%\{state\} !~ /up\|clean/' --critical-group '%\{state\} !~ /started\|starting/') | diff --git a/pp/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md b/pp/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md index 60961f36a0f1..b95734e767ef 100644 --- a/pp/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-pfsense-fauxapi.md @@ -223,8 +223,8 @@ yum install centreon-plugin-Applications-Pfsense-Fauxapi | CRITICALPACKETSLOSS | Thresholds | | | | WARNINGPACKETSSTDDEV | Thresholds | | | | CRITICALPACKETSSTDDEV | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /none/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /none/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /none/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /none/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -334,7 +334,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -386,9 +386,9 @@ All available options for each service template are listed below: |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter gateway name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /none/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /none/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'packets-delay' (ms), 'packets-loss' (%), 'packets-stddev' (ms). | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md index 4d37d22f0827..e76aebdd27e2 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-bgp-snmp.md @@ -184,8 +184,8 @@ yum install centreon-plugin-Applications-Protocol-Bgp-Snmp | FILTERAS | Filter based on AS number (regexp allowed) | .* | | | FILTERPEER | Filter based on IP of peers (regexp allowed) | .* | | | CRITCALUPDATES | Critical threshold on last update (seconds) | | | -| CRITICALSTATUS | Specify admin and peer state that trigger a critical. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '%{adminstate} =~ /start/ && %{peerstate} !~ /established/') | %{adminstate} !~ /stop/ and %{peerstate} !~ /established/ | | -| WARNINGSTATUS | Specify admin and peer state that trigger a warning. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '') | | | +| CRITICALSTATUS | Specify admin and peer state that trigger a critical. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '%\{adminstate\} =~ /start/ && %\{peerstate\} !~ /established/') | %\{adminstate\} !~ /stop/ and %\{peerstate\} !~ /established/ | | +| WARNINGSTATUS | Specify admin and peer state that trigger a warning. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '') | | | | WARNINGUPDATES | Warning threshold on last update (seconds) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --filter-perfdata '^(?!(seconds))' | | @@ -212,7 +212,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-updates '' \ --critical-updates '' \ --warning-status '' \ - --critical-status '%{adminstate} !~ /stop/ and %{peerstate} !~ /established/' \ + --critical-status '%\{adminstate\} !~ /stop/ and %\{peerstate\} !~ /established/' \ --verbose \ --filter-perfdata '^(?!(seconds))' ``` @@ -270,7 +270,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -318,8 +318,8 @@ All available options for each service template are listed below: | --filter-peer | Filter based on IP of peers (regexp allowed) | | --warning-updates | Warning threshold on last update (seconds) | | --critical-updates | Critical threshold on last update (seconds) | -| --warning-status | Specify admin and peer state that trigger a warning. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '') | -| --critical-status | Specify admin and peer state that trigger a critical. Can use special variables like %{adminstate}, %{peerstate}, %{local}, %{remote}, %{as}, %{display} (default: '%{adminstate} =~ /start/ && %{peerstate} !~ /established/') | +| --warning-status | Specify admin and peer state that trigger a warning. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '') | +| --critical-status | Specify admin and peer state that trigger a critical. Can use special variables like %\{adminstate\}, %\{peerstate\}, %\{local\}, %\{remote\}, %\{as\}, %\{display\} (default: '%\{adminstate\} =~ /start/ && %\{peerstate\} !~ /established/') | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-cifs.md b/pp/integrations/plugin-packs/procedures/applications-protocol-cifs.md index b00799744b0c..b13c3883bf68 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-cifs.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-cifs.md @@ -208,8 +208,8 @@ yum install centreon-plugin-Applications-Protocol-Cifs | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| | DIRECTORY | Set the share directory. | | X | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | %{message} !~ /authentication succeeded/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | %\{message\} !~ /authentication succeeded/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGTIME | Warning threshold in seconds. | | | | CRITICALTIME | Critical threshold in seconds. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -257,10 +257,10 @@ yum install centreon-plugin-Applications-Protocol-Cifs | SCENARIO | Scenario used. Can be a file or json content. | | X | | WARNINGERRORS | Thresholds. | | | | CRITICALERRORS | Thresholds. | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}. | %{status} ne "success" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | | | -| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | -| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}. | %\{status\} ne "success" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | | | +| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | +| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGSTEPTIME | Thresholds. | | | | CRITICALSTEPTIME | Thresholds. | | | | WARNINGTOTALSTEPS | Thresholds. | | | @@ -290,7 +290,7 @@ is able to monitor a resource using a command like this one (replace the sample --timeout='' \ --scenario='' \ --warning-status='' \ - --critical-status='%{status} ne "success"' \ + --critical-status='%\{status\} ne "success"' \ --warning-total-time='' \ --critical-total-time='' \ --warning-total-steps='' \ @@ -362,7 +362,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -398,8 +398,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --directory | Set the share directory. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{message} !~ /authentication succeeded/i' You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{message\} !~ /authentication succeeded/i' You can use the following variables: %\{status\}, %\{message\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -442,10 +442,10 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------| | --scenario | Scenario used (required). Can be a file or json content. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} ne "success"') You can use the following variables: %{status} | -| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} ne "success"') You can use the following variables: %\{status\} | +| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\} | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'errors', 'step-time'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-dns.md b/pp/integrations/plugin-packs/procedures/applications-protocol-dns.md index bb454b0f170a..4f2cc218cf2b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-dns.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-dns.md @@ -247,7 +247,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-ftp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-ftp.md index 4f632b8e61fe..823188ff3186 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-ftp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-ftp.md @@ -300,7 +300,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-http.md b/pp/integrations/plugin-packs/procedures/applications-protocol-http.md index 0e7ae3ae631b..45344b71b9fd 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-http.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-http.md @@ -223,7 +223,7 @@ yum install centreon-plugin-Applications-Protocol-Http | Macro | Description | Default value | Mandatory | |:----------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| EXPECTEDCONTENT | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%{content} !~ /mypattern/mi'. It is recommended to use --critical-content directly | | | +| EXPECTEDCONTENT | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%\{content\} !~ /mypattern/mi'. It is recommended to use --critical-content directly | | | | URLPATH | Define the path of the web page to get (default: '/') | / | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -235,11 +235,11 @@ yum install centreon-plugin-Applications-Protocol-Http | URLPATH | Set path to get Webpage (default: '/') | / | | | HEADER | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx' | Content-Type: text/xml;charset=UTF-8 | | | THRESHOLDVALUE | Define the scope to which the numeric thresholds apply. Possible values for this option: 'value' to check numeric values, 'count' to check the number of values (default: count) | count | | -| FORMATOK | Customize the format of the output when the status is OK (default: '%{count} element(s) found'). You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | %{count} element(s) found | | +| FORMATOK | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found'). You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | %\{count\} element(s) found | | | DATAFILE | Set file with JSON request | | | | LOOKUP | What to lookup in JSON response (JSON XPath string) (can be multiple) See: http://goessner.net/articles/JsonPath/ | | | -| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | -| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | +| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | +| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | | WARNINGNUMERIC | Warning threshold (default: on total matching elements) | | | | CRITICALNUMERIC | Critical threshold (default: on total matching elements) | | | | WARNINGSTRING | Returns a WARNING status if the value matches the string | | | @@ -267,9 +267,9 @@ yum install centreon-plugin-Applications-Protocol-Http | DATAFILE | Set file with SOAP request (required) | | | | LOOKUP | What to lookup in XML response (XPath string) (can be multiple) FORMAT OPTIONS: | | | | THRESHOLDVALUE | Define the scope to which the numeric thresholds apply. Possible values for this option: 'value' to check numeric values, 'count' to check the number of values (default: count) | count | | -| FORMATOK | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | %{count} element(s) found | | -| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | -| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | %{count} element(s) found | | +| FORMATOK | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | %\{count\} element(s) found | | +| FORMATWARNING | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | +| FORMATCRITICAL | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | %\{count\} element(s) found | | | WARNINGNUMERIC | Warning threshold (default: on total matching elements) | | | | CRITICALNUMERIC | Critical threshold (default: on total matching elements) | | | | WARNINGSTRING | Returns a WARNING status if the value matches the string | | | @@ -354,7 +354,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -422,8 +422,8 @@ All available options for each service template are listed below: | --post-param | Set POST params (multiple option. Example: --post-param='key=value') | | --cookies-file | Save cookies in a file (example: '/tmp/lwp\_cookies.dat') | | --extracted-pattern | Define a pattern to extract a number from the returned page (use --warning-extracted and --critical-extracted option). | -| --expected-string | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%{content} !~ /mypattern/mi'. It is recommended to use --critical-content directly. | -| --unknown-status | Warning threshold for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --expected-string | Define the expected expression, where --expected-string='mypattern' is actually a shortcut for --critical-content='%\{content\} !~ /mypattern/mi'. It is recommended to use --critical-content directly. | +| --unknown-status | Warning threshold for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code | | --critical-status | Critical threshold for http response code | | --warning-time | Warning threshold in seconds (Webpage response time) | @@ -432,9 +432,9 @@ All available options for each service template are listed below: | --critical-size | Critical threshold for content size | | --warning-extracted | Warning threshold for extracted value | | --critical-extracted | Critical threshold for extracted value | -| --unknown-content | Set warning conditions for content page (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | -| --warning-content | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | -| --critical-content | Set critical threshold for content page (default: ''). You can use the following variables: %{content}, %{header}, %{first\_header}, %{code} | +| --unknown-content | Set warning conditions for content page (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | +| --warning-content | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | +| --critical-content | Set critical threshold for content page (default: ''). You can use the following variables: %\{content\}, %\{header\}, %\{first_header\}, %\{code\} | @@ -452,10 +452,10 @@ All available options for each service template are listed below: | --lookup | What to lookup in JSON response (JSON XPath string) (can be multiple) See: http://goessner.net/articles/JsonPath/ | | --lookup-perfdatas-nagios | Take perfdatas from the JSON response (JSON XPath string) Chain must be formated in Nagios format. Ex : "rta=10.752ms;50.000;100.000;0; pl=0%;20;40;; rtmax=10.802ms;;;;" FORMAT OPTIONS: | | --format-lookup | Take the output message from the JSON response (JSON XPath string) Override all the format options but substitute are still applied. | -| --format-ok | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | -| --format-warning | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-unknown | Customize the format of the output when the status is UNKNOWN (default: '%{count} element(s) found') You can use the variables described in --format-ok | +| --format-ok | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | +| --format-warning | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-unknown | Customize the format of the output when the status is UNKNOWN (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | | --values-separator | Separator used for values in format option (default: ', ') THRESHOLD OPTIONS: | | --warning-numeric | Warning threshold (default: on total matching elements) | | --critical-numeric | Critical threshold (default: on total matching elements) | @@ -482,7 +482,7 @@ All available options for each service template are listed below: | --cert-pkcs12 | Specify that the type of certificate is PKCS1. | | --get-param | Set GET params (multiple option. Example: --get-param='key=value'). | | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | @@ -519,7 +519,7 @@ All available options for each service template are listed below: | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | | --post-param | Set POST params (multiple option. Example: --post-param='key=value'). | | --cookies-file | Save cookies in a file (example: '/tmp/lwp\_cookies.dat'). | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | | --extra-stats | Add detailed time statistics (only with curl backend). | @@ -540,9 +540,9 @@ All available options for each service template are listed below: | --service-soap | Service Soap Action (required) | | --data | Set file with SOAP request (required) | | --lookup | What to lookup in XML response (XPath string) (can be multiple) FORMAT OPTIONS: | -| --format-ok | Customize the format of the output when the status is OK (default: '%{count} element(s) found') You can use the following variables: '%{values}' = display all values (also text string) '%{values\_ok}' = values from attributes and text node only (separated by option values-separator) '%{values\_warning}' and '%{values\_critical}' | -| --format-warning | Customize the format of the output when the status is WARNING (default: '%{count} element(s) found') You can use the variables described in --format-ok | -| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%{count} element(s) found') You can use the variables described in --format-ok | +| --format-ok | Customize the format of the output when the status is OK (default: '%\{count\} element(s) found') You can use the following variables: '%\{values\}' = display all values (also text string) '%\{values_ok\}' = values from attributes and text node only (separated by option values-separator) '%\{values_warning\}' and '%\{values_critical\}' | +| --format-warning | Customize the format of the output when the status is WARNING (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | +| --format-critical | Customize the format of the output when the status is CRITICAL (default: '%\{count\} element(s) found') You can use the variables described in --format-ok | | --values-separator | Separator used for values in format option (default: ', ') THRESHOLD OPTIONS: | | --warning-numeric | Warning threshold (default: on total matching elements) | | --critical-numeric | Critical threshold (default: on total matching elements) | @@ -567,7 +567,7 @@ All available options for each service template are listed below: | --cert-pwd | Specify certificate's password. | | --cert-pkcs12 | Specify that the type of certificate is PKCS1. | | --header | Set HTTP headers(multiple option). Example: --header='Content-Type: xxxxx'. | -| --unknown-status | Unknown conditions for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300'). | +| --unknown-status | Unknown conditions for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300'). | | --warning-status | Warning conditions for http response code. | | --critical-status | Critical conditions for http response code. | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-ldap.md b/pp/integrations/plugin-packs/procedures/applications-protocol-ldap.md index a4615aa78947..5c2ceec72bea 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-ldap.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-ldap.md @@ -274,7 +274,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -325,7 +325,7 @@ All available options for each service template are listed below: | --ldap-starttls-options | Add custom start tls options (need --tls option): An example --ldap-starttls-options='verify=none' | | --ldap-bind-options | Add custom bind options (can force noauth) (not really useful now). | | --ldap-search-options | Add custom search options (can change the scope for example). | -| --display-entry | Display ldap entries (with --verbose option) (example: '%{cn} account locked') | +| --display-entry | Display ldap entries (with --verbose option) (example: '%\{cn\} account locked') | | --username | Specify username for authentification (can be a DN) | | --password | Specify password for authentification | | --timeout | Connection timeout in seconds (default: 30) | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-modbus.md b/pp/integrations/plugin-packs/procedures/applications-protocol-modbus.md index 331314e27d37..1adebd10a09b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-modbus.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-modbus.md @@ -236,7 +236,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-ntp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-ntp.md index 6f4e47318a1d..176b9bb8a35c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-ntp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-ntp.md @@ -247,7 +247,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-ospf.md b/pp/integrations/plugin-packs/procedures/applications-protocol-ospf.md index fa4f5da8fe1f..0f38dc7ef149 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-ospf.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-ospf.md @@ -172,12 +172,12 @@ yum install centreon-plugin-Applications-Protocol-Ospf | Macro | Description | Default value | Mandatory | |:--------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{NbrState} =~ /down/i'). You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | %{NbrState} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{NbrState\} =~ /down/i'). You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | %\{NbrState\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | -| WARNINGTOTALCHANGE | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | | | -| CRITICALTOTALCHANGE | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | | | +| WARNINGTOTALCHANGE | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | | +| CRITICALTOTALCHANGE | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -203,7 +203,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-total-change='' \ --critical-total-change='' \ --warning-status='' \ - --critical-status='%{NbrState} =~ /down/i' \ + --critical-status='%\{NbrState\} =~ /down/i' \ --verbose ``` @@ -260,7 +260,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -317,10 +317,10 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{NbrState} =~ /down/i'). You can use the following variables: %{NbrState}, %{NbrRtrId}, %{NbrIpAddr} | -| --warning-total-change | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | -| --critical-total-change | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %{TotalLast} != %{Total} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{NbrState\} =~ /down/i'). You can use the following variables: %\{NbrState\}, %\{NbrRtrId\}, %\{NbrIpAddr\} | +| --warning-total-change | Set warning threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | +| --critical-total-change | Set critical threshold. Should be used if there is a difference of total neighbors between two checks. Example: %\{TotalLast\} != %\{Total\} | | --warning-* | Warning threshold. Can be: 'total'. | | --critical-* | Critical threshold. Can be: 'total'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-radius.md b/pp/integrations/plugin-packs/procedures/applications-protocol-radius.md index 7ea474519260..99e1150e40f6 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-radius.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-radius.md @@ -106,7 +106,7 @@ yum install centreon-pack-applications-protocol-radius --username='' \ --password='' \ --warning-status='' \ - --critical-status='%{status} ne "accepted"' \ + --critical-status='%\{status\} ne "accepted"' \ --warning-time='2' \ --critical-time='3' \ --use-new-perfdata diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-sftp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-sftp.md index 380d56973786..e7b014452f9d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-sftp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-sftp.md @@ -198,8 +198,8 @@ yum install centreon-plugin-Applications-Protocol-Sftp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | %{message} !~ /authentication succeeded/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | %\{message\} !~ /authentication succeeded/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGTIME | Warning threshold in seconds. | | | | CRITICALTIME | Critical threshold in seconds. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -235,10 +235,10 @@ yum install centreon-plugin-Applications-Protocol-Sftp | SCENARIO | Scenario used (required). Can be a file or json content | | X | | WARNINGERRORS | Thresholds. | | | | CRITICALERRORS | Thresholds. | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}. | %{status} ne "success" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | | | -| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message}. | | | -| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}. | %\{status\} ne "success" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | | | +| WARNINGSTEPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\}. | | | +| CRITICALSTEPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\}. | | | | WARNINGSTEPTIME | Thresholds. | | | | CRITICALSTEPTIME | Thresholds. | | | | WARNINGTOTALSTEPS | Thresholds. | | | @@ -267,7 +267,7 @@ is able to monitor a resource using a command like this one (replace the sample --ssh-password='my-password' \ --scenario='' \ --warning-status='' \ - --critical-status='%{status} ne "success"' \ + --critical-status='%\{status\} ne "success"' \ --warning-total-time='' \ --critical-total-time='' \ --warning-total-steps='' \ @@ -337,7 +337,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -374,8 +374,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{message} !~ /authentication succeeded/i' You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{message\} !~ /authentication succeeded/i' You can use the following variables: %\{status\}, %\{message\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -406,10 +406,10 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| | --scenario | Scenario used (required). Can be a file or json content. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "success"') You can use the following variables: %{status} | -| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{message} | -| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{message} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "success"') You can use the following variables: %\{status\} | +| --warning-step-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{message\} | +| --critical-step-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{message\} | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'errors', 'step-time'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-smtp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-smtp.md index 6a34201f6440..a33d53f57457 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-smtp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-smtp.md @@ -258,7 +258,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-snmp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-snmp.md index ee3d17dc7110..6266a843968b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-snmp.md @@ -241,13 +241,13 @@ yum install centreon-plugin-Applications-Protocol-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| -| FORMATOK | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | %{filter\_rows} value(s) | | -| FORMATUNKNOWN | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_unknown} | | +| FORMATOK | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | %\{filter_rows\} value(s) | | +| FORMATUNKNOWN | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_unknown\} | | | OID | OID value to check (numeric format only) | | | | WARNING | Return Warning if an oid value match the regexp | | | | CRITICAL | Return Critical if an oid value match the regexp | | | -| FORMATWARNING | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_warning} | | -| FORMATCRITICAL | Output format according to the threshold. : '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | value(s): %{details\_critical} | | +| FORMATWARNING | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_warning\} | | +| FORMATCRITICAL | Output format according to the threshold. : '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | value(s): %\{details_critical\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -337,7 +337,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -417,14 +417,14 @@ All available options for each service template are listed below: | --perfdata-name | Perfdata name in perfdata output (Default: 'value') | | --perfdata-min | Minimum value to add in perfdata output (Default: '') | | --perfdata-max | Maximum value to add in perfdata output (Default: '') | -| --config-json | JSON format to configure the mode. Can check multiple OID. Example: --config-json='\[ { "oid": ".1.3.6.1.2.1.1.3.0", "perfdata\_name": "oid1", "format": "current oid1 value is %s"}, { "oid": ".1.3.6.1.2.1.1.3.2", "perfdata\_name": "oid2", "format": "current oid2 value is %s"} \]' | +| --config-json | JSON format to configure the mode. Can check multiple OID. Example: --config-json='\[ \{ "oid": ".1.3.6.1.2.1.1.3.0", "perfdata_name": "oid1", "format": "current oid1 value is %s"\}, \{ "oid": ".1.3.6.1.2.1.1.3.2", "perfdata_name": "oid2", "format": "current oid2 value is %s"\} \]' | | Option | Description | |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --oid or <--oid-leef> | OID value to check (numeric format only). | +| --oid or \<--oid-leef\> | OID value to check (numeric format only). | | --oid-table | OID table value to check (numeric format only). | | --oid-instance | OID table value for the instance (numeric format only). Can be used to have human readable instance name. | | --filter-table-value | Filter value from --oid-table option (can be a regexp). | @@ -432,7 +432,7 @@ All available options for each service template are listed below: | --warning-regexp | Return Warning if an oid value match the regexp. | | --critical-regexp | Return Critical if an oid value match the regexp. | | --regexp-isensitive | Allows to use regexp non case-sensitive. | -| --format-* | Output format according to the threshold. Can be: 'ok' (default: '%{filter\_rows} value(s)'), 'warning' (default: 'value(s): %{details\_warning}'), 'critical' (default: 'value(s): %{details\_critical}'), 'unknown' (default: 'value(s): %{details\_unknown}'). You can use the following variables: %{rows}, %{filter\_rows}, %{details\_warning}, %{details\_ok}, %{details\_critical}, %{details\_unknown} | +| --format-* | Output format according to the threshold. Can be: 'ok' (default: '%\{filter_rows\} value(s)'), 'warning' (default: 'value(s): %\{details_warning\}'), 'critical' (default: 'value(s): %\{details_critical\}'), 'unknown' (default: 'value(s): %\{details_unknown\}'). You can use the following variables: %\{rows\}, %\{filter_rows\}, %\{details_warning\}, %\{details_ok\}, %\{details_critical\}, %\{details_unknown\} | | --map-values | Use to transform an integer value in most common case. Example: --map-values='1=\>ok,10=\>fan failed,11=\>psu recovery' | | --map-value-other | Use to transform an integer value not defined in --map-values option. | | --map-values-separator | Separator uses between values (default: coma). | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-ssh.md b/pp/integrations/plugin-packs/procedures/applications-protocol-ssh.md index 5ed31484bf6e..71688810b31a 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-ssh.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-ssh.md @@ -102,7 +102,7 @@ command: --ssh-username='' \ --ssh-password='' \ --warning-status='' \ - --critical-status='%{message} !~ /authentification succeeded/i' \ + --critical-status='%\{message\} !~ /authentification succeeded/i' \ --warning-time='2' \ --critical-time='3' \ --use-new-perfdata diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-tcp.md b/pp/integrations/plugin-packs/procedures/applications-protocol-tcp.md index 4b2875f8fd96..5f72a7ab818c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-tcp.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-tcp.md @@ -311,7 +311,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -344,9 +344,9 @@ All available options for each service template are listed below: | --port | Port used | | --ssl | Use SSL connection. (no attempt is made to check the certificatevalidity by default). | | --timeout | Connection timeout in seconds (default: 3) | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{port}, %{error\_message} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{port}, %{error\_message} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "failed"'). You can use the following variables: %{status}, %{port}, %{error\_message} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "failed"'). You can use the following variables: %\{status\}, %\{port\}, %\{error_message\} | | --warning-time | Warning threshold in seconds | | --critical-time | Critical threshold in seconds | diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-telnet.md b/pp/integrations/plugin-packs/procedures/applications-protocol-telnet.md index 872987fc9bec..ff2ba65497fc 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-telnet.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-telnet.md @@ -19,11 +19,11 @@ The remote server must have a Telnet service running and available. You need to create a JSON scenario file. An example: [ - {"cmd": "open", "options": { "Host": "10.0.0.1", "Port": "23", "Timeout": "30" } }, - {"cmd": "login", "options": { "Name": "admin", "Password": "pass", "Timeout": "5" } }, - {"cmd": "waitfor", "options": { "Match": "/string/", "Timeout": "5" } }, - {"cmd": "put", "options": { "String": "/mystring/", "Timeout": "5" } }, - {"cmd": "close" } + \{"cmd": "open", "options": \{ "Host": "10.0.0.1", "Port": "23", "Timeout": "30" \} \}, + \{"cmd": "login", "options": \{ "Name": "admin", "Password": "pass", "Timeout": "5" \} \}, + \{"cmd": "waitfor", "options": \{ "Match": "/string/", "Timeout": "5" \} \}, + \{"cmd": "put", "options": \{ "String": "/mystring/", "Timeout": "5" \} \}, + \{"cmd": "close" \} ] ## Centreon Configuration diff --git a/pp/integrations/plugin-packs/procedures/applications-protocol-x509.md b/pp/integrations/plugin-packs/procedures/applications-protocol-x509.md index 75eec6a481b3..111c96f1e14c 100644 --- a/pp/integrations/plugin-packs/procedures/applications-protocol-x509.md +++ b/pp/integrations/plugin-packs/procedures/applications-protocol-x509.md @@ -157,8 +157,8 @@ yum install centreon-plugin-Applications-Protocol-X509 |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | CUSTOMMODE | | tcp | | | PORT | Port used by host | 443 | X | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (Default: '%{expiration} \< 60'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects} | %{expiration} \< 60 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%{expiration} \< 30'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%{expiration} \< 30 \|\| %{alt\_subjects} !~ /my.app.com/' | %{expiration} \< 30 | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (Default: '%\{expiration\} \< 60'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\} | %\{expiration\} \< 60 | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expiration\} \< 30'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%\{expiration\} \< 30 \|\| %\{alt_subjects\} !~ /my.app.com/' | %\{expiration\} \< 30 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -179,8 +179,8 @@ is able to monitor a resource using a command like this one (replace the sample --custommode='tcp' \ --hostname='www.google.com' \ --port=443 \ - --warning-status='%{expiration} < 60' \ - --critical-status='%{expiration} < 30' + --warning-status='%\{expiration\} < 60' \ + --critical-status='%\{expiration\} < 30' ``` The expected command output is shown below: @@ -325,7 +325,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -344,8 +344,8 @@ All available options for each service template are listed below: | --disco-show | Applies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery. | | --float-precision | Define the float precision for thresholds (default: 8). | | --source-encoding | Define the character encoding of the response sent by the monitored resource Default: 'UTF-8'. | -| --warning-status | Define the conditions to match for the status to be WARNING. (Default: '%{expiration} \< 60'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{expiration} \< 30'). Can use special variables like: %{expiration}, %{subject}, %{issuer}, %{alt\_subjects}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%{expiration} \< 30 \|\| %{alt\_subjects} !~ /my.app.com/' | +| --warning-status | Define the conditions to match for the status to be WARNING. (Default: '%\{expiration\} \< 60'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{expiration\} \< 30'). Can use special variables like: %\{expiration\}, %\{subject\}, %\{issuer\}, %\{alt_subjects\}. Examples : Raise a critical alarm if certificate expires in less than 30 days or does not cover alternative name 'my.app.com' --critical-status='%\{expiration\} \< 30 \|\| %\{alt_subjects\} !~ /my.app.com/' | diff --git a/pp/integrations/plugin-packs/procedures/applications-pvx-restapi.md b/pp/integrations/plugin-packs/procedures/applications-pvx-restapi.md index 6d73e17f10b0..855d275a4f3e 100644 --- a/pp/integrations/plugin-packs/procedures/applications-pvx-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-pvx-restapi.md @@ -91,7 +91,7 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the -[official documentation](). In +[official documentation](http://docs.performancevision.com/api_use.html). In each step replace the value of the macros enclosed by '< \>' with yours. ```bash diff --git a/pp/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md b/pp/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md index 92b39e026887..cec6ccab702f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-rapidrecovery-snmp.md @@ -190,12 +190,12 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | %{status} =~ /unreachable/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /unreachable/i | | | FILTERNAME | Filter agent name (can be a regexp) | | | | WARNINGRECOVERYPOINTS | Thresholds | | | | CRITICALRECOVERYPOINTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /failed\|authenticationError/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /failed\|authenticationError/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -205,7 +205,7 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /unknown/i | | | FILTERNAME | Filter repository name (can be a regexp) | | | | WARNINGSPACEUSAGE | Thresholds | | | | CRITICALSPACEUSAGE | Thresholds | | | @@ -213,8 +213,8 @@ yum install centreon-plugin-Applications-Rapidrecovery-Snmp | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /error/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -236,9 +236,9 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --filter-name='' \ - --unknown-status='%{status} =~ /unknown/i' \ + --unknown-status='%\{status\} =~ /unknown/i' \ --warning-status='' \ - --critical-status='%{status} =~ /error/i' \ + --critical-status='%\{status\} =~ /error/i' \ --warning-space-usage='' \ --critical-space-usage='' \ --warning-space-usage-free='' \ @@ -300,7 +300,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -354,9 +354,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unreachable/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed\|authenticationError/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unreachable/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed\|authenticationError/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'recoverypoints'. | | --filter-name | Filter agent name (can be a regexp). | @@ -365,9 +365,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /error/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage' (B), 'space-usage-free' (B), 'space-usage-prct' (%). | | --filter-name | Filter repository name (can be a regexp). | diff --git a/pp/integrations/plugin-packs/procedures/applications-redis-sentinel.md b/pp/integrations/plugin-packs/procedures/applications-redis-sentinel.md index c1c5ff0fd5b7..8cae83775852 100644 --- a/pp/integrations/plugin-packs/procedures/applications-redis-sentinel.md +++ b/pp/integrations/plugin-packs/procedures/applications-redis-sentinel.md @@ -60,10 +60,10 @@ It brings the following Service Templates: To control your Redis Sentinel, the Poller should be able to perform ```redis-cli``` requests over the TCP/26379 port (by default). The following commands are used: -* sentinel ckquorum +* sentinel ckquorum \ * sentinel masters -* sentinel replicas -* sentinel sentinels +* sentinel replicas \ +* sentinel sentinels \ ## Setup diff --git a/pp/integrations/plugin-packs/procedures/applications-rrdcached.md b/pp/integrations/plugin-packs/procedures/applications-rrdcached.md index 249443deeba0..dacf2b5d0293 100644 --- a/pp/integrations/plugin-packs/procedures/applications-rrdcached.md +++ b/pp/integrations/plugin-packs/procedures/applications-rrdcached.md @@ -303,8 +303,8 @@ yum install centreon-plugin-Applications-RRDCached | Macro | Description | Default value | Mandatory | |:-----------------|:---------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| CRITICALRESPONSE | Define the conditions to match for the status to be CRITICAL. You can use the variable '%{response}'. | %{response} !~ /PONG/ | | -| WARNINGRESPONSE | Define the conditions to match for the status to be WARNING. You can use the variable '%{response}'. | | | +| CRITICALRESPONSE | Define the conditions to match for the status to be CRITICAL. You can use the variable '%\{response\}'. | %\{response\} !~ /PONG/ | | +| WARNINGRESPONSE | Define the conditions to match for the status to be WARNING. You can use the variable '%\{response\}'. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -397,7 +397,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -450,8 +450,8 @@ All available options for each service template are listed below: | Option | Description | |:-------|:------------| -| --warning-response | Define the conditions to match for the status to be WARNING. You can use the variable '%{response}'. | -| --critical-response | Define the conditions to match for the status to be CRITICAL. You can use the variable '%{response}'. Default: '%{response} !~ /PONG/'. | +| --warning-response | Define the conditions to match for the status to be WARNING. You can use the variable '%\{response\}'. | +| --critical-response | Define the conditions to match for the status to be CRITICAL. You can use the variable '%\{response\}'. Default: '%\{response\} !~ /PONG/'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-rubrik-restapi.md b/pp/integrations/plugin-packs/procedures/applications-rubrik-restapi.md index a6c44b2ececa..d2ece9d220e0 100644 --- a/pp/integrations/plugin-packs/procedures/applications-rubrik-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-rubrik-restapi.md @@ -140,7 +140,7 @@ Here is the list of services for this connector, detailing all metrics and statu Rubrik App provides a RESTful API on top of Cluster and Edge components. You can get a closer look to the API directly on the Cluster using this address: -https://{{node_ip}}/docs/{{v1|v2|internal}}/playground +https://\{\{node_ip\}\}/docs/\{\{v1|v2|internal\}\}/playground Information about its configuration is available on github: https://github.com/rubrikinc/api-documentation @@ -265,13 +265,13 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | CLUSTERID | Which cluster to check (default: 'me') | me | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGREAD | Threshold | | | | CRITICALREAD | Threshold | | | | WARNINGREADIOPS | Threshold | | | | CRITICALREADIOPS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGWRITE | Threshold | | | | CRITICALWRITE | Threshold | | | | WARNINGWRITEIOPS | Threshold | | | @@ -301,8 +301,8 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | CRITICALCLUSTERDISKSACTIVE | Threshold | | | | WARNINGCLUSTERDISKSTOTAL | Threshold | | | | CRITICALCLUSTERDISKSTOTAL | Threshold | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{id} | %{status} !~ /active/i | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{id\} | %\{status\} !~ /active/i | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -315,8 +315,8 @@ yum install centreon-plugin-Applications-Rubrik-Restapi | FILTERJOBTYPE | Filter jobs by job type | | | | FILTEROBJECTTYPE | Filter jobs by object type | | | | FILTERLOCATIONNAME | Filter jobs by location name | | | -| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (default: %{status} =~ /Failure/i). You can use the following variables: %{status}, %{jobName} | %{status} =~ /failure/i | | -| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | | | +| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (default: %\{status\} =~ /Failure/i). You can use the following variables: %\{status\}, %\{jobName\} | %\{status\} =~ /failure/i | | +| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | | | | WARNINGJOBEXECUTIONLAST | Threshold | | | | CRITICALJOBEXECUTIONLAST | Threshold | | | | WARNINGJOBEXECUTIONSFAILEDPRCT | Threshold | | | @@ -334,13 +334,13 @@ yum install centreon-plugin-Applications-Rubrik-Restapi |:--------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | CLUSTERID | Which cluster to check (default: 'me') | me | | | FILTERNODEID | Filter nodes by node ID (can be a regexp) | | | -| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{ip\_address}, %{id} | | | +| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | | | WARNINGCLUSTERNODESOK | Threshold | | | | CRITICALCLUSTERNODESOK | Threshold | | | | WARNINGCLUSTERNODESTOTAL | Threshold | | | | CRITICALCLUSTERNODESTOTAL | Threshold | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{ip\_address}, %{id} | %{status} !~ /ok/i | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{ip\_address}, %{id} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | %\{status\} !~ /ok/i | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -405,7 +405,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-jobs-executions-detected='' \ --critical-jobs-executions-detected='' \ --warning-execution-status='' \ - --critical-execution-status='%{status} =~ /failure/i' \ + --critical-execution-status='%\{status\} =~ /failure/i' \ --verbose ``` @@ -470,7 +470,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -534,9 +534,9 @@ All available options for each service template are listed below: |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --cluster-id | Which cluster to check (default: 'me'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'read' (B/s), 'write' (B/s), 'read-iops', 'write-iops'. | @@ -555,9 +555,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='disk-status' | | --cluster-id | Which cluster to check (default: 'me'). | | --filter-disk-id | Filter disks by disk ID (can be a regexp). | -| --unknown-disks-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{id} | -| --warning-disk-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status}, %{id} | +| --unknown-disks-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{id\} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'cluster-disks-total', 'cluster-disks-active'. | @@ -573,9 +573,9 @@ All available options for each service template are listed below: | --unit | Select the time unit for last execution time thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --limit | Define the number of entries to retrieve for the pagination (default: 500). | | --check-retention | Use the retention file to check if a job have been detected once but does not appear in the API response. | -| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --warning-execution-status | Set warning threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --critical-execution-status | Set critical threshold for last job execution status (default: %{status} =~ /Failure/i). You can use the following variables: %{status}, %{jobName} | +| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --warning-execution-status | Set warning threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --critical-execution-status | Set critical threshold for last job execution status (default: %\{status\} =~ /Failure/i). You can use the following variables: %\{status\}, %\{jobName\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-executions-detected', 'job-executions-failed-prct', 'job-execution-last', 'job-running-duration'. | @@ -586,9 +586,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='node-status' | | --cluster-id | Which cluster to check (default: 'me'). | | --filter-node-id | Filter nodes by node ID (can be a regexp). | -| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{ip\_address}, %{id} | -| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{ip\_address}, %{id} | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{ip\_address}, %{id} | +| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | +| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{ip_address\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'cluster-nodes-total', 'cluster-nodes-ok'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-rudder-restapi.md b/pp/integrations/plugin-packs/procedures/applications-rudder-restapi.md index 19d1992e7bae..af87a6b9a25d 100644 --- a/pp/integrations/plugin-packs/procedures/applications-rudder-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-rudder-restapi.md @@ -18,7 +18,7 @@ yum install centreon-plugin-Applications-Rudder-Restapi A token needs to be created to acces the API. To do so, follow the official documentation here : -. +\. ## Centreon Configuration diff --git a/pp/integrations/plugin-packs/procedures/applications-sahipro-restapi.md b/pp/integrations/plugin-packs/procedures/applications-sahipro-restapi.md index 7ff41f12f705..db341fbf0b07 100644 --- a/pp/integrations/plugin-packs/procedures/applications-sahipro-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-sahipro-restapi.md @@ -178,19 +178,19 @@ yum install centreon-plugin-Applications-Sahipro-Restapi | SAHIBROWSERTYPE | Browser used for script executions (Default: chrome) | chrome | | | RETRIESSCENARIOSTATUS | Define the number of retries to get scenario status (if we fail to get the status) | 0 | | | INTERVALSCENARIOSTATUS | Define time interval to get scenario status in seconds (default: 10) | 10 | | -| UNKNOWNRUNSTATUS | Unknown threshold for running scenario rest api response. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | %{http\_code} \< 200 or %{http\_code} \>= 300 | | +| UNKNOWNRUNSTATUS | Unknown threshold for running scenario rest api response. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | %\{http_code\} \< 200 or %\{http_code\} \>= 300 | | | SAHISUITE | Define path for scenario files (required. Example: 'sahitests/small.suite') | | | | SAHIBASEURL | Define default Start URL for scripts | | | | TIMEOUT | Define the global script timeout. If timeout is reached, scenario is killed | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | | WARNINGERRORS | Thresholds | | | | CRITICALERRORS | Thresholds | | | | WARNINGFAILURES | Thresholds | | | | CRITICALFAILURES | Thresholds | | | | WARNINGRUNSTATUS | Warning threshold for running scenario rest api response | | | | CRITICALRUNSTATUS | Critical threshold for running scenario rest api response | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "SUCCESS"'). You can use the following variables: %{status} | %{status} ne "SUCCESS" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "SUCCESS"'). You can use the following variables: %\{status\} | %\{status\} ne "SUCCESS" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | WARNINGSTEPTIME | Thresholds | | | | CRITICALSTEPTIME | Thresholds | | | | WARNINGTOTALSTEPS | Thresholds | | | @@ -279,7 +279,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -318,11 +318,11 @@ All available options for each service template are listed below: | --timeout | Define the global script timeout. If timeout is reached, scenario is killed. | | --retries-scenario-status | Define the number of retries to get scenario status (if we fail to get the status). | | --interval-scenario-status | Define time interval to get scenario status in seconds (default: 10). | -| --unknown-run-status | Unknown threshold for running scenario rest api response. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-run-status | Unknown threshold for running scenario rest api response. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-run-status | Warning threshold for running scenario rest api response. | | --critical-run-status | Critical threshold for running scenario rest api response. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "SUCCESS"'). You can use the following variables: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "SUCCESS"'). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: 'total-time', 'total-steps', 'failures', 'errors', 'step-time'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md b/pp/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md index a08a528951c4..89176c2c8221 100644 --- a/pp/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-sailpoint-identitynow-restapi.md @@ -194,7 +194,7 @@ yum install centreon-plugin-Applications-Sailpoint-Identitynow-Restapi | Macro | Description | Default value | Mandatory | |:---------------------|:----------------------------------------------------------------------------------------------------|:----------------------------|:------------| -| OUTPUT | Output to print after retrieving the count of results (Default: "Number of results: %{count}") | Number of results: %{count} | | +| OUTPUT | Output to print after retrieving the count of results (Default: "Number of results: %\{count\}") | Number of results: %\{count\} | | | QUERY | Query parameters used to construct an Elasticsearch query object(see documentation) | | | | WARNINGRESULTSCOUNT | | | | | CRITICALRESULTSCOUNT | | | | @@ -208,7 +208,7 @@ yum install centreon-plugin-Applications-Sailpoint-Identitynow-Restapi | SOURCEID | Define source ID to retrieve only one source health status (useful with service discovery) | | | | FILTERNAME | Filter source name (Can be a regexp) | | | | FILTERTYPE | Filter source type (Can be a regexp) | | | -| CRITICALHEALTHSTATUS | Set critical threshold for each source health status (Default: '%{status} ne "SOURCE\_STATE\_HEALTHY"') | %{status} ne "SOURCE_STATE_HEALTHY" | | +| CRITICALHEALTHSTATUS | Set critical threshold for each source health status (Default: '%\{status\} ne "SOURCE\_STATE\_HEALTHY"') | %\{status\} ne "SOURCE_STATE_HEALTHY" | | | WARNINGHEALTHSTATUS | Set warning threshold for each source health status (Default: none) | | | | WARNINGSOURCESERROR | Set threshold for each status counter | | | | CRITICALSOURCESERROR | Set threshold for each status counter | | | @@ -301,7 +301,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -357,7 +357,7 @@ All mode-specific options are listed here: | Option | Description | Type | |:-------------------------------------------------|:--------------------------------------------------------------------------------------------------|:-----| | --query | Query parameters used to construct an Elasticsearch query object(see documentation). | Mode | -| --output | Output to print after retrieving the count of results (Default: "Number of results: %{count}"). | Mode | +| --output | Output to print after retrieving the count of results (Default: "Number of results: %\{count\}"). | Mode | | --warning-results-count --critical-results-count | Thresholds on count of results. | Mode | @@ -369,7 +369,7 @@ All mode-specific options are listed here: | --filter-name | Filter source name (Can be a regexp). | Mode | | --filter-type | Filter source type (Can be a regexp). | Mode | | --warning-health-status | Set warning threshold for each source health status (Default: none). | Mode | -| --critical-health-status | Set critical threshold for each source health status (Default: '%{status} ne "SOURCE\_STATE\_HEALTHY"'). | Mode | +| --critical-health-status | Set critical threshold for each source health status (Default: '%\{status\} ne "SOURCE\_STATE\_HEALTHY"'). | Mode | | --warning-sources-* --critical-sources-* | Set threshold for each status counter. Can be: 'healthy', 'error', 'failure', 'unchecked'. | Mode | diff --git a/pp/integrations/plugin-packs/procedures/applications-salesforce-restapi.md b/pp/integrations/plugin-packs/procedures/applications-salesforce-restapi.md index cce6e2faf9db..b715fd77ffc8 100644 --- a/pp/integrations/plugin-packs/procedures/applications-salesforce-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-salesforce-restapi.md @@ -241,7 +241,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -274,7 +274,7 @@ All available options for each service template are listed below: | --alias | Add this option if your want to use your instance alias | | --unknown-status | Set unknown threshold for instance status (default: ''). | | --warning-status | Set warning threshold for instance status (default: ''). | -| --critical-status | Set critical threshold for instance status (default: '%{status} !~ /OK/'). | +| --critical-status | Set critical threshold for instance status (default: '%\{status\} !~ /OK/'). | diff --git a/pp/integrations/plugin-packs/procedures/applications-sccm-nsclient.md b/pp/integrations/plugin-packs/procedures/applications-sccm-nsclient.md index 9bbf0a17f3ce..47d863576739 100644 --- a/pp/integrations/plugin-packs/procedures/applications-sccm-nsclient.md +++ b/pp/integrations/plugin-packs/procedures/applications-sccm-nsclient.md @@ -155,7 +155,7 @@ user account and test the Plugin by running the following command: -p 5666 \ -t 30 \ -u -m 8192 \ - -c check_centreon_plugins -a 'apps::sccm::local::plugin' 'site-status' '--critical-status="%{status} eq FAILED"' + -c check_centreon_plugins -a 'apps::sccm::local::plugin' 'site-status' '--critical-status="%\{status\} eq FAILED"' ``` This command should return an output message like: @@ -191,7 +191,7 @@ parameter to the command: --command=check_centreon_plugins \ --arg='apps::sccm::local::plugin' \ --arg='site-status' \ - --arg='--critical-status="%{status} eq FAILED"' + --arg='--critical-status="%\{status\} eq FAILED"' ``` This command should return an output message like: diff --git a/pp/integrations/plugin-packs/procedures/applications-slack-restapi.md b/pp/integrations/plugin-packs/procedures/applications-slack-restapi.md index 099c11e65a75..2ec0b7795a74 100644 --- a/pp/integrations/plugin-packs/procedures/applications-slack-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-slack-restapi.md @@ -124,8 +124,8 @@ by running the following command (Some of the parameters such as ```proxyurl``` --mode=services \ --proxyurl='http://myproxy.mycompany.org:8080' \ --filter-name='Connections|Messaging' \ - --warning-status='%{status} eq "active" and %{type} eq "incident"' \ - --critical-status='%{status} eq "active" and %{type} eq "outage"' \ + --warning-status='%\{status\} eq "active" and %\{type\} eq "incident"' \ + --critical-status='%\{status\} eq "active" and %\{type\} eq "outage"' \ --verbose ``` diff --git a/pp/integrations/plugin-packs/procedures/applications-tosca-restapi.md b/pp/integrations/plugin-packs/procedures/applications-tosca-restapi.md index c82af59a2fd8..98de18f5ad47 100644 --- a/pp/integrations/plugin-packs/procedures/applications-tosca-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-tosca-restapi.md @@ -200,8 +200,8 @@ yum install centreon-plugin-Applications-Tosca-Restapi | SCENARIOID | Scenario unique ID | | | | WARNINGDURATION | Thresholds | | | | CRITICALDURATION | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{result} !~ /Passed/'). You can use the following variables: %{result} | %{result} !~ /Passed/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{result} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{result\} !~ /Passed/'). You can use the following variables: %\{result\} | %\{result\} !~ /Passed/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{result\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -277,7 +277,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -331,8 +331,8 @@ All modes specific options are listed here: |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:-----| | --workspace | Workspace name of the provided scenario. | Mode | | --scenario-id | Scenario unique ID. | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{result} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{result} !~ /Passed/'). You can use the following variables: %{result} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{result\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{result\} !~ /Passed/'). You can use the following variables: %\{result\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'duration'. | Mode | diff --git a/pp/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md b/pp/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md index 0938799accfb..e02019c4ec56 100644 --- a/pp/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md +++ b/pp/integrations/plugin-packs/procedures/applications-trendmicro-iwsva-snmp.md @@ -334,7 +334,7 @@ yum install centreon-plugin-Applications-TrendMicro-Iwsva | CRITICALIN | Critical thresholds for in traffic | 90 | | | WARNINGOUT | Warning thresholds for out traffic | 80 | | | CRITICALOUT | Critical thresholds for out traffic | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -437,7 +437,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -598,9 +598,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/applications-veeam-nrpe.md b/pp/integrations/plugin-packs/procedures/applications-veeam-nrpe.md index f83eda383f70..b78109742959 100644 --- a/pp/integrations/plugin-packs/procedures/applications-veeam-nrpe.md +++ b/pp/integrations/plugin-packs/procedures/applications-veeam-nrpe.md @@ -217,11 +217,11 @@ yum install centreon-nrpe3-plugin | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter job with start time greater than current time less value in seconds | | | | FILTERCOUNTERS | Only display some counters (regexp can be used). | | | -| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -241,8 +241,8 @@ yum install centreon-nrpe3-plugin | CRITICALLICENSEINSTANCESUSAGE | Thresholds | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Thresholds | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -260,8 +260,8 @@ yum install centreon-nrpe3-plugin | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -270,8 +270,8 @@ yum install centreon-nrpe3-plugin | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -291,8 +291,8 @@ yum install centreon-nrpe3-plugin | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCESS | Thresholds | | | | CRITICALJOBSSUCCESS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -310,7 +310,7 @@ is able to monitor a resource using a command like this one (replace the sample /usr/lib64/nagios/plugins//check_centreon_nrpe -H 10.0.0.1 -p 5666 -t 55 -c check_centreon_plugins -a 'apps::backup::veeam::local::plugin' 'tape-jobs' ' \ --filter-name="" \ --warning-status="" \ - --critical-status="%{enabled} == 1 and not %{last_result} =~ /Success|None/i" \ + --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \ --warning-total="" \ --critical-total="" \ --verbose' @@ -372,7 +372,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -413,11 +413,11 @@ All available options for each service template are listed below: | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (default: 86400). | -| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -436,8 +436,8 @@ All available options for each service template are listed below: | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the time unit for the expiration thresholds. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -456,8 +456,8 @@ All available options for each service template are listed below: | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -475,9 +475,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -496,9 +496,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md b/pp/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md index 2275bbad91d3..515d2b421f8f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-veeam-nsclient-05-restapi.md @@ -221,11 +221,11 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter job with start time greater than current time less value in seconds | | | | FILTERCOUNTERS | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\ |yyyy$' | | | -| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -245,8 +245,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALLICENSEINSTANCESUSAGE | Threshold | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Threshold | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -264,8 +264,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALSPACEUSAGEFREE | Threshold | | | | WARNINGSPACEUSAGEPRCT | Threshold | | | | CRITICALSPACEUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -274,8 +274,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -295,8 +295,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | CRITICALJOBSFAILED | Threshold | | | | WARNINGJOBSSUCCESS | Threshold | | | | CRITICALJOBSSUCCESS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -333,7 +333,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-jobs-warning="" \ --critical-jobs-warning="" \ --warning-status="" \ - --critical-status="not %{status} =~ /success/i" \ + --critical-status="not %\{status\} =~ /success/i" \ --verbose' ``` @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -439,11 +439,11 @@ All available options for each service template are listed below: | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (default: 86400). | -| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). You can use the following variables: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. You can use the following variables: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Define the conditions to match for the status to be OK. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. You can use the following variables: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -462,8 +462,8 @@ All available options for each service template are listed below: | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{to}, %{status}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). You can use the following variables: %{to}, %{status}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). You can use the following variables: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the time unit for the expiration thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -482,8 +482,8 @@ All available options for each service template are listed below: | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /ordinal\|maintenance/i'). You can use the following variables: %{status}, %{name}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /ordinal\|maintenance/i'). You can use the following variables: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -501,9 +501,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). You can use the following variables: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). You can use the following variables: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -522,9 +522,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %{status} =~ /success/i'). You can use the following variables: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: 'not %\{status\} =~ /success/i'). You can use the following variables: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md b/pp/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md index ebd50a4a4ace..269a02684ac7 100644 --- a/pp/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-veeam-vbem-restapi.md @@ -205,8 +205,8 @@ yum install centreon-plugin-Applications-Veeam-Vbem-Restapi | FILTERUID | Filter jobs by UID | | | | FILTERNAME | Filter jobs by name | | | | FILTERTYPE | Filter jobs by type | | | -| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status (Default: %{status} =~ /warning/i). You can use the following variables like: %{status}, %{jobName} | %{status} =~ /warning/i | | -| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (Default: %{status} =~ /failed/i). You can use the following variables: %{status}, %{jobName} | %{status} =~ /failed/i | | +| WARNINGEXECUTIONSTATUS | Set warning threshold for last job execution status (Default: %\{status\} =~ /warning/i). You can use the following variables like: %\{status\}, %\{jobName\} | %\{status\} =~ /warning/i | | +| CRITICALEXECUTIONSTATUS | Set critical threshold for last job execution status (Default: %\{status\} =~ /failed/i). You can use the following variables: %\{status\}, %\{jobName\} | %\{status\} =~ /failed/i | | | WARNINGJOBEXECUTIONLAST | Thresholds | | | | CRITICALJOBEXECUTIONLAST | Thresholds | | | | WARNINGJOBEXECUTIONSFAILEDPRCT | Thresholds | | | @@ -317,7 +317,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -377,9 +377,9 @@ All available options for each service template are listed below: | --filter-type | Filter jobs by type. | | --timeframe | Timeframe to get BackupJobSession (in seconds. Default: 86400). | | --unit | Select the unit for last execution time threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | -| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %{status}, %{jobName} | -| --warning-execution-status | Set warning threshold for last job execution status (Default: %{status} =~ /warning/i). You can use the following variables like: %{status}, %{jobName} | -| --critical-execution-status | Set critical threshold for last job execution status (Default: %{status} =~ /failed/i). You can use the following variables: %{status}, %{jobName} | +| --unknown-execution-status | Set unknown threshold for last job execution status. You can use the following variables: %\{status\}, %\{jobName\} | +| --warning-execution-status | Set warning threshold for last job execution status (Default: %\{status\} =~ /warning/i). You can use the following variables like: %\{status\}, %\{jobName\} | +| --critical-execution-status | Set critical threshold for last job execution status (Default: %\{status\} =~ /failed/i). You can use the following variables: %\{status\}, %\{jobName\} | | --warning-* --critical-* | Thresholds. Can be: 'jobs-executions-detected', 'job-executions-failed-prct', 'job-execution-last', 'job-running-duration'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-veeam-wsman.md b/pp/integrations/plugin-packs/procedures/applications-veeam-wsman.md index 7f7ef17d1fab..a4caa21828d2 100644 --- a/pp/integrations/plugin-packs/procedures/applications-veeam-wsman.md +++ b/pp/integrations/plugin-packs/procedures/applications-veeam-wsman.md @@ -214,11 +214,11 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | FILTERNAME | Filter job name (can be a regexp) | | | | FILTERSTARTTIME | Filter out jobs whose start date is older than the value specified in seconds | | | | FILTERCOUNTERS | | | | -| OKSTATUS | Set ok threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | -| WARNINGLONG | Set warning threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALLONG | Set critical threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed} | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | %{is\_running} == 0 and not %{status} =~ /Success/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled} | | | +| OKSTATUS | Set ok threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | +| WARNINGLONG | Set warning threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALLONG | Set critical threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | %\{is_running\} == 0 and not %\{status\} =~ /Success/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -238,8 +238,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALLICENSEINSTANCESUSAGE | Thresholds | | | | WARNINGLICENSEINSTANCESUSAGEPRCT | Thresholds | | | | CRITICALLICENSEINSTANCESUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{to}, %{status}, %{type} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{to}, %{status}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{to\}, %\{status\}, %\{type\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{to\}, %\{status\}, %\{type\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -257,8 +257,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALSPACEUSAGEFREE | Thresholds | | | | WARNINGSPACEUSAGEPRCT | Thresholds | | | | CRITICALSPACEUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: 'not %{status} =~ /ordinal\|maintenance/i'). Can use special variables like: %{status}, %{name}, %{type} | not %{status} =~ /ordinal\|maintenance/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{status}, %{name}, %{type} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: 'not %\{status\} =~ /ordinal\|maintenance/i'). Can use special variables like: %\{status\}, %\{name\}, %\{type\} | not %\{status\} =~ /ordinal\|maintenance/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{status\}, %\{name\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -267,8 +267,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------|:-----------:| | FILTERNAME | Filter job name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | %{enabled} == 1 and not %{last\_result} =~ /Success\|None/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | %\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\} | | | | WARNINGTOTAL | Set warning threshold for total jobs | | | | CRITICALTOTAL | Set critical threshold for total jobs | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -288,8 +288,8 @@ yum install centreon-plugin-Applications-Backup-Veeam-Wsman | CRITICALJOBSFAILED | Thresholds | | | | WARNINGJOBSSUCCESS | Thresholds | | | | CRITICALJOBSSUCCESS | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: 'not %{status} =~ /success/i'). Can use special variables like: %{name}, %{type}, %{status}, %{duration} | not %{status} =~ /success/i | | -| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: 'not %\{status\} =~ /success/i'). Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | not %\{status\} =~ /success/i | | +| WARNINGSTATUS | Set warning threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -316,7 +316,7 @@ is able to monitor a resource using a command like this one (replace the sample --wsman-auth-method='basic' \ --filter-name="" \ --warning-status="" \ - --critical-status="%{enabled} == 1 and not %{last_result} =~ /Success|None/i" \ + --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \ --warning-total="" \ --critical-total="" \ --verbose @@ -378,7 +378,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -427,11 +427,11 @@ All available options for each service template are listed below: | --filter-type | Filter job type (can be a regexp). | | --filter-start-time | Filter job with start time greater than current time less value in seconds. | | --filter-end-time | Filter job with end time greater than current time less value in seconds (Default: 86400). | -| --ok-status | Set ok threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-status | Set warning threshold for status. Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --critical-status | Set critical threshold for status (Default: '%{is\_running} == 0 and not %{status} =~ /Success/i'). Can use special variables like: %{display}, %{status}, %{type}, %{is\_running}, %{scheduled}. | -| --warning-long | Set warning threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed}. | -| --critical-long | Set critical threshold for long jobs. Can use special variables like: %{display}, %{status}, %{type}, %{elapsed}. | +| --ok-status | Set ok threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --critical-status | Set critical threshold for status (Default: '%\{is_running\} == 0 and not %\{status\} =~ /Success/i'). Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{is_running\}, %\{scheduled\}. | +| --warning-long | Set warning threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | +| --critical-long | Set critical threshold for long jobs. Can use special variables like: %\{display\}, %\{status\}, %\{type\}, %\{elapsed\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -445,8 +445,8 @@ All available options for each service template are listed below: | --filter-to | Filter licenses by person/organization (can be a regexp). | | --filter-type | Filter licenses by type (can be a regexp). | | --filter-status | Filter licenses by status (can be a regexp). | -| --warning-status | Set warning threshold for status. Can use special variables like: %{to}, %{status}, %{type}. | -| --critical-status | Set critical threshold for status (Default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{to}, %{status}, %{type}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{to\}, %\{status\}, %\{type\}. | +| --critical-status | Set critical threshold for status (Default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{to\}, %\{status\}, %\{type\}. | | --unit | Select the unit for expires threshold. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'total', 'expires', 'license-instances-usage', 'license-instances-free', 'license-instances-usage-prct'. | @@ -460,8 +460,8 @@ All available options for each service template are listed below: | --filter-name | Filter repositories by name (can be a regexp). | | --exclude-name | Exclude repositories by name (regexp can be used). | | --filter-type | Filter repositories by type (can be a regexp). | -| --warning-status | Set warning threshold for status. Can use special variables like: %{status}, %{name}, %{type}. | -| --critical-status | Set critical threshold for status (Default: 'not %{status} =~ /ordinal\|maintenance/i'). Can use special variables like: %{status}, %{name}, %{type}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{status\}, %\{name\}, %\{type\}. | +| --critical-status | Set critical threshold for status (Default: 'not %\{status\} =~ /ordinal\|maintenance/i'). Can use special variables like: %\{status\}, %\{name\}, %\{type\}. | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | @@ -474,9 +474,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Set unknown threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --warning-status | Set warning threshold for status (Default: '') Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | -| --critical-status | Set critical threshold for status (Default: '%{enabled} == 1 and not %{last\_result} =~ /Success\|None/i'). Can use special variables like: %{display}, %{enabled}, %{type}, %{last\_result}, %{last\_state}. | +| --unknown-status | Set unknown threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --warning-status | Set warning threshold for status (Default: '') Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | +| --critical-status | Set critical threshold for status (Default: '%\{enabled\} == 1 and not %\{last_result\} =~ /Success\|None/i'). Can use special variables like: %\{display\}, %\{enabled\}, %\{type\}, %\{last_result\}, %\{last_state\}. | | --warning-total | Set warning threshold for total jobs. | | --critical-total | Set critical threshold for total jobs. | @@ -490,9 +490,9 @@ All available options for each service template are listed below: | --filter-name | Filter job name (can be a regexp). | | --exclude-name | Exclude job name (regexp can be used). | | --filter-type | Filter job type (can be a regexp). | -| --unknown-status | Set unknown threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | -| --warning-status | Set warning threshold for status. Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | -| --critical-status | Set critical threshold for status (Default: 'not %{status} =~ /success/i'). Can use special variables like: %{name}, %{type}, %{status}, %{duration}. | +| --unknown-status | Set unknown threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --warning-status | Set warning threshold for status. Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | +| --critical-status | Set critical threshold for status (Default: 'not %\{status\} =~ /success/i'). Can use special variables like: %\{name\}, %\{type\}, %\{status\}, %\{duration\}. | | --warning-* --critical-* | Thresholds. Can be: 'jobs-detected', 'jobs-success', 'jobs-warning', 'jobs-failed'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-vernemq-restapi.md b/pp/integrations/plugin-packs/procedures/applications-vernemq-restapi.md index f1202a5fad0e..25c1b148a8cb 100644 --- a/pp/integrations/plugin-packs/procedures/applications-vernemq-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-vernemq-restapi.md @@ -208,13 +208,13 @@ yum install centreon-plugin-Applications-Vernemq-Restapi | Macro | Description | Default value | Mandatory | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | FILTERNAME | Filter cluster name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGNOTRUNNING | Thresholds | | | | CRITICALNOTRUNNING | Thresholds | | | | WARNINGRUNNING | Thresholds | | | | CRITICALRUNNING | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "notRunning"'). You can use the following variables: %{status}, %{display} | %{status} eq "notRunning" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "notRunning"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "notRunning" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -223,13 +223,13 @@ yum install centreon-plugin-Applications-Vernemq-Restapi | Macro | Description | Default value | Mandatory | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERTYPE | Filter listener type (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGNOTRUNNING | Thresholds | | | | CRITICALNOTRUNNING | Thresholds | | | | WARNINGRUNNING | Thresholds | | | | CRITICALRUNNING | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "running"'). You can use the following variables: %{status}, %{display} | %{status} ne "running" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "running"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} ne "running" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -335,7 +335,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -377,9 +377,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter cluster name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "notRunning"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "notRunning"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'running', 'notrunning'. | @@ -388,9 +388,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-type | Filter listener type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "running"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "running"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'running', 'notrunning'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md b/pp/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md index 61a63a8bb43f..e6fe19066750 100644 --- a/pp/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-vmware-vcsa-restapi.md @@ -161,9 +161,9 @@ yum install centreon-plugin-Applications-Vmware-Vcsa-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERSERVICE | Define which services should be monitored based on the services' names. This option will be treated as a regular expression. | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{health} !~ /green/'). You can use the following variables: %{health}, %{display} | %{health} !~ /green/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{health\} !~ /green/'). You can use the following variables: %\{health\}, %\{display\} | %\{health\} !~ /green/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -189,7 +189,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-service='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{health} !~ /green/' \ + --critical-status='%\{health\} !~ /green/' \ --verbose ``` @@ -249,7 +249,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -294,9 +294,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-service | Define which services should be monitored based on the services' names. This option will be treated as a regular expression. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{health} !~ /green/'). You can use the following variables: %{health}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{health\} !~ /green/'). You can use the following variables: %\{health\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md b/pp/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md index 31b86d8d30eb..71b256ed564b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-voip-3cx-restapi.md @@ -175,7 +175,7 @@ yum install centreon-plugin-Applications-Voip-3cx-Restapi | Macro | Description | Default value | Mandatory | |:-----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{error}, %{service} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{error\}, %\{service\} | | | | WARNINGCALLSACTIVEFREE | Thresholds | | | | CRITICALCALLSACTIVEFREE | Thresholds | | | | WARNINGCALLSACTIVEUSAGE | Thresholds | | | @@ -184,8 +184,8 @@ yum install centreon-plugin-Applications-Voip-3cx-Restapi | CRITICALCALLSACTIVEUSAGEPRCT | Thresholds | | | | WARNINGEXTENSIONSREGISTERED | Thresholds | | | | CRITICALEXTENSIONSREGISTERED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{error} =~ /false/'). You can use the following variables: %{error}, %{service} | %{error} =~ /true/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{error}, %{service} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{error\} =~ /false/'). You can use the following variables: %\{error\}, %\{service\} | %\{error\} =~ /true/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{error\}, %\{service\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -211,7 +211,7 @@ is able to monitor a resource using a command like this one (replace the sample --3cx-version='18.0.9.20' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{error} =~ /true/' \ + --critical-status='%\{error\} =~ /true/' \ --warning-calls-active-usage='' \ --critical-calls-active-usage='' \ --warning-calls-active-free='' \ @@ -279,7 +279,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -305,9 +305,9 @@ All available options for each service template are listed below: | --api-username | Define the username for authentication. | | --api-password | Define the password associated with the username. | | --timeout | Define the timeout in seconds (default: 30). | -| --unknown-http-status | Define the conditions to match on the HTTP Status for the returned status to be UNKNOWN. Default: '%{http\_code} \< 200 or %{http\_code} \>= 300' | -| --warning-http-status | Define the conditions to match on the HTTP Status for the returned status to be WARNING. Example: '%{http\_code} == 500' | -| --critical-http-status | Define the conditions to match on the HTTP Status for the returned status to be CRITICAL. Example: '%{http\_code} == 500' | +| --unknown-http-status | Define the conditions to match on the HTTP Status for the returned status to be UNKNOWN. Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300' | +| --warning-http-status | Define the conditions to match on the HTTP Status for the returned status to be WARNING. Example: '%\{http_code\} == 500' | +| --critical-http-status | Define the conditions to match on the HTTP Status for the returned status to be CRITICAL. Example: '%\{http_code\} == 500' | | --http-peer-addr | Set the address you want to connect to. Useful if hostname is only a vhost, to avoid IP resolution. | | --proxyurl | Proxy URL. Example: http://my.proxy:3128 | | --proxypac | Proxy pac file (can be a URL or a local file). | @@ -328,9 +328,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-category | Filter updates' category. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{error}, %{service} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{error}, %{service} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{error} =~ /false/'). You can use the following variables: %{error}, %{service} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{error\}, %\{service\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{error\}, %\{service\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{error\} =~ /false/'). You can use the following variables: %\{error\}, %\{service\} | | --warning-* --critical-* | Thresholds. Can be: 'calls-active-usage', 'calls-active-free', 'calls-active-usage-prct', 'extensions-registered'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-wazuh-restapi.md b/pp/integrations/plugin-packs/procedures/applications-wazuh-restapi.md index e63a4342ac24..3a27ec9e1b0b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-wazuh-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-wazuh-restapi.md @@ -188,8 +188,8 @@ yum install centreon-plugin-Applications-Wazuh-Restapi | CRITICALNEVERCONNECTED | Thresholds | | | | WARNINGPENDING | Thresholds | | | | CRITICALPENDING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -209,8 +209,8 @@ yum install centreon-plugin-Applications-Wazuh-Restapi | CRITICALPROCESSESRUNNING | Thresholds | | | | WARNINGPROCESSESSTOPPED | Thresholds | | | | CRITICALPROCESSESSTOPPED | Thresholds | | | -| WARNINGPROCESSSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALPROCESSSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{display} | | | +| WARNINGPROCESSSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALPROCESSSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -301,7 +301,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -358,8 +358,8 @@ All available options for each service template are listed below: |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter agent name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{node\_name}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{node_name\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'active', 'pending', 'neverconnected', 'disconnected'. | @@ -370,8 +370,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-process | Filter process name (can be a regexp). | | --filter-log | Filter log name (can be a regexp). | -| --warning-process-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | -| --critical-process-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status}, %{display} | +| --warning-process-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-process-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'processes-running', 'processes-stopped', 'log-error', 'log-critical', 'log-warning'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md b/pp/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md index beef5aad9a0c..af0249a101c5 100644 --- a/pp/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md +++ b/pp/integrations/plugin-packs/procedures/applications-webservers-iis-restapi.md @@ -204,8 +204,8 @@ yum install centreon-plugin-Applications-Webservers-Iis-Restapi | FILTERNAME | Filter application pool name (can be a regexp) | .* | | | WARNINGREQUESTS | Thresholds | | | | CRITICALREQUESTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{auto\_start} eq "true" and %{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{auto\_start}, %{display} | %{auto\_start} eq "true" and %{status} !~ /starting\|started/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{auto\_start}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | %\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -220,8 +220,8 @@ yum install centreon-plugin-Applications-Webservers-Iis-Restapi | CRITICALCONNECTIONSTOTAL | Thresholds | | | | WARNINGREQUESTS | Thresholds | | | | CRITICALREQUESTS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{display} | %{status} !~ /starting\|started/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /starting\|started/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -251,7 +251,7 @@ is able to monitor a resource using a command like this one (replace the sample --api-token='' \ --filter-name='.*' \ --warning-status='' \ - --critical-status='%{status} !~ /starting|started/' \ + --critical-status='%\{status\} !~ /starting|started/' \ --warning-requests='' \ --critical-requests='' \ --warning-traffic-in='' \ @@ -321,7 +321,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -378,9 +378,9 @@ All available options for each service template are listed below: |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter application pool name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{auto\_start}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{auto\_start}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{auto\_start} eq "true" and %{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{auto\_start}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{auto_start\} eq "true" and %\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{auto_start\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'requests'. | @@ -390,9 +390,9 @@ All available options for each service template are listed below: |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter website name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /starting\|started/'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /starting\|started/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'requests', 'traffic-in', 'traffic-out', 'connections-current', 'connections-total'. | diff --git a/pp/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md b/pp/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md index 01c6f42b817c..dad6a5916c2f 100644 --- a/pp/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md +++ b/pp/integrations/plugin-packs/procedures/applications-webservers-nginx-serverstatus.md @@ -53,16 +53,16 @@ To activate this module, you have to open your nginx configuration file: and check that if not already configured, add the followings lines in 'server' bracket: - server { - ... - location /nginx_status { - stub_status on; + server \{ + ... + location /nginx_status \{ + stub_status on; access_log off; - allow ; - deny all; - } + allow \; + deny all; + \} ... - } + \} Make sure you are allowing Pollers to access this URL. @@ -78,7 +78,7 @@ Nginx must be reloaded to take this modification into account: You can now check the result by accessing the URL - http:///nginx_status + http://\/nginx_status ## Installation diff --git a/pp/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md b/pp/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md index d32f2e2f1042..2984ca55050b 100644 --- a/pp/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md +++ b/pp/integrations/plugin-packs/procedures/applications-webservers-tomcat-webmanager.md @@ -36,7 +36,7 @@ You need to configure an account with the manage role. Add in */usr/share/tomcat6/conf/tomcat-users.xml* file: - + \ Tomcat must be restarted: diff --git a/pp/integrations/plugin-packs/procedures/base-generic.md b/pp/integrations/plugin-packs/procedures/base-generic.md index 8b0438180b49..df0553909d74 100644 --- a/pp/integrations/plugin-packs/procedures/base-generic.md +++ b/pp/integrations/plugin-packs/procedures/base-generic.md @@ -161,7 +161,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-apigateway.md b/pp/integrations/plugin-packs/procedures/cloud-aws-apigateway.md index 605b169183e7..64432769fd47 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-apigateway.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-apigateway.md @@ -333,7 +333,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-backup.md b/pp/integrations/plugin-packs/procedures/cloud-aws-backup.md index 14b83c1af1c7..28cc857d2bba 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-backup.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-backup.md @@ -334,7 +334,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-billing.md b/pp/integrations/plugin-packs/procedures/cloud-aws-billing.md index ce910fccb7db..4457d8bbb62c 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-billing.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-billing.md @@ -301,7 +301,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md index 1ba31685207b..9fbb1e489ba7 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudfront.md @@ -362,7 +362,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md index e5be8c5f3afb..05923d6c0888 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatch.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Cloud-Aws-Cloudwatch-Api | AWSCUSTOMMODE | When a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option | awscli | | | AWSREGION | Set the region name (required) | | X | | FILTERALARMNAME | Filter by alarm name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | %{state\_value} =~ /INSUFFICIENT\_DATA/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | %{state\_value} =~ /ALARM/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | %\{state_value\} =~ /INSUFFICIENT\_DATA/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | %\{state_value\} =~ /ALARM/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -323,7 +323,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -388,8 +388,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-alarm-name | Filter by alarm name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state\_value} =~ /INSUFFICIENT\_DATA/i') You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state\_value} =~ /ALARM/i'). You can use the following variables: %{alarm\_name}, %{state\_value}, %{metric\_name}, %{last\_update} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state_value\} =~ /INSUFFICIENT\_DATA/i') You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state_value\} =~ /ALARM/i'). You can use the following variables: %\{alarm_name\}, %\{state_value\}, %\{metric_name\}, %\{last_update\} | | --memory | Only check new alarms. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md index 41b888b6786b..5417c90677b3 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-cloudwatchlogs.md @@ -215,9 +215,9 @@ yum install centreon-plugin-Cloud-Aws-Cloudwatchlogs-Api | GROUPNAME | Set log group name (required) | | | | STREAMNAME | Filters the results to only logs from the log stream (multiple option) | | | | STARTTIMESINCE | Lookup logs last X seconds ago. If not set: lookup logs since the last execution | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{message}, %{stream\_name}, %{since} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -313,9 +313,9 @@ All available options for each service template are listed below: | --group-name | Set log group name (required). | | --stream-name | Filters the results to only logs from the log stream (multiple option). | | --start-time-since | Lookup logs last X seconds ago. If not set: lookup logs since the last execution. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{message}, %{stream\_name}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{message}, %{stream\_name}, %{since} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{message\}, %\{stream_name\}, %\{since\} | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | | --dyn-mode | Specify a mode with the module's path (advanced). | | --list-mode | List all available modes. | @@ -328,7 +328,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-directconnect.md b/pp/integrations/plugin-packs/procedures/cloud-aws-directconnect.md index c53e493d38a7..8615630daf08 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-directconnect.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-directconnect.md @@ -253,8 +253,8 @@ yum install centreon-plugin-Cloud-Aws-Directconnect-Api | CRITICALCONNECTIONPACKETSEGRESS | Threshold | | | | WARNINGCONNECTIONPACKETSINGRESS | Threshold | | | | CRITICALCONNECTIONPACKETSINGRESS | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -266,8 +266,8 @@ yum install centreon-plugin-Cloud-Aws-Directconnect-Api | TIMEFRAME | Set timeframe in seconds | 600 | | | PERIOD | Set period in seconds | 60 | | | FILTERVIRTUALINTERFACEID | Filter virtual interface ID (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | | | WARNINGVIRTUALINTERFACEEGRESS | Threshold | | | | CRITICALVIRTUALINTERFACEEGRESS | Threshold | | | | WARNINGVIRTUALINTERFACEINGRESS | Threshold | | | @@ -381,7 +381,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -435,8 +435,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-connection-id | Filter connection ID (can be a regexp). | | --filter-metric | Filter metrics (can be: 'ConnectionBpsEgress', 'ConnectionBpsIngress', 'ConnectionPpsEgress', 'ConnectionPpsIngress', 'ConnectionLightLevelTx', 'ConnectionLightLevelRx') (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{bandwidth}, %{connectionName} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{bandwidth\}, %\{connectionName\} | | --warning-* --critical-* | Thresholds. Can be 'connection-egress', 'connection-ingress', 'connection-packets-egress', 'connection-packets-ingress', 'connection-ligh-level-outbound', 'connection-ligh-level-inbound. | @@ -447,8 +447,8 @@ All available options for each service template are listed below: | --filter-connection-id | Filter connection ID (can be a regexp). | | --filter-virtual-interface-id | Filter virtual interface ID (can be a regexp). | | --filter-metric | Filter metrics (can be: 'VirtualInterfaceBpsEgress', 'VirtualInterfaceBpsIngress', 'VirtualInterfacePpsEgress', 'VirtualInterfacePpsIngress') (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{vlan}, %{type}, %{virtualInterfaceId} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{vlan\}, %\{type\}, %\{virtualInterfaceId\} | | --warning-* --critical-* | Thresholds. Can be 'virtual-interface-egress', 'virtual-interface-ingress', 'virtual-interface-packets-egress', 'virtual-interface-packets-ingress'. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-ebs.md b/pp/integrations/plugin-packs/procedures/cloud-aws-ebs.md index 50dc6521e692..f41951463df3 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-ebs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-ebs.md @@ -368,7 +368,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-ec2.md b/pp/integrations/plugin-packs/procedures/cloud-aws-ec2.md index 01eda0212a52..e780b4b00309 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-ec2.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-ec2.md @@ -397,8 +397,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | FILTERASG | Filter by autoscaling group name (can be a regexp) | .* | | | WARNINGCOUNT | Warning threshold about number of instances in the autoscaling group | | | | CRITICALCOUNT | Critical threshold about number of instances in the autoscaling group | | | -| CRITICALINSTANCES | Set critical threshold for instances states (Default: '%{health} =~ /Healthy/ && %{lifecycle} !~ /InService/'). Can use special variables like: %{health}, %{lifecycle} | %{health} =~ /Healthy/ && %{lifecycle} !~ /InService/ | | -| WARNINGINSTANCES | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %{health}, %{lifecycle} | | | +| CRITICALINSTANCES | Set critical threshold for instances states (Default: '%\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/'). Can use special variables like: %\{health\}, %\{lifecycle\} | %\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/ | | +| WARNINGINSTANCES | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %\{health\}, %\{lifecycle\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -474,8 +474,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | CRITICALRUNNING | Thresholds | | | | WARNINGSHUTTINGDOWN | Thresholds | | | | CRITICALSHUTTINGDOWN | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGSTOPPED | Thresholds | | | | CRITICALSTOPPED | Thresholds | | | | WARNINGSTOPPING | Thresholds | | | @@ -517,8 +517,8 @@ yum install centreon-plugin-Cloud-Aws-Ec2-Api | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. 'status' can be: 'passed', 'failed' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /failed/i'). You can use the following variables: %{status}. 'status' can be: 'passed', 'failed' | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed' | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -642,7 +642,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -727,8 +727,8 @@ All available options for each service template are listed below: |:--------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Possible values: asg / instances | | --filter-asg | Filter by autoscaling group name (can be a regexp). | -| --warning-instances | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %{health}, %{lifecycle} | -| --critical-instances | Set critical threshold for instances states (Default: '%{health} =~ /Healthy/ && %{lifecycle} !~ /InService/'). Can use special variables like: %{health}, %{lifecycle} | +| --warning-instances | Define the conditions to match for the status to be WARNING (Default: ''). Can use special variables like: %\{health\}, %\{lifecycle\} | +| --critical-instances | Set critical threshold for instances states (Default: '%\{health\} =~ /Healthy/ && %\{lifecycle\} !~ /InService/'). Can use special variables like: %\{health\}, %\{lifecycle\} | | --warning-asg-instance-current | Warning threshold about number of instances in the autoscaling group | | --critical-asg-instance-current | Critical threshold about number of instances in the autoscaling group | @@ -773,8 +773,8 @@ All available options for each service template are listed below: | --filter-instanceid | Filter by instance id (can be a regexp). | | --add-uptime | Monitor instances uptime. | | --uptime-unit | Select the unit for uptime threshold. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'pending', 'running', 'shuttingdown', 'terminated', 'stopping', 'stopped', 'uptime'. | @@ -805,8 +805,8 @@ All available options for each service template are listed below: |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --type | Set the instance type (Required) (Can be: 'asg', 'instance'). | | --name | Set the instance name (Required) (can be defined multipletimes). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}. 'status' can be: 'passed', 'failed'. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /failed/i'). You can use the following variables: %{status}. 'status' can be: 'passed', 'failed'. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed'. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}. 'status' can be: 'passed', 'failed'. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-efs.md b/pp/integrations/plugin-packs/procedures/cloud-aws-efs.md index 7a1d80c8f644..956a68196830 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-efs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-efs.md @@ -357,7 +357,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-elasticache.md b/pp/integrations/plugin-packs/procedures/cloud-aws-elasticache.md index 5bacdfc1aaa7..717a020673da 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-elasticache.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-elasticache.md @@ -611,7 +611,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-elb.md b/pp/integrations/plugin-packs/procedures/cloud-aws-elb.md index def925246af6..6e64401a7334 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-elb.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-elb.md @@ -579,7 +579,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-fsx.md b/pp/integrations/plugin-packs/procedures/cloud-aws-fsx.md index 6c360a8f9b6e..87bd7273638b 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-fsx.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-fsx.md @@ -358,7 +358,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-kinesis.md b/pp/integrations/plugin-packs/procedures/cloud-aws-kinesis.md index 5288f26db8af..07fbea9707ca 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-kinesis.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-kinesis.md @@ -352,7 +352,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-lambda.md b/pp/integrations/plugin-packs/procedures/cloud-aws-lambda.md index 27e91141ee89..40c3cb1177fc 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-lambda.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-lambda.md @@ -332,7 +332,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-rds.md b/pp/integrations/plugin-packs/procedures/cloud-aws-rds.md index 7c8b0cfddc77..85ac9902ff67 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-rds.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-rds.md @@ -618,8 +618,8 @@ yum install centreon-plugin-Cloud-Aws-Rds-Api | AWSCUSTOMMODE | | awscli | | | AWSREGION | | | X | | FILTERINSTANCEID | Filter by instance id (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGTOTALAVAILABLE | Warning threshold | | | | CRITICALTOTALAVAILABLE | Critical threshold | | | | WARNINGTOTALBACKINGUP | Warning threshold | | | @@ -873,7 +873,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -995,8 +995,8 @@ All available options for each service template are listed below: |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^total-available$' | | --filter-instanceid | Filter by instance id (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{state\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'total-available', 'total-backing-up', 'total-failed', 'total-maintenance', 'total-stopped', 'total-storage-full'. | | --critical-* | Critical threshold. Can be: 'total-available', 'total-backing-up', 'total-failed', 'total-maintenance', 'total-stopped', 'total-storage-full'. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-s3.md b/pp/integrations/plugin-packs/procedures/cloud-aws-s3.md index 9c95b5e35b2d..e20163ba0a96 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-s3.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-s3.md @@ -377,7 +377,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-ses.md b/pp/integrations/plugin-packs/procedures/cloud-aws-ses.md index 8473861cf802..5ab72410b915 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-ses.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-ses.md @@ -301,7 +301,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-sns.md b/pp/integrations/plugin-packs/procedures/cloud-aws-sns.md index 800e27e90f24..cf4f2d200b06 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-sns.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-sns.md @@ -320,7 +320,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-sqs.md b/pp/integrations/plugin-packs/procedures/cloud-aws-sqs.md index 8047c90e9881..b13117b49670 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-sqs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-sqs.md @@ -340,7 +340,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md b/pp/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md index e91df397b804..0539ff0a3300 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-transitgateway.md @@ -339,7 +339,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-aws-vpn.md b/pp/integrations/plugin-packs/procedures/cloud-aws-vpn.md index 2e85341096a1..14f0e7e83948 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-aws-vpn.md +++ b/pp/integrations/plugin-packs/procedures/cloud-aws-vpn.md @@ -352,7 +352,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md b/pp/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md index 565658f013d9..6a4d0af5f805 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-analytics-eventhubs.md @@ -169,7 +169,7 @@ To use the 'azcli' custom mode, install the required packages on every Centreon monitor Azure Resources using CLI: - The CLI needs at least Python version 2.7 -(). +(\). On RPM-Based distributions, use the command below to install it using *root* or 'sudo': @@ -191,7 +191,7 @@ The shell will output this message including an authentication code: *To sign in, use a web browser to open the page https://microsoft.com/devicelogin* *and enter the code CWT4WQZAD to authenticate.* -Go to and enter the code. +Go to \ and enter the code. Connect using a monitoring service account, as a result, the shell should prompt information below: diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md index 49bec926cbaf..8517e8372b87 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-aks.md @@ -316,10 +316,10 @@ yum install centreon-plugin-Cloud-Azure-Compute-Aks-Api | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| STATUSOK | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| STATUSOK | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -513,7 +513,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -630,10 +630,10 @@ All available options for each service template are listed below: |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md index 58346595d4a5..c62f967bd993 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-functions.md @@ -422,10 +422,10 @@ yum install centreon-plugin-Cloud-Azure-Compute-Functions-Api | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (Default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (Default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -652,7 +652,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -807,10 +807,10 @@ All available options for each service template are listed below: |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or id (Required). | | --resource-group | Set resource group (Required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %{status}, %{summary}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary}. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary}. | -| --ok-status | Define the conditions to match for the status to be OK (Default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). Special variables that can be used: %\{status\}, %\{summary\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --ok-status | Define the conditions to match for the status to be OK (Default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\}. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md index 31fccda2e819..969d46317991 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-compute-virtualmachine.md @@ -196,10 +196,10 @@ running the following command: --client-id='xxxxxxxxx' \ --client-secret='xxxxxxxxx' \ --proxyurl='' \ - --ok-status='%{status} =~ /^Available$/' \ + --ok-status='%\{status\} =~ /^Available$/' \ --warning-status='' \ - --critical-status='%{status} =~ /^Unavailable$/' \ - --unknown-status='%{status} =~ /^Unknown$/' \ + --critical-status='%\{status\} =~ /^Unavailable$/' \ + --unknown-status='%\{status\} =~ /^Unknown$/' \ --api-version=2017-07-01\ ``` diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md index fb3ac3827c83..c0880e875dec 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-cosmosdb.md @@ -325,10 +325,10 @@ yum install centreon-plugin-Cloud-Azure-Database-CosmosDb-Api | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -505,7 +505,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -630,10 +630,10 @@ All available options for each service template are listed below: |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md index 45db8c520d36..6b0ae6795fc1 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-elasticpool.md @@ -456,7 +456,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md index 868ff860cbca..f76a6fa797d2 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-mariadb.md @@ -481,7 +481,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md index b722520b71d8..2eee7d870677 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-mysql.md @@ -529,7 +529,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md index 27e5934dd2db..952f711fea13 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-postgresql.md @@ -461,7 +461,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-redis.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-redis.md index e43c4e8d421a..95b32385eae3 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-redis.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-redis.md @@ -373,10 +373,10 @@ yum install centreon-plugin-Cloud-Azure-Database-Redis-Api | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -533,7 +533,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -688,10 +688,10 @@ All available options for each service template are listed below: |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md index cffa5f63b968..f30444fa3d26 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqldatabase.md @@ -331,10 +331,10 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlDatabase-Api | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| STATUSOK | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | | | -| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | | | +| STATUSOK | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| STATUSUNKNOWN | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | | | +| STATUSCRITICAL | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| STATUSWARNING | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -485,7 +485,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -623,10 +623,10 @@ All available options for each service template are listed below: |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{summary} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). You can use the following variables: %{status}, %{summary} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). You can use the following variables: %{status}, %{summary} | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). You can use the following variables: %{status}, %{summary} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{summary\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). You can use the following variables: %\{status\}, %\{summary\} | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). You can use the following variables: %\{status\}, %\{summary\} | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md index 35c416e6cf09..da99b0c545d1 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlmanagedinstance.md @@ -272,10 +272,10 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlManagedInstance-Api | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Available$/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unknown$/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary} | %{status} =~ /^Unavailable$/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %{status}, %{summary} | | | +| OKSTATUS | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Available$/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unknown$/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\} | %\{status\} =~ /^Unavailable$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %\{status\}, %\{summary\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -402,7 +402,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -517,10 +517,10 @@ All available options for each service template are listed below: |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --resource | Set resource name or ID (required). | | --resource-group | Set resource group (required if resource's name is used). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %{status}, %{summary}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^Unavailable$/'). Special variables that can be used: %{status}, %{summary}. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /^Unknown$/'). Special variables that can be used: %{status}, %{summary}. | -| --ok-status | Define the conditions to match for the status to be OK (default: '%{status} =~ /^Available$/'). Special variables that can be used: %{status}, %{summary}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). Special variables that can be used: %\{status\}, %\{summary\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^Unavailable$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /^Unknown$/'). Special variables that can be used: %\{status\}, %\{summary\}. | +| --ok-status | Define the conditions to match for the status to be OK (default: '%\{status\} =~ /^Available$/'). Special variables that can be used: %\{status\}, %\{summary\}. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md index 8f8650842e8b..aced37bd0dbf 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-database-sqlserver.md @@ -209,8 +209,8 @@ yum install centreon-plugin-Cloud-Azure-Database-SqlServer-Api | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "Ready"'). You can use the following variables: %{state}, %{fqdn}, %{display} | %{state} ne "Ready" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{fqdn}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "Ready"'). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | %\{state\} ne "Ready" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -238,7 +238,7 @@ is able to monitor an Azure Instance using a command like this one (replace the --location='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{state} ne "Ready"' + --critical-status='%\{state\} ne "Ready"' ``` The expected command output is shown below: @@ -376,7 +376,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -398,8 +398,8 @@ All available options for each service template are listed below: | --resource-group | Set resource group. | | --location | Set resource location. | | --filter-name | Filter server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{fqdn}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "Ready"'). You can use the following variables: %{state}, %{fqdn}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "Ready"'). You can use the following variables: %\{state\}, %\{fqdn\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md b/pp/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md index 792b42bbaa9e..d849061f2ffe 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-datafactory-factories.md @@ -328,7 +328,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-management-costs.md b/pp/integrations/plugin-packs/procedures/cloud-azure-management-costs.md index 399170475219..f38920770e1e 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-management-costs.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-management-costs.md @@ -405,7 +405,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md b/pp/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md index f90d29267df5..47cf0b2293ff 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-management-monitor.md @@ -305,7 +305,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md b/pp/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md index a028be5a6a91..fd1cd6d5d7e8 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-management-recovery.md @@ -156,7 +156,7 @@ running the following command: --proxyurl='' \ --vault-name='vault123' \ --warning-status='' \ - --critical-status='%{status} eq "Failed"' \ + --critical-status='%\{status\} eq "Failed"' \ --warning-total-completed='' \ --critical-total-completed='' \ --warning-total-failed='' \ diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-management-resource.md b/pp/integrations/plugin-packs/procedures/cloud-azure-management-resource.md index 739c7acafd2d..8773b6957aa8 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-management-resource.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-management-resource.md @@ -32,7 +32,7 @@ The login and access token handling will be made by the plugin itself. ### Azure CLI 2.0 (for 'azcli' custom mode) The CLI needs at least Python version 2.7 -(). +(\). On CentOS/RedHat, install with following commands: @@ -47,7 +47,7 @@ The shell should prompt: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code CWT4WQZAD to authenticate. -Go to and enter the given code. +Go to \ and enter the given code. Log in with your account credentials. You should use a service account. Application is not yet supported. @@ -55,18 +55,18 @@ Application is not yet supported. The command line should now show: [ - { + \{ "cloudName": "AzureCloud", "id": "0ef83f3a-d83e-2039-d930-309df93acd93d", "isDefault": true, "name": "N/A(tenant level account)", "state": "Enabled", "tenantId": "0ef83f3a-03cd-2039-d930-90fd39ecd048", - "user": { + "user": \{ "name": "email@mycompany.onmicrosoft.com", "type": "user" - } - } + \} + \} ] You now have a hidden azure directory where your token is stored in an @@ -121,5 +121,5 @@ Click on the *Save* button. ## Available metrics Go to - +\ to see the description of return metrics for this Azure service. diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md b/pp/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md index 7c73633ebfef..662bb42ac3cd 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-network-networkinterface.md @@ -32,7 +32,7 @@ The login and access token handling will be made by the plugin itself. ### Azure CLI 2.0 (for 'azcli' custom mode) The CLI needs at least Python version 2.7 -(). +(\). On CentOS/RedHat, install with following commands: @@ -47,7 +47,7 @@ The shell should prompt: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code CWT4WQZAD to authenticate. -Go to and enter the given code. +Go to \ and enter the given code. Log in with your account credentials. You should use a service account. Application is not yet supported. @@ -55,18 +55,18 @@ Application is not yet supported. The command line should now show: [ - { + \{ "cloudName": "AzureCloud", "id": "0ef83f3a-d83e-2039-d930-309df93acd93d", "isDefault": true, "name": "N/A(tenant level account)", "state": "Enabled", "tenantId": "0ef83f3a-03cd-2039-d930-90fd39ecd048", - "user": { + "user": \{ "name": "email@mycompany.onmicrosoft.com", "type": "user" - } - } + \} + \} ] You now have a hidden azure directory where your token is stored in an @@ -123,5 +123,5 @@ Click on the *Save* button. ## Available metrics Go to - +\ to see the description of return metrics for this Azure service. diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md b/pp/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md index 73a7ecdb560a..747a62545e60 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-network-publicip.md @@ -148,8 +148,8 @@ user account and test the Plugin by running the following command: --resource='IPA001ABCD' \ --timeframe='900' \ --interval='PT5M' \ - --critical-provisioning-state='%{state} =~ /Failed/i' \ - --critical-ddos-status='%{status} =~ /DDOS Attack ongoing/i' + --critical-provisioning-state='%\{state\} =~ /Failed/i' \ + --critical-ddos-status='%\{status\} =~ /DDOS Attack ongoing/i' ``` Expected command output is shown below: diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md b/pp/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md index a6c499d9507b..999c18597954 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-network-virtualnetwork.md @@ -141,7 +141,7 @@ running the following command: --proxyurl='' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{peering_state} ne "Connected" || %{provisioning_state} ne "Succeeded"' \ + --critical-status='%\{peering_state\} ne "Connected" || %\{provisioning_state\} ne "Succeeded"' \ ``` The expected command output is shown below: diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md b/pp/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md index 95e1ff1da38c..24416a5f1441 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-network-vpngateway.md @@ -173,10 +173,10 @@ running the following command: --client-id='' \ --client-secret='' \ --proxyurl='' \ - --ok-status='%{status} =~ /^Available$/' \ + --ok-status='%\{status\} =~ /^Available$/' \ --warning-status='' \ - --critical-status='%{status} =~ /^Unavailable$/' \ - --unknown-status='%{status} =~ /^Unknown$/' \ + --critical-status='%\{status\} =~ /^Unavailable$/' \ + --unknown-status='%\{status\} =~ /^Unknown$/' \ --api-version=2017-07-01\ ``` diff --git a/pp/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md b/pp/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md index 24146ff7d79f..9a93b6c16034 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md +++ b/pp/integrations/plugin-packs/procedures/cloud-azure-policyinsights-policystates.md @@ -171,7 +171,7 @@ Once the template is applied, fill in the corresponding macros. Some macros are | | RESOURCELOCATION | Set resource location (Optional) | | | | RESOURCETYPE | Set resource type (Optional) | | | | POLICYNAME | Set policy name (Optional) | | -| | CRITICALCOMPLIANCESTATE | | %{compliance_state} eq "NonCompliant" | +| | CRITICALCOMPLIANCESTATE | | %\{compliance_state\} eq "NonCompliant" | | | WARNINGCOMPLIANCESTATE | | | | | WARNINGNONCOMPLIANTPOLICIES | | | | | CRITICALNONCOMPLIANTPOLICIES | | | diff --git a/pp/integrations/plugin-packs/procedures/cloud-cadvisor-api.md b/pp/integrations/plugin-packs/procedures/cloud-cadvisor-api.md index b0512c87c080..bd400ecc01a3 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-cadvisor-api.md +++ b/pp/integrations/plugin-packs/procedures/cloud-cadvisor-api.md @@ -386,7 +386,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-kubernetes-api.md b/pp/integrations/plugin-packs/procedures/cloud-kubernetes-api.md index 9e2de104d07c..ac131644787c 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-kubernetes-api.md +++ b/pp/integrations/plugin-packs/procedures/cloud-kubernetes-api.md @@ -1031,8 +1031,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERTYPE | Filter event type (can be a regexp) | .* | | | FILTERNAMESPACE | Filter namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{type} =~ /warning/i') Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen} | %{type} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} =~ /error/i'). Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen} | %{type} =~ /error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{type\} =~ /warning/i') Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\} | %\{type\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} =~ /error/i'). Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\} | %\{type\} =~ /error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1042,8 +1042,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERCRONJOB | Filter CronJob name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter CronJob namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1053,8 +1053,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERDAEMONSET | Filter DaemonSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter DaemonSet namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{up_to_date\} \< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1064,8 +1064,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:-----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERDEPLOYMENT | Filter deployment name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter deployment namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{up_to_date\} \< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1073,8 +1073,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '(%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i)'). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name} | (%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i) | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '(%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i)'). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\} | (%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i) | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1101,8 +1101,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------|:-----------:| | FILTERPERSISTENTVOLUME | Filter persistent volume name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter persistent volume name (can be a regexp). | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Bound\|Available\|Released/i'). You can use the following variables: %{name}, %{phase} | %{phase} !~ /Bound\|Available\|Released/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{phase} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Bound\|Available\|Released/i'). You can use the following variables: %\{name\}, %\{phase\} | %\{phase\} !~ /Bound\|Available\|Released/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{phase\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1115,10 +1115,10 @@ yum install centreon-plugin-Cloud-Kubernetes-Api | UNITS | Units of thresholds (default: '%') ('%', 'count') | % | | | WARNINGCONTAINERSREADY | Warning threshold | | | | CRITICALCONTAINERSREADY | Critical threshold | | | -| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i \|\| %{state} !~ /^ready$/'). You can use the following variables: %{status}, %{state}, %{name} | %{status} !~ /running/i \|\| %{state} !~ /^ready$/ | | -| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name} | | | -| CRITICALPODSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name}, %{namespace} | %{status} !~ /running/i | | -| WARNINGPODSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}, %{namespace} | | | +| CRITICALCONTAINERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/'). You can use the following variables: %\{status\}, %\{state\}, %\{name\} | %\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/ | | +| WARNINGCONTAINERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALPODSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\} | %\{status\} !~ /running/i | | +| WARNINGPODSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\} | | | | WARNINGRESTARTSCOUNT | Warning threshold | | | | CRITICALRESTARTSCOUNT | Critical threshold | | | | WARNINGTOTALRESTARTSCOUNT | Warning threshold | | | @@ -1132,8 +1132,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERREPLICATSET | Filter ReplicaSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter ReplicaSet namespace (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | %{ready} \< %{desired} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | %\{ready\} \< %\{desired\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1143,8 +1143,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:----------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERREPLICATIONCONTROLLER | Filter ReplicationController name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter ReplicationController namespace (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | %{ready} \< %{desired} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | %\{ready\} \< %\{desired\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1154,8 +1154,8 @@ yum install centreon-plugin-Cloud-Kubernetes-Api |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | FILTERSTATEFULSET | Filter StatefulSet name (can be a regexp) | .* | | | FILTERNAMESPACE | Filter StatefulSet namespace (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready} | %{ready} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\} | %\{up_to_date\} \< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\} | %\{ready\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -1184,8 +1184,8 @@ is able to monitor a resource using a command like this one (replace the sample --timeout='10' \ --filter-name='.*' \ --filter-namespace='.*' \ - --warning-status='%{up_to_date} < %{desired}' \ - --critical-status='%{ready} < %{desired}' \ + --warning-status='%\{up_to_date\} < %\{desired\}' \ + --critical-status='%\{ready\} < %\{desired\}' \ --verbose ``` @@ -1295,7 +1295,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1377,8 +1377,8 @@ All available options for each service template are listed below: | --command-options | Command options (default: none). | | --filter-type | Filter event type (can be a regexp). | | --filter-namespace | Filter namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{type} =~ /warning/i') Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} =~ /error/i'). Can use special variables like: %{name}, %{namespace}, %{type}, %{object}, %{message}, %{count}, %{first\_seen}, %{last\_seen}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{type\} =~ /warning/i') Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} =~ /error/i'). Can use special variables like: %\{name\}, %\{namespace\}, %\{type\}, %\{object\}, %\{message\}, %\{count\}, %\{first_seen\}, %\{last_seen\}. | @@ -1387,8 +1387,8 @@ All available options for each service template are listed below: |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter CronJob name (can be a regexp). | | --filter-namespace | Filter CronJob namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{name}, %{namespace}, %{active}, %{last\_schedule}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{name\}, %\{namespace\}, %\{active\}, %\{last_schedule\}. | @@ -1397,8 +1397,8 @@ All available options for each service template are listed below: |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter DaemonSet name (can be a regexp). | | --filter-namespace | Filter DaemonSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\}. | @@ -1407,8 +1407,8 @@ All available options for each service template are listed below: |:-------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter deployment name (can be a regexp). | | --filter-namespace | Filter deployment namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}. | @@ -1416,8 +1416,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter node name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '(%{type} =~ /Ready/i && %{status} !~ /True/i) \|\| (%{type} =~ /.*Pressure/i && %{status} !~ /False/i)'). You can use the following variables: %{type}, %{status}, %{reason}, %{message}, %{name}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '(%\{type\} =~ /Ready/i && %\{status\} !~ /True/i) \|\| (%\{type\} =~ /.*Pressure/i && %\{status\} !~ /False/i)'). You can use the following variables: %\{type\}, %\{status\}, %\{reason\}, %\{message\}, %\{name\}. | @@ -1433,8 +1433,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter persistent volume name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{phase}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Bound\|Available\|Released/i'). You can use the following variables: %{name}, %{phase}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{phase\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Bound\|Available\|Released/i'). You can use the following variables: %\{name\}, %\{phase\}. | @@ -1444,10 +1444,10 @@ All available options for each service template are listed below: | --filter-name | Filter pod name (can be a regexp). | | --filter-namespace | Filter pod namespace (can be a regexp). | | --extra-filter | Add an extra filter based on labels (can be defined multiple times) Example : --extra-filter='app=mynewapp' | -| --warning-pod-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}, %{namespace}. | -| --critical-pod-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{status}, %{name}, %{namespace}. | -| --warning-container-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{name}. | -| --critical-container-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i \|\| %{state} !~ /^ready$/'). You can use the following variables: %{status}, %{state}, %{name}. | +| --warning-pod-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\}. | +| --critical-pod-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{status\}, %\{name\}, %\{namespace\}. | +| --warning-container-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{name\}. | +| --critical-container-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i \|\| %\{state\} !~ /^ready$/'). You can use the following variables: %\{status\}, %\{state\}, %\{name\}. | | --warning-* | Warning threshold. Can be: 'containers-ready', 'total-restarts-count' (count), 'restarts-count' (count). | | --critical-* | Critical threshold. Can be: 'containers-ready', 'total-restarts-count' (count), 'restarts-count' (count). | | --units | Units of thresholds (default: '%') ('%', 'count'). | @@ -1459,8 +1459,8 @@ All available options for each service template are listed below: |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ReplicaSet name (can be a regexp). | | --filter-namespace | Filter ReplicaSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | @@ -1469,8 +1469,8 @@ All available options for each service template are listed below: |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ReplicationController name (can be a regexp). | | --filter-namespace | Filter ReplicationController namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{ready\}. | @@ -1479,8 +1479,8 @@ All available options for each service template are listed below: |:-------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter StatefulSet name (can be a regexp). | | --filter-namespace | Filter StatefulSet namespace (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ready} \< %{desired}'). You can use the following variables: %{name}, %{namespace}, %{desired}, %{current}, %{up\_to\_date}, %{ready}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ready\} \< %\{desired\}'). You can use the following variables: %\{name\}, %\{namespace\}, %\{desired\}, %\{current\}, %\{up_to_date\}, %\{ready\}. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md index a51135e87839..71c8bf34a972 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-exchange.md @@ -242,8 +242,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Exchange-Api | CRITICALACTIVEMAILBOXES | Critical threshold | | | | WARNINGITEMS | Warning threshold | | | | CRITICALITEMS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | %{used} \> %{issue\_warning\_quota} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | %{used} \> %{prohibit\_send\_quota} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | %\{used\} \> %\{issue_warning_quota\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | %\{used\} \> %\{prohibit_send_quota\} | | | WARNINGTOTALUSAGEACTIVE | Warning threshold | | | | CRITICALTOTALUSAGEACTIVE | Critical threshold | | | | WARNINGTOTALUSAGEINACTIVE | Warning threshold | | | @@ -341,7 +341,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -409,8 +409,8 @@ All available options for each service template are listed below: | --filter-mailbox | Filter mailboxes. | | --warning-* | Warning threshold. Can be: 'active-mailboxes', 'total-usage-active' (count), 'total-usage-inactive' (count). | | --critical-* | Critical threshold. Can be: 'active-mailboxes', 'total-usage-active' (count), 'total-usage-inactive' (count). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{used} \> %{issue\_warning\_quota}'). You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{used} \> %{prohibit\_send\_quota}'). You can use the following variables: %{used}, %{issue\_warning\_quota}, %{prohibit\_send\_quota}, %{prohibit\_send\_receive\_quota} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{used\} \> %\{issue_warning_quota\}'). You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{used\} \> %\{prohibit_send_quota\}'). You can use the following variables: %\{used\}, %\{issue_warning_quota\}, %\{prohibit_send_quota\}, %\{prohibit_send_receive_quota\} | | --filter-counters | Only display some counters (regexp can be used). Example to hide per user counters: --filter-counters='active\|total' (default: 'active\|total') | | --units | Unit of thresholds (default: '%') ('%', 'count'). | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md index c36034c7446c..9a21891a2be9 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-management.md @@ -280,12 +280,12 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | FILTERAPPNAME | Filter applications (can be a regexp) | | | | WARNINGKEYEXPIRES | Thresholds | | | | CRITICALKEYEXPIRES | Thresholds | | | -| CRITICALKEYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name} | %{status} =~ /expired/i | | -| WARNINGKEYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name} | | | +| CRITICALKEYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | %\{status\} =~ /expired/i | | +| WARNINGKEYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | | | | WARNINGPASSWORDEXPIRES | Thresholds | | | | CRITICALPASSWORDEXPIRES | Thresholds | | | -| CRITICALPASSWORDSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name} | %{status} =~ /expired/i | | -| WARNINGPASSWORDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name} | | | +| CRITICALPASSWORDSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | %\{status\} =~ /expired/i | | +| WARNINGPASSWORDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -294,8 +294,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | Macro | Description | Default value | Mandatory | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERSERVICENAME | Filter services (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %{service\_name}, %{status}, %{classification} | %{status} !~ /serviceOperational\|serviceRestored/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{service\_name}, %{status}, %{classification} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | %\{status\} !~ /serviceOperational\|serviceRestored/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -304,8 +304,8 @@ yum install centreon-plugin-Cloud-Microsoft-Office365-Management-Api | Macro | Description | Default value | Mandatory | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERSKUPARTNUMBER | Filter subscriptions by SKU part number (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | %{capabilityStatus} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | %\{capabilityStatus\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | | | | WARNINGSUBSCRIPTIONUSAGE | Thresholds | | | | CRITICALSUBSCRIPTIONUSAGE | Thresholds | | | | WARNINGSUBSCRIPTIONUSAGEFREE | Thresholds | | | @@ -333,7 +333,7 @@ is able to monitor a resource using a command like this one (replace the sample --client-id='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxx' \ --client-secret='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' \ --filter-sku-part-number='' \ - --warning-status='%{capabilityStatus} =~ /warning/i' \ + --warning-status='%\{capabilityStatus\} =~ /warning/i' \ --critical-status='' \ --warning-subscription-usage='' \ --critical-subscription-usage='' \ @@ -401,7 +401,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -456,10 +456,10 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-app-name | Filter applications (can be a regexp). | -| --warning-key-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --critical-key-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --warning-password-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{id}, %{app\_name}. | -| --critical-password-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired/i'). You can use the following variables: %{status}, %{id}, %{app\_name}. | +| --warning-key-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --critical-key-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --warning-password-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | +| --critical-password-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{status\}, %\{id\}, %\{app_name\}. | | --unit | Select the time unit for the expiration thresholds. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is secondss. | | --warning-* --critical-* | Thresholds. Can be: 'key-expires', 'password-expires'. | @@ -469,8 +469,8 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-service-name | Filter services (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{service\_name}, %{status}, %{classification} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %{service\_name}, %{status}, %{classification} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /serviceOperational\|serviceRestored/i'). You can use the following variables: %\{service_name\}, %\{status\}, %\{classification\} | @@ -478,8 +478,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-sku-part-number | Filter subscriptions by SKU part number (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{capabilityStatus}, %{skuPartNumber} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{capabilityStatus\}, %\{skuPartNumber\} | | --warning-* --critical-* | Thresholds. Can be: 'subscription-usage', 'subscription-usage-free', 'subscription-usage-prct'. | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md index 5944d1d18fb9..d7757d0aa9ad 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-onedrive.md @@ -326,7 +326,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md index 8b70fa8044f8..e729e8db8c34 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-sharepoint.md @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md index 39f3c2a4adcc..4767e3255683 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-skype.md @@ -345,7 +345,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md index 9ba36cffd97d..b623101d45b5 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md +++ b/pp/integrations/plugin-packs/procedures/cloud-microsoft-office365-teams.md @@ -354,7 +354,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/cloud-prometheus-api.md b/pp/integrations/plugin-packs/procedures/cloud-prometheus-api.md index 9a7347cd5b59..3ce4818dad50 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-prometheus-api.md +++ b/pp/integrations/plugin-packs/procedures/cloud-prometheus-api.md @@ -166,7 +166,7 @@ user account and test the Plugin by running the following command: --hostname=amzprometheus.int.centreon.com \ --url-path='/api/v1' --port='9090' --proto='http' \ --filter-label='job,coredns' \ - --warning-status='' --critical-status='%{health} !~ /up/' + --warning-status='' --critical-status='%\{health\} !~ /up/' ``` Expected command output is shown below: @@ -198,9 +198,9 @@ Nothing is better than a clear example to understand how the Expression generic --hostname=amzprometheus.int.centreon.com \ --url-path='/api/v1' --port='9090' --proto='http' \ --query='cpu_requests,sum by (node) (kube_pod_container_resource_requests_cpu_cores) / sum by (node) (kube_node_status_capacity_cpu_cores) * 100' \ - --output='%{instance} CPU Requests: %{cpu_requests}%' --multiple-output='Nodes CPU Requests within bounds' \ + --output='%\{instance\} CPU Requests: %\{cpu_requests\}%' --multiple-output='Nodes CPU Requests within bounds' \ --instance='node' \ - --warning-status='%{cpu_requests} > 60' --critical-status='%{cpu_requests} > 70' \ + --warning-status='%\{cpu_requests\} > 60' --critical-status='%\{cpu_requests\} > 70' \ --use-new-perfdata --verbose ``` @@ -228,8 +228,8 @@ check in the following cases: - Check returning an error Values can be specified through the corresponding macros, in this example the value of OUTPUT macro -would be "%{instance} CPU Requests: %{cpu_requests}%". Note that we use the Centreon label defined in the `--query` -option to use the obtained value). We also use the '%{instance}' keyword to display the node name. +would be "%\{instance\} CPU Requests: %\{cpu_requests\}%". Note that we use the Centreon label defined in the `--query` +option to use the obtained value). We also use the '%\{instance\}' keyword to display the node name. The MULTIPLEOUTPUT value would be "Nodes CPU Requests within bounds" @@ -243,7 +243,7 @@ In the command above, the check triggers a *WARNING* alarm when the 'cpu_request Note that the Centreon label defined in the `--query` options is used again to compare the obtained value with thresholds. -The macros value would be '%{cpu_requests} > 60' for WARNINGSTATUS and '%{cpu_requests} > 70' +The macros value would be '%\{cpu_requests\} > 60' for WARNINGSTATUS and '%\{cpu_requests\} > 70' for CRITICALSTATUS. #### Expected output and macros summary @@ -265,18 +265,18 @@ Here is a summary of the Service's macros definitions: | INSTANCE | node | | OUTPUT | URL Path to reach API (Default: '/api/v1) | | MULTIPLEOUTPUT | Nodes CPU Requests within bounds | -| WARNINGSTATUS | %{cpu_requests} > 60 | -| CRITICALSTATUS | %{cpu_requests} > 70 | +| WARNINGSTATUS | %\{cpu_requests\} > 60 | +| CRITICALSTATUS | %\{cpu_requests\} > 70 | | EXTRAOPTIONS | --verbose --use-new-perfdata | ## Troubleshooting -### UNKNOWN: 500 Can't connect to amzprometheus.int.centreon.com:9090 () | When facing this error message, check that port, hostname are OK and double check the connection between your Centreon Poller and the Prometheus Server. -The should give more information about the root cause +The \ should give more information about the root cause ### UNKNOWN: 400 Bad Request | diff --git a/pp/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md b/pp/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md index db97e934900e..7b3d3d399095 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md +++ b/pp/integrations/plugin-packs/procedures/cloud-prometheus-kubernetes-api.md @@ -208,8 +208,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | POD | Filter on a specific pod (must be a PromQL filter, Default:'pod=~".*"') | pod=~".*" | | | WARNINGRESTARTSCOUNT | Warning threshold for container restarts count | | | | CRITICALRESTARTSCOUNT | Critical threshold for container restarts count | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/ \|\| %{state} !~ /ready/'). You can use the following variables: %{status}, %{state}, %{reason} | %{status} !~ /running/ \|\| %{state} !~ /ready/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{status}, %{state}, %{reason} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/ \|\| %\{state\} !~ /ready/'). You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | %\{status\} !~ /running/ \|\| %\{state\} !~ /ready/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -218,8 +218,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | DAEMONSET | Filter on a specific daemonset (must be a PromQL filter, Default: 'daemonset=~".*"') | daemonset=~".*" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{up_to_date\} \< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -228,8 +228,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | DEPLOYMENT | Filter on a specific deployment (must be a PromQL filter, Default: 'deployment=~".*"') | deployment=~".*" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{up\_to\_date} \< %{desired} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | %{available} \< %{desired} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{up_to_date\} \< %\{desired\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | %\{available\} \< %\{desired\} | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -239,8 +239,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | NAMESPACE | Filter on a specific namespace (must be a PromQL filter, Default: 'namespace=~".*"') | namespace=~".*" | | | PHASE | Filter on a specific phase (must be a PromQL filter, Default:'phase=~".*"') | phase=~".*" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Active/'). You can use the following variables: %{display}, %{phase} | %{phase} !~ /Active/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{phase} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Active/'). You can use the following variables: %\{display\}, %\{phase\} | %\{phase\} !~ /Active/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{phase\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -252,8 +252,8 @@ yum install centreon-plugin-Cloud-Prometheus-Kubernetes-Api | UNITS | Units of thresholds (default: '') (can be '%') | | | | WARNINGALLOCATEDPODS | Warning threshold for pods allocation | | | | CRITICALALLOCATEDPODS | Critical threshold for pods allocation | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Ready/ \|\| %{schedulable} != /false/'). You can use the following variables: %{display}, %{status}, %{schedulable} | %{status} !~ /Ready/ \|\| %{schedulable} =~ /false/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{status}, %{schedulable} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Ready/ \|\| %\{schedulable\} != /false/'). You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | %\{status\} !~ /Ready/ \|\| %\{schedulable\} =~ /false/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -277,7 +277,7 @@ is able to monitor a resource using a command like this one (replace the sample --proto='http' \ --node='node=~".*"' \ --warning-status='' \ - --critical-status='%{status} !~ /Ready/ || %{schedulable} =~ /false/' \ + --critical-status='%\{status\} !~ /Ready/ || %\{schedulable\} =~ /false/' \ --warning-allocated-pods='' \ --critical-allocated-pods='' \ --units='' \ @@ -347,7 +347,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -397,8 +397,8 @@ All available options for each service template are listed below: |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --container | Filter on a specific container (must be a PromQL filter, Default: 'container=~".*"') | | --pod | Filter on a specific pod (must be a PromQL filter, Default:'pod=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{status}, %{state}, %{reason} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/ \|\| %{state} !~ /ready/'). You can use the following variables: %{status}, %{state}, %{reason} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/ \|\| %\{state\} !~ /ready/'). You can use the following variables: %\{status\}, %\{state\}, %\{reason\} | | --warning-restarts-count | Warning threshold for container restarts count. | | --critical-restarts-count | Critical threshold for container restarts count. | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | @@ -411,8 +411,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --daemonset | Filter on a specific daemonset (must be a PromQL filter, Default: 'daemonset=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date}, %{ready}, %{misscheduled} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\}, %\{ready\}, %\{misscheduled\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - desired: ^kube\_daemonset\_status\_desired\_number\_scheduled$ - current: ^kube\_daemonset\_status\_current\_number\_scheduled$ - available: ^kube\_daemonset\_status\_number\_available$ - unavailable: ^kube\_daemonset\_status\_number\_unavailable$ - up\_to\_date: ^kube\_daemonset\_updated\_number\_scheduled$ - ready: ^kube\_daemonset\_status\_number\_ready$ - misscheduled: ^kube\_daemonset\_status\_number\_misscheduled$ | @@ -422,8 +422,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --deployment | Filter on a specific deployment (must be a PromQL filter, Default: 'deployment=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{up\_to\_date} \< %{desired}') You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{available} \< %{desired}'). You can use the following variables: %{display}, %{desired}, %{current}, %{available}, %{unavailable}, %{up\_to\_date} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{up_to_date\} \< %\{desired\}') You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{available\} \< %\{desired\}'). You can use the following variables: %\{display\}, %\{desired\}, %\{current\}, %\{available\}, %\{unavailable\}, %\{up_to_date\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - desired: ^kube\_deployment\_spec\_replicas$ - current: ^kube\_deployment\_status\_replicas$ - available: ^kube\_deployment\_status\_replicas\_available$ - unavailable: ^kube\_deployment\_status\_replicas\_unavailable$ - up\_to\_date: ^kube\_deployment\_status\_replicas\_updated$ | @@ -434,8 +434,8 @@ All available options for each service template are listed below: |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --namespace | Filter on a specific namespace (must be a PromQL filter, Default: 'namespace=~".*"') | | --phase | Filter on a specific phase (must be a PromQL filter, Default:'phase=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{phase}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{phase} !~ /Active/'). You can use the following variables: %{display}, %{phase} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{phase\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{phase\} !~ /Active/'). You can use the following variables: %\{display\}, %\{phase\} | | --extra-filter | Add a PromQL filter (can be defined multiple times) Example : --extra-filter='name=~".*pretty.*"' | | --metric-overload | Overload default metrics name (can be defined multiple times) Example : --metric-overload='metric,^my\_metric\_name$' Default : - status: ^kube\_namespace\_status\_phase$ | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | @@ -446,8 +446,8 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --node | Filter on a specific node (must be a PromQL filter, Default:'node=~".*"') | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{display}, %{status}, %{schedulable} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Ready/ \|\| %{schedulable} != /false/'). You can use the following variables: %{display}, %{status}, %{schedulable} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Ready/ \|\| %\{schedulable\} != /false/'). You can use the following variables: %\{display\}, %\{status\}, %\{schedulable\} | | --warning-allocated-pods | Warning threshold for pods allocation. | | --critical-allocated-pods | Critical threshold for pods allocation. | | --units | Units of thresholds (default: '') (can be '%'). | diff --git a/pp/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md b/pp/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md index 16796877d5e3..391d3719e22c 100644 --- a/pp/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md +++ b/pp/integrations/plugin-packs/procedures/cloud-vmware-velocloud-restapi.md @@ -326,9 +326,9 @@ yum install centreon-plugin-Cloud-Vmware-Velocloud-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{edge\_state} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | %{edge\_state} =~ /NEVER\_ACTIVATED/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | %{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{edge_state\} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | %\{edge_state\} =~ /NEVER\_ACTIVATED/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | %\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -337,11 +337,11 @@ yum install centreon-plugin-Cloud-Vmware-Velocloud-Restapi | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERLINKNAME | Filter links based on their name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{vpn\_state}, %{backup\_state} | | | -| WARNINGEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | -| CRITICALEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | -| CRITICALSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | %{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/ | | -| WARNINGSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/') | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{vpn_state\}, %\{backup_state\} | | | +| WARNINGEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | +| CRITICALEDGELINKSCOUNT | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | +| CRITICALSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | %\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/ | | +| WARNINGSTATUS | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -487,7 +487,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -573,9 +573,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter edge by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{edge\_state} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{edge\_state} !~ /CONNECTED/ && %{edge\_state} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %{edge\_state}, %{service\_state}, %{ha\_state}, %{activation\_state}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{edge_state\} =~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{edge_state\} !~ /CONNECTED/ && %\{edge_state\} !~ /NEVER\_ACTIVATED/'). You can use the following variables: %\{edge_state\}, %\{service_state\}, %\{ha_state\}, %\{activation_state\}. | @@ -584,8 +584,8 @@ All available options for each service template are listed below: |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-edge-name | Filter edge by name (can be a regexp). | | --filter-link-name | Filter link by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{vpn\_state}, %{backup\_state}. | -| --warning-* --critical-* | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %{state}, %{vpn\_state}, %{backup\_state} (Critical threshold default: '%{state} !~ /STABLE/ \|\| %{vpn\_state} !~ /STABLE/'). | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{vpn_state\}, %\{backup_state\}. | +| --warning-* --critical-* | Warning & Critical thresholds Can be 'status', 'edge-links-count'. For 'status', special variables can be used: %\{state\}, %\{vpn_state\}, %\{backup_state\} (Critical threshold default: '%\{state\} !~ /STABLE/ \|\| %\{vpn_state\} !~ /STABLE/'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ats-apc.md b/pp/integrations/plugin-packs/procedures/hardware-ats-apc.md index ee2f081d86cb..52a0273646aa 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ats-apc.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ats-apc.md @@ -216,8 +216,8 @@ yum install centreon-plugin-Hardware-Ats-Apc-Snmp | CRITICALLOADCAPACITY | Critical threshold | | | | WARNINGPOWER | Warning threshold | | | | CRITICALPOWER | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nearoverload/'). You can use the following variables: %{status}, %{display} | %{status} =~ /nearoverload/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(lowload\|overload)$/'). You can use the following variables: %{status}, %{display} | %{status} =~ /^(lowload\|overload)$/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nearoverload/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /nearoverload/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(lowload\|overload)$/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /^(lowload\|overload)$/ | | | WARNINGVOLTAGE | Warning threshold | | | | CRITICALVOLTAGE | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -303,7 +303,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -379,8 +379,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^power$' | | --warning-* | Warning threshold. Can be: 'voltage', 'current', 'power', 'load', 'load-capacity'. | | --critical-* | Critical threshold. Can be: 'voltage', 'current', 'power', 'load', 'load-capacity'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nearoverload/'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(lowload\|overload)$/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nearoverload/'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(lowload\|overload)$/'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md index 5868025d01c4..407e8d63e61c 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ats-eaton-snmp.md @@ -222,7 +222,7 @@ yum install centreon-plugin-Hardware-Ats-Eaton-Snmp | UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: operation\_mode | | | | WARNINGHUMIDITY | Warning threshold | | | | CRITICALHUMIDITY | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{operation\_mode} !~ /source1\|source2/i'). You can use the following variables: %{operation\_mode} | %{operation\_mode} !~ /source1\|source2/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{operation_mode\} !~ /source1\|source2/i'). You can use the following variables: %\{operation_mode\} | %\{operation_mode\} !~ /source1\|source2/i | | | WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: operation\_mode | | | | WARNINGTEMPERATURE | Warning threshold | | | | CRITICALTEMPERATURE | Critical threshold | | | @@ -304,7 +304,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -377,7 +377,7 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: operation\_mode | | --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: operation\_mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{operation\_mode} !~ /source1\|source2/i'). You can use the following variables: %{operation\_mode} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{operation_mode\} !~ /source1\|source2/i'). You can use the following variables: %\{operation_mode\} | | --warning-* | Warning threshold. Can be: 'temperature', 'humidity'. | | --critical-* | Critical threshold. Can be: 'temperature', 'humidity'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md index 4eeae9e325f9..16c4c3468d8b 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-device-gorgy-ntpserver-snmp.md @@ -211,10 +211,10 @@ yum install centreon-plugin-Hardware-Devices-Gorgy-Ntpserver-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------|:-----------:| -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{sync\_status} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %{sync\_status} | %{sync\_status} =~ /Running with autonomy\|Free running/i | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %{sync\_status} | %{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i | | -| WARNINGTIMEBASESTATUS | Define the conditions to match for the status to be WARNING (Default: '%{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %{timebase\_status} | %{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i | | -| CRITICALTIMEBASESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{timebase\_status} =~ /^XO$/i'). You can use the following variables: %{timebase\_status} | %{timebase\_status} =~ /^XO$/i | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{sync_status\} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %\{sync_status\} | %\{sync_status\} =~ /Running with autonomy\|Free running/i | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %\{sync_status\} | %\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i | | +| WARNINGTIMEBASESTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %\{timebase_status\} | %\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i | | +| CRITICALTIMEBASESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{timebase_status\} =~ /^XO$/i'). You can use the following variables: %\{timebase_status\} | %\{timebase_status\} =~ /^XO$/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -227,7 +227,7 @@ yum install centreon-plugin-Hardware-Devices-Gorgy-Ntpserver-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -312,7 +312,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -379,10 +379,10 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^sync-status$' | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (Default: '%{sync\_status} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %{sync\_status} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (Default: '%{sync\_status} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %{sync\_status} | -| --warning-timebase-status | Define the conditions to match for the status to be WARNING (Default: '%{timebase\_status} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %{timebase\_status} | -| --critical-timebase-status | Define the conditions to match for the status to be CRITICAL (Default: '%{timebase\_status} =~ /^XO$/i'). You can use the following variables: %{timebase\_status} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (Default: '%\{sync_status\} =~ /Running with autonomy\|Free running/i'). You can use the following variables: %\{sync_status\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{sync_status\} =~ /Server locked\|Never synchronized\|Server not synchronized/i'). You can use the following variables: %\{sync_status\} | +| --warning-timebase-status | Define the conditions to match for the status to be WARNING (Default: '%\{timebase_status\} =~ /^(?!(XO\|XO OK\|TCXO Precision \< 2usec\|OCXO Precision \< 1usec)$)/i'). You can use the following variables: %\{timebase_status\} | +| --critical-timebase-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{timebase_status\} =~ /^XO$/i'). You can use the following variables: %\{timebase_status\} | | --warning-* | Warning threshold. Can be: 'ntp-requests'. | | --critical-* | Critical threshold. Can be: 'ntp-requests'. | @@ -399,9 +399,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md index eca38a4d7535..7509e408122e 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-abb-cms700-snmp.md @@ -357,7 +357,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md index 4e0f9cb8c896..d6c741f85b32 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-camera-avigilon-snmp.md @@ -270,8 +270,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -298,9 +298,9 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match to return a unknown status. The condition can be written using the following macros: %{storage\_state} | %{storage\_state} =~ /Unknown/i | | -| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{storage\_state} | %{storage_state} =~ /insufficientMediaCapacity/i \| \ | %{storage_state} =~ /insufficientMediaSpeed/i | | -| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %{storage\_state} | %{storage_state} =~ /mediaNotPresent/i \| \ | %{storage_state} =~ /error/i | | +| UNKNOWNSTATUS | Define the conditions to match to return a unknown status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /Unknown/i | | +| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /insufficientMediaCapacity/i \| \ | %\{storage_state\} =~ /insufficientMediaSpeed/i | | +| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %\{storage_state\} | %\{storage_state\} =~ /mediaNotPresent/i \| \ | %\{storage_state\} =~ /error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -308,8 +308,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Avigilon-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %{status} | %{status} ne "ok" | | -| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{status} | | | +| CRITICALSTATUS | Define the conditions to match to return a critical status. The condition can be written using the following macros: %\{status\} | %\{status\} ne "ok" | | +| WARNINGSTATUS | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{status\} | | | | WARNINGTEMPERATURE | Warning threshold for temperature (Celsius). | | | | CRITICALTEMPERATURE | Critical threshold for temperature (Celsius). | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | | | @@ -398,7 +398,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -472,9 +472,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -508,17 +508,17 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match to return a unknown status (default: "%{storage\_state} =~ /Unknown/i"). The condition can be written using the following macros: %{storage\_state}. | -| --warning-status | Define the conditions to match to return a warning status (default: "%{storage\_state} =~ /insufficientMediaCapacity/i \|\| %{storage\_state} =~ /insufficientMediaSpeed/i"). The condition can be written using the following macros: %{storage\_state}. | -| --critical-status | Define the conditions to match to return a critical status (default: "%{storage\_state} =~ /mediaNotPresent/i \|\| %{storage\_state} =~ /error/i"). The condition can be written using the following macros: %{storage\_state}. | +| --unknown-status | Define the conditions to match to return a unknown status (default: "%\{storage_state\} =~ /Unknown/i"). The condition can be written using the following macros: %\{storage_state\}. | +| --warning-status | Define the conditions to match to return a warning status (default: "%\{storage_state\} =~ /insufficientMediaCapacity/i \|\| %\{storage_state\} =~ /insufficientMediaSpeed/i"). The condition can be written using the following macros: %\{storage_state\}. | +| --critical-status | Define the conditions to match to return a critical status (default: "%\{storage_state\} =~ /mediaNotPresent/i \|\| %\{storage_state\} =~ /error/i"). The condition can be written using the following macros: %\{storage_state\}. | | Option | Description | |:------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match to return a warning status. The condition can be written using the following macros: %{status}. | -| --critical-status | Define the conditions to match to return a critical status (default: '%{status} ne "ok"'). The condition can be written using the following macros: %{status}. | +| --warning-status | Define the conditions to match to return a warning status. The condition can be written using the following macros: %\{status\}. | +| --critical-status | Define the conditions to match to return a critical status (default: '%\{status\} ne "ok"'). The condition can be written using the following macros: %\{status\}. | | --warning-temperature* | Warning threshold for temperature (Celsius). | | --critical-temperature* | Critical threshold for temperature (Celsius). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md index b0797d1389ca..35ecff3e7bb3 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-camera-optelecom-snmp.md @@ -238,8 +238,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | %{alarm} eq "enabled" | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | %\{alarm\} eq "enabled" | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -280,8 +280,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -312,8 +312,8 @@ yum install centreon-plugin-Hardware-Devices-Camera-Optelecom-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | %{alarm} eq "enabled" | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | %\{alarm\} eq "enabled" | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | | | | WARNINGPROBETEMPERATURE | Thresholds | | | | CRITICALPROBETEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -406,7 +406,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -461,9 +461,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm} eq "enabled"'). You can use the following variables: %{alarm}, %{alarmName}, %{deviceName} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm\} eq "enabled"'). You can use the following variables: %\{alarm\}, %\{alarmName\}, %\{deviceName\} | @@ -490,9 +490,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -527,9 +527,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm} eq "enabled"'). You can use the following variables: %{alarm}, %{probeIndex}, %{deviceName} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm\} eq "enabled"'). You can use the following variables: %\{alarm\}, %\{probeIndex\}, %\{deviceName\} | | --warning-* --critical-* | Thresholds. Can be: 'probe-temperature'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md index 53d30e955048..59860a9f339d 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-hms-netbiter-argos-restapi.md @@ -313,10 +313,10 @@ All modes specific options are listed here: | --filter-acked | Hide acknowledged alarms. | Mode | | --filter-active | Only show active alarms. | Mode | | --filter-severity | Only show alarms with a given severity level. Can be: 'critical', 'major', 'minor', 'warning', 'cleared'. Only one value can be set (no multiple values). | Mode | -| --warning-active-status | Set warning threshold for active status (Default: ''). Typical syntax: --warning-active-status='%{active} =~ "true"' | Mode | -| --critical-active-status | Set critical threshold for active status (Default: '%{active} =~ "true"'). Typical syntax: --critical-active-status='%{active} =~ "true"' | Mode | -| --warning-acked-status | Set warning threshold for acked status (Default: '%{acked} =~ "false"'). Typical syntax: --warning-acked-status='%{acked} =~ "false"' | Mode | -| --critical-acked-status | Set critical threshold for acked status (Default: ''). Typical syntax: --critical-acked-status='%{acked} =~ "false"' | Mode | +| --warning-active-status | Set warning threshold for active status (Default: ''). Typical syntax: --warning-active-status='%\{active\} =~ "true"' | Mode | +| --critical-active-status | Set critical threshold for active status (Default: '%\{active\} =~ "true"'). Typical syntax: --critical-active-status='%\{active\} =~ "true"' | Mode | +| --warning-acked-status | Set warning threshold for acked status (Default: '%\{acked\} =~ "false"'). Typical syntax: --warning-acked-status='%\{acked\} =~ "false"' | Mode | +| --critical-acked-status | Set critical threshold for acked status (Default: ''). Typical syntax: --critical-acked-status='%\{acked\} =~ "false"' | Mode | | --warning-* --critical-* | Thresholds. Can be: 'warning-alarms-total' (count) 'critical-alarms-total' (count), 'warning-alarm-duration' (s), 'critical-alarm-duration' (s), 'warning-alarm-severity' (level from 0 to 5), critical-alarm-severity (level from 0 to 5). | Mode | diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md b/pp/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md index ddef39eac58e..72d0d6ec5d93 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-pexip-infinity-managementapi.md @@ -117,8 +117,8 @@ Once the Plugin installed, log into your poller using the *centreon-engine* user --api-username='myapiusername' \ --api-password='myapipassword' \ --filter-name='mycall1.centreon.com' \ - --warning-status='%{level} =~ /warning|minor/i' \ - --critical-status='%{level} =~ /critical|major|error/i' \ + --warning-status='%\{level\} =~ /warning|minor/i' \ + --critical-status='%\{level\} =~ /critical|major|error/i' \ --verbose ``` diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md index 3734234638c3..e23dbc4ada69 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-polycom-dma-snmp.md @@ -153,7 +153,7 @@ through **Configuration > Monitoring Connector Manager** page. * Add a new Host and apply the *HW-Device-Polycom-Dma-SNMP-Custom* Host Template * Fill SNMP Version and Community fields according to the device's configuration -> When using SNMP v3, use the SNMPEXTRAOPTIONS Macro to add specific authentication parameters +> When using SNMP v3, use the SNMPEXTRAOPTIONS Macro to add specific authentication parameters > More information in the [Troubleshooting SNMP](../getting-started/how-to-guides/troubleshooting-plugins.md#snmpv3-options-mapping) section. | Mandatory | Name | Description | @@ -174,8 +174,8 @@ and test the Plugin by running the following command: --hostname=10.0.0.1 \ --snmp-version='2c' --snmp-community='mysnmpcommunity' \ - --critical-cluster-status='%{cluster_status} =~ /outOfService/i' \ - --critical-license-status='%{license_status} =~ /notinstalled/i' \ + --critical-cluster-status='%\{cluster_status\} =~ /outOfService/i' \ + --critical-license-status='%\{license_status\} =~ /notinstalled/i' \ --warning-cluster-license-usage-prct='80' \ --critical-cluster-license-usage-prct='90' \ --verbose diff --git a/pp/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md index 420bbaa04edc..b6445852c760 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-devices-video-appeartv-snmp.md @@ -187,9 +187,9 @@ yum install centreon-plugin-Hardware-Devices-Video-Appeartv-Snmp | Macro | Description | Default value | Mandatory | |:--------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| -| CRITICSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/ | | +| CRITICSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/ | | | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor\|warning/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor\|warning/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -211,8 +211,8 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --filter-msg='' \ - --warning-status='%{severity} =~ /minor|warning/i' \ - --critical-status='%{severity} =~ /critical|major/' + --warning-status='%\{severity\} =~ /minor|warning/i' \ + --critical-status='%\{severity\} =~ /critical|major/' ``` The expected command output is shown below: @@ -274,8 +274,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | | --mode | Define the mode in which you want the plugin to be executed (see --list-mode). | | --dyn-mode | Specify a mode with the module's path (advanced). | @@ -311,7 +311,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md index f905bcacb67b..0463b87d8ae2 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-kvm-avocent-acs-8000-snmp.md @@ -282,9 +282,9 @@ yum install centreon-plugin-Hardware-Kvm-Avocent-Acs-8000-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter by serial port name (can be a regexp). | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICOUT | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -371,7 +371,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -489,9 +489,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-name | Filter by serial port name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md index 5cfb71bbcd7a..a39443387c08 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-apc-snmp.md @@ -295,7 +295,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -362,12 +362,12 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-bank-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | -| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low\|nearOverload/i'). You can use the following variables: %{type}, %{status}, %{display} | -| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^overload/'). You can use the following variables: %{type}, %{status}, %{display} | -| --unknown-phase-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low\|nearOverload/i'). You can use the following variables: %{status}, %{display} | -| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^overload/i'). You can use the following variables: %{status}, %{display} | +| --unknown-bank-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low\|nearOverload/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^overload/'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --unknown-phase-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low\|nearOverload/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^overload/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current', 'power'. | @@ -375,9 +375,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{phase}, %{bank}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /off/'). You can use the following variables: %{status}, %{phase}, %{bank}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{phase\}, %\{bank\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /off/'). You can use the following variables: %\{status\}, %\{phase\}, %\{bank\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md index 165339ef0f56..238d0acdff95 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-clever-snmp.md @@ -269,7 +269,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md index b3cef90b8ef3..8e075de77c07 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-cyberpower-snmp.md @@ -196,14 +196,14 @@ yum install centreon-plugin-Hardware-Pdu-Cyberpower-Snmp |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------|:-----------:| | WARNINGBANKCURRENT | Thresholds | | | | CRITICALBANKCURRENT | Thresholds | | | -| WARNINGBANKSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /low\|nearOverload/i | | -| CRITICALBANKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/'). You can use the following variables: %{state}, %{display} | %{state} =~ /^overload/i | | +| WARNINGBANKSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /low\|nearOverload/i | | +| CRITICALBANKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /^overload/i | | | WARNINGPHASECURRENT | Thresholds | | | | CRITICALPHASECURRENT | Thresholds | | | | WARNINGPHASEPOWER | Thresholds | | | | CRITICALPHASEPOWER | Thresholds | | | -| WARNINGPHASESTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /low\|nearOverload/i | | -| CRITICALPHASESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /^overload/i | | +| WARNINGPHASESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /low\|nearOverload/i | | +| CRITICALPHASESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /^overload/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -213,8 +213,8 @@ yum install centreon-plugin-Hardware-Pdu-Cyberpower-Snmp |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /off/'). You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | %{state} =~ /off/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /off/'). You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | %\{state\} =~ /off/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -236,7 +236,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{state} =~ /off/i' \ + --critical-status='%\{state\} =~ /off/i' \ --warning-current='' \ --critical-current='' \ --verbose @@ -293,7 +293,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -347,12 +347,12 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-bank-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | -| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/'). You can use the following variables: %{state}, %{display} | -| --unknown-phase-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /low\|nearOverload/i'). You can use the following variables: %{state}, %{display} | -| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /^overload/i'). You can use the following variables: %{state}, %{display} | +| --unknown-bank-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-bank-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | +| --critical-bank-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/'). You can use the following variables: %\{state\}, %\{display\} | +| --unknown-phase-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-phase-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /low\|nearOverload/i'). You can use the following variables: %\{state\}, %\{display\} | +| --critical-phase-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /^overload/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'phase-current', 'phase-power', 'phase-voltage', 'bank-current'. | @@ -360,9 +360,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%{state}, %{phase}, %{bank}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /off/'). You can use the following variables: %{state}, %{phase}, %{bank}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %%\{state\}, %\{phase\}, %\{bank\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /off/'). You can use the following variables: %\{state\}, %\{phase\}, %\{bank\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md index 072f0a904c63..c1c683763860 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-eaton-snmp.md @@ -200,16 +200,16 @@ yum install centreon-plugin-Hardware-Pdu-Eaton-Snmp | Macro | Description | Default value | Mandatory | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| UNKNOWNHUMIDITYSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | -| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNHUMIDITYSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGHUMIDITY | Thresholds | | | | CRITICALHUMIDITY | Thresholds | | | -| CRITICALHUMIDITYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | %{status} eq "bad" | | -| WARNINGHUMIDITYSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALHUMIDITYSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "bad" | | +| WARNINGHUMIDITYSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | -| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | %{status} eq "bad" | | -| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "bad" | | +| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -317,7 +317,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -371,12 +371,12 @@ All available options for each service template are listed below: | Option | Description | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | -| --unknown-humidity-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-humidity-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-humidity-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'). You can use the following variables: %{status}, %{display} | +| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-humidity-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-humidity-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-humidity-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'humidity' (%), 'temperature' (C). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md index 90249c1386b7..229a5c25d86a 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-emerson-snmp.md @@ -209,8 +209,8 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| | FILTERNAME | Filter PDU name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /normalWithAlarm\|abnormalOperation/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /normalWithWarning/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /normalWithWarning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /normalWithAlarm\|abnormalOperation/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /normalWithWarning/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /normalWithWarning/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -237,7 +237,7 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | Macro | Description | Default value | Mandatory | |:----------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | FILTERNAME | Filter by name (can be a regexp) | | | -| UNKNOWNRCPSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | | | +| UNKNOWNRCPSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | | | | WARNINGCURRENTNEUTRAL | Thresholds | | | | CRITICALCURRENTNEUTRAL | Thresholds | | | | WARNINGLINE2NEUTRALAPPARENTPOWER | Thresholds | | | @@ -246,8 +246,8 @@ yum install centreon-plugin-Hardware-Pdu-Emerson-Snmp | CRITICALLINE2NEUTRALREALPOWER | Thresholds | | | | WARNINGPOTENTIALNEUTRAL | Thresholds | | | | CRITICALPOTENTIALNEUTRAL | Thresholds | | | -| WARNINGRCPSTATUS | Define the conditions to match for the status to be WARNING (default: '%{oper\_state} =~ /warning\|alarm/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | %{oper\_state} =~ /warning\|alarm/ | | -| CRITICALRCPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_state} =~ /abnormal/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | %{oper\_state} =~ /abnormal/ | | +| WARNINGRCPSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{oper_state\} =~ /warning\|alarm/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | %\{oper_state\} =~ /warning\|alarm/ | | +| CRITICALRCPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_state\} =~ /abnormal/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | %\{oper_state\} =~ /abnormal/ | | | WARNINGTOTALACCUMULATEDENERGY | Thresholds | | | | CRITICALTOTALACCUMULATEDENERGY | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -336,7 +336,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -391,8 +391,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter PDU name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /normalWithWarning/i'). You can use the following variables: %{status}, %{display}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /normalWithWarning/i'). You can use the following variables: %\{status\}, %\{display\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /normalWithAlarm\|abnormalOperation/i'). You can use the following variables: %\{status\}, %\{display\} | @@ -434,9 +434,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-rb | Filter receptable branch name (can be a regexp). | -| --unknown-rcp-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | -| --warning-rcp-status | Define the conditions to match for the status to be WARNING (default: '%{oper\_state} =~ /warning\|alarm/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | -| --critical-rcp-status | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_state} =~ /abnormal/'). You can use the following variables: %{oper\_state}, %{power\_state}, %{display} | +| --unknown-rcp-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | +| --warning-rcp-status | Define the conditions to match for the status to be WARNING (default: '%\{oper_state\} =~ /warning\|alarm/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | +| --critical-rcp-status | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_state\} =~ /abnormal/'). You can use the following variables: %\{oper_state\}, %\{power_state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-accumulated-energy', 'line2neutral-real-power', 'line2neutral-apparent-power'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md index 12b1abdd080c..6af1228907dc 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-gude-epc-snmp.md @@ -226,7 +226,7 @@ yum install centreon-plugin-Hardware-Pdu-Gude-Epc-Snmp | CRITICALENERGY | Critical threshold | | | | WARNINGFREQUENCY | Warning threshold | | | | CRITICALFREQUENCY | Critical threshold | | | -| CRITICALOVPSTATUS | Critical threshold for OVP (OverVoltage Protection) status (default: '%{ovp\_status} !~ /ok/i') | %{ovp\_status} !~ /ok/i | | +| CRITICALOVPSTATUS | Critical threshold for OVP (OverVoltage Protection) status (default: '%\{ovp_status\} !~ /ok/i') | %\{ovp_status\} !~ /ok/i | | | WARNINGOVPSTATUS | Warning threshold for OVP (OverVoltage Protection) status | | | | WARNINGPHASEANGLE | Warning threshold | | | | CRITICALPHASEANGLE | Critical threshold | | | @@ -238,9 +238,9 @@ yum install centreon-plugin-Hardware-Pdu-Gude-Epc-Snmp | CRITICALPOWERFACTOR | Critical threshold | | | | WARNINGPOWERREACTIVE | Warning threshold | | | | CRITICALPOWERREACTIVE | Critical threshold | | | -| CRITICALPSSTATUS | Critical threshold for power supply status (default: '%{ps\_status} !~ /up/i') | %{ps\_status} !~ /up/i | | +| CRITICALPSSTATUS | Critical threshold for power supply status (default: '%\{ps_status\} !~ /up/i') | %\{ps_status\} !~ /up/i | | | WARNINGPSSTATUS | Warning threshold for power supply status | | | -| CRITICALSTATUS | Critical threshold for channel status (default: '%{status} !~ /valid/i') | %{status} !~ /valid/i | | +| CRITICALSTATUS | Critical threshold for channel status (default: '%\{status\} !~ /valid/i') | %\{status\} !~ /valid/i | | | WARNINGSTATUS | Warning threshold for channel status | | | | WARNINGVOLTAGE | Warning threshold | | | | CRITICALVOLTAGE | Critical threshold | | | @@ -376,7 +376,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -432,11 +432,11 @@ All available options for each service template are listed below: |:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter power channel interfaces by name (can be a regexp). | | --warning-status | Warning threshold for channel status. | -| --critical-status | Critical threshold for channel status (default: '%{status} !~ /valid/i') | +| --critical-status | Critical threshold for channel status (default: '%\{status\} !~ /valid/i') | | --warning-ovp-status | Warning threshold for OVP (OverVoltage Protection) status. | -| --critical-ovp-status | Critical threshold for OVP (OverVoltage Protection) status (default: '%{ovp\_status} !~ /ok/i') | +| --critical-ovp-status | Critical threshold for OVP (OverVoltage Protection) status (default: '%\{ovp_status\} !~ /ok/i') | | --warning-ps-status | Warning threshold for power supply status. | -| --critical-ps-status | Critical threshold for power supply status (default: '%{ps\_status} !~ /up/i') | +| --critical-ps-status | Critical threshold for power supply status (default: '%\{ps_status\} !~ /up/i') | | --warning-* | Warning threshold. Can be: 'active-channels', 'current', 'energy', 'frequency', 'phase-angle', 'power-active', 'power-apparent', 'power-factor', 'power-reactive', 'voltage' | | --critical-* | Can be: 'active-channels', 'current', 'energy', 'frequency', 'phase-angle', 'power-active', 'power-apparent', 'power-factor', 'power-reactive', 'voltage' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md index 022d003aea9a..2d310685f56b 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-raritan-snmp.md @@ -314,7 +314,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md index 6154469211c9..8d6b8a7e3d87 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-pdu-schleifenbauer-gateway-snmp.md @@ -261,7 +261,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md index 215de28ed212..adb5d9f2f47f 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-printers-standard-rfc3805-snmp.md @@ -265,10 +265,10 @@ yum install centreon-plugin-Hardware-Printers-Generic-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| OKSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /ok/'). You can use the following variables: %{status} | %{status} =~ /ok/ | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /.*/'). You can use the following variables: %{status} | %{status} =~ /.*/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| OKSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /ok/'). You can use the following variables: %\{status\} | %\{status\} =~ /ok/ | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /.*/'). You can use the following variables: %\{status\} | %\{status\} =~ /.*/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -296,9 +296,9 @@ is able to monitor a resource using a command like this one (replace the sample --hostname=10.0.0.1 \ --snmp-community='my-snmp-community' \ --snmp-version='2c' \ - --ok-status='%{status} =~ /ok/' \ + --ok-status='%\{status\} =~ /ok/' \ --unknown-status='' \ - --warning-status='%{status} =~ /.*/' \ + --warning-status='%\{status\} =~ /.*/' \ --critical-status='' \ --verbose ``` @@ -358,7 +358,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -412,9 +412,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%%{status} =~ /other\|unknown/'). You can use the following variables: %{status}, %{description} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%%{status} =~ /coverOpen\|interlockOpen/'). You can use the following variables: %{status}, %{description} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{description} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%%\{status\} =~ /other\|unknown/'). You can use the following variables: %\{status\}, %\{description\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%%\{status\} =~ /coverOpen\|interlockOpen/'). You can use the following variables: %\{status\}, %\{description\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{description\} | @@ -460,10 +460,10 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| | --big-endian | Use that option if your printer provides big-endian bits ordering. | -| --ok-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /ok/'). You can use the following variables: %{status} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /.*/'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --ok-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /ok/'). You can use the following variables: %\{status\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /.*/'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md index c1ef538895a0..1e4e3fd74d97 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-akcp-snmp.md @@ -262,7 +262,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md index c6a3512b8394..433f3e4cfd6e 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-apc-snmp.md @@ -273,7 +273,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md index 1b5eccdabe29..8c837125bc08 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-comet-p8000-snmp.md @@ -264,7 +264,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md index 1699956d03b4..fee4091aa07c 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-geist-snmp.md @@ -297,7 +297,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md index 5c272c5a9cf4..a77f7ab4e271 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-hwgste-snmp.md @@ -263,7 +263,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md index b1d32d61fda0..2e1c09980d9b 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-jacarta-snmp.md @@ -46,7 +46,7 @@ Here is the list of services for this connector, detailing all metrics linked to | Metric name | Unit | |:---------------|:------| -| hardware.sensor.temperature. | C or F | +| hardware.sensor.temperature.\ | C or F | | hardware.sensor.humidity.percentage | % | | input.status | N/A | @@ -259,7 +259,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md index 88f9661eb184..790b200f55e2 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-netbotz-snmp.md @@ -262,7 +262,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md index e30826fae504..8f4244e53f14 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-rittal-cmc3-snmp.md @@ -217,8 +217,8 @@ yum install centreon-plugin-Hardware-Sensors-Rittal-Cmc-Snmp | FILTERINDEX | | | | | FILTERNAME | Filter device name (can be a regexp) | | | | FILTERALIAS | Filter devices alias (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %{status} | %{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /notAvail\|lost\|error/i'). You can use the following variables: %{status} | %{status} =~ /notAvail\|lost\|error/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %\{status\} | %\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /notAvail\|lost\|error/i'). You can use the following variables: %\{status\} | %\{status\} =~ /notAvail\|lost\|error/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -239,9 +239,9 @@ yum install centreon-plugin-Hardware-Sensors-Rittal-Cmc-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------|:------------| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{overall\_device\_status} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{overall\_device\_status} =~ /detected\|lost\|changed\|update/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{unit\_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{unit\_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | %{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{overall_device_status\} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{overall_device_status\} =~ /detected\|lost\|changed\|update/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\} =~ /warning/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\} =~ /alarm/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | %\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\} =~ /alarm/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -336,7 +336,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -393,9 +393,9 @@ All modes specific options are listed here: | --filter-name | Filter device name (can be a regexp). | Mode | | --filter-alias | Filter devices alias (can be a regexp). | Mode | | --index | Filter device index (exact match). | Mode | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %{status} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /notAvail\|lost\|error/i'). You can use the following variables: %{status} | Mode | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /detect\|changed\|fwUpdate\|fwUpdateRun/i'). You can use the following variables: %\{status\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /notAvail\|lost\|error/i'). You can use the following variables: %\{status\} | Mode | @@ -409,9 +409,9 @@ All modes specific options are listed here: | Option | Description | Type | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{overall\_device\_status} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{unit\_status} =~ /overload/i \|\| %{overall\_device\_status} =~ /warning/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{unit\_status} =~ /failed/i \|\| %{overall\_device\_status} =~ /alarm/i'). You can use the following variables: %{unit\_status}, %{overall\_device\_status}, %{mode}, %{available\_devices} | Mode | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{overall_device_status\} =~ /detected\|lost\|changed\|update/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{unit_status\} =~ /overload/i \|\| %\{overall_device_status\} =~ /warning/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{unit_status\} =~ /failed/i \|\| %\{overall_device_status\} =~ /alarm/i'). You can use the following variables: %\{unit_status\}, %\{overall_device_status\}, %\{mode\}, %\{available_devices\} | Mode | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md index 9ae6b273cf22..972e3c89fd2c 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-sensorip-snmp.md @@ -329,7 +329,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md index 498f6547166d..96473f09140d 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-sensormetrix-em01-web.md @@ -352,7 +352,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md index 4808db111a04..fab0953d0a9a 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-sensors-serverscheck-sensorgateway-snmp.md @@ -255,7 +255,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md index 9485872be6a2..8a821a5348c1 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-servers-cisco-ucs-snmp.md @@ -244,8 +244,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALAUDITMINOR | Critical threshold | | | | WARNINGAUDITTOTAL | Warning threshold | | | | CRITICALAUDITTOTAL | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -277,8 +277,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALFAULTSMINOR | Critical threshold | | | | WARNINGFAULTSTOTAL | Warning threshold | | | | CRITICALFAULTSTOTAL | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -286,9 +286,9 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown"') You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | %{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down"'). You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | %{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown"') You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | %\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down"'). You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | %\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -302,8 +302,8 @@ yum install centreon-plugin-Hardware-Servers-Cisco-Ucs-Snmp | CRITICALOFFLINE | Thresholds | | | | WARNINGONLINE | Thresholds | | | | CRITICALONLINE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "offline"'). You can use the following variables: %{dn}, %{status} | %{status} eq "offline" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "offline"'). You can use the following variables: %\{dn\}, %\{status\} | %\{status\} eq "offline" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -333,7 +333,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-offline='' \ --critical-offline='' \ --warning-status='' \ - --critical-status='%{status} eq "offline"' \ + --critical-status='%\{status\} eq "offline"' \ --verbose ``` @@ -391,7 +391,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -457,8 +457,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | | --memory | Only check new audit. | | --filter-message | Filter on event message. (default: none) | | --retention | Event older (current time - retention time) is not checked (in seconds). | @@ -491,8 +491,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/') You can use the following variables: %{severity}, %{description}, %{dn} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{severity}, %{description}, %{dn} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/') You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{severity\}, %\{description\}, %\{dn\} | | --memory | Only check new fault. | | --filter-message | Filter on event message. (default: none) | | --retention | Event older (current time - retention time) is not checked (in seconds). | @@ -502,9 +502,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{role} =~ /unknown/ or %{status} eq "unknown" or %{services\_status} eq "unknown"') You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} =~ /electionFailed\|inapplicable/ or %{status} eq "down" or %{services\_status} eq "down"'). You can use the following variables: %{dn}, %{role}, %{services\_status}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{role\} =~ /unknown/ or %\{status\} eq "unknown" or %\{services_status\} eq "unknown"') You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} =~ /electionFailed\|inapplicable/ or %\{status\} eq "down" or %\{services_status\} eq "down"'). You can use the following variables: %\{dn\}, %\{role\}, %\{services_status\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -512,8 +512,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{dn}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "offline"'). You can use the following variables: %{dn}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{dn\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "offline"'). You can use the following variables: %\{dn\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'online', 'offline'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md index f6e77e50a295..9d42bc41c227 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-servers-dell-idrac-snmp.md @@ -272,7 +272,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -326,12 +326,12 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nonCritical\|other/'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical\|nonRecoverable/'). You can use the following variables: %{status} | -| --unknown-storage-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /unknown/'). You can use the following variables: %{status} | -| --warning-storage-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /nonCritical\|other/'). You can use the following variables: %{status} | -| --critical-storage-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical\|nonRecoverable/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nonCritical\|other/'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical\|nonRecoverable/'). You can use the following variables: %\{status\} | +| --unknown-storage-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\} | +| --warning-storage-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /nonCritical\|other/'). You can use the following variables: %\{status\} | +| --critical-storage-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical\|nonRecoverable/'). You can use the following variables: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md index 1d6a8c606578..3af1dde5ecc9 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-ilo-xmlapi.md @@ -240,7 +240,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md index 9d7ab121dd34..abe6f7ce4060 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-oneview-restapi.md @@ -186,9 +186,9 @@ yum install centreon-plugin-Hardware-Servers-Hp-Oneview-Restapi | Macro | Description | Default value | Mandatory | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter pool name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -200,7 +200,7 @@ yum install centreon-plugin-Hardware-Servers-Hp-Oneview-Restapi -3. [Deploy the configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). The service appears in the list of services, and on the **Resources Status** page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros. +1. [Deploy the configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). The service appears in the list of services, and on the **Resources Status** page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros. ## How to check in the CLI that the configuration is OK and what are the main options for? @@ -283,7 +283,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -350,9 +350,9 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter pool name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /warning/i'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /warning/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md index 51689236e08f..9785f2fe2f6e 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-servers-hp-snmp.md @@ -378,7 +378,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md index 754eecc14057..48aa2b47840b 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-adic-tape-snmp.md @@ -276,7 +276,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md index 670530d02978..a2f2f95ea594 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-avid-isis-snmp.md @@ -237,8 +237,8 @@ yum install centreon-plugin-Hardware-Storage-Avid-Isis-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{state} !~ /Online/i'). Can use special variables like: %{state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{state\} !~ /Online/i'). Can use special variables like: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -332,7 +332,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -408,8 +408,8 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{state} !~ /Online/i'). Can use special variables like: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{state\} !~ /Online/i'). Can use special variables like: %\{state\} | | --warning-redistributing-count | Warning threshold for number of workspaces redistributing. | | --critical-redistributing-count | Critical threshold for number of workspaces redistributing. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md index 9f5aca25aba2..08a4154bdb84 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-bdt-multistak-snmp.md @@ -262,7 +262,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md b/pp/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md index e97428f0218f..2b04ea4d8f85 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-datacore-api.md @@ -221,8 +221,8 @@ yum install centreon-plugin-Hardware-Storage-DataCore-Sansymphony-Restapi | Macro | Description | Default value | Mandatory | |:--------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------|:-----------:| | FILTERCAPTION | Define which element should be monitored based on the extended caption. This option will be treated as a regular expression. By default all elements will be checked | | | -| WARNINGSTATE | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | -| CRITICALSTATE | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | +| WARNINGSTATE | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | +| CRITICALSTATE | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -320,7 +320,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -384,7 +384,7 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-caption | Define which element should be monitored based on the extended caption. This option will be treated as a regular expression. By default all elements will be checked. | -| --warning-state --critical-state | define which output from the api should be considered warning or critical. warning\_default = '%{state} =~ /Warning/i', critical\_default = '%{state} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical. | +| --warning-state --critical-state | define which output from the api should be considered warning or critical. warning\_default = '%\{state\} =~ /Warning/i', critical\_default = '%\{state\} =~ /Critical/i', possible value for state : Undefined, Healthy, Attention, Warning, Critical. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md index 22500a738c27..6f4d4e2c2825 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-api.md @@ -84,7 +84,7 @@ Powershell and `DellStorage.ApiCommandSet.dll` have to be installed on Windows Server. You'll need to add the file `powershell.exe.config` in directory `C:WindowsSystem32WindowsPowerShellv1.0`: - + \ @@ -330,7 +330,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md index a09c438f171e..52171060a167 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-compellent-snmp.md @@ -262,7 +262,7 @@ yum install centreon-plugin-Hardware-Storage-Dell-Compellent-Snmp | WARNINGIN | Warning thresholds | 80 | | | CRITICALOUT | Critical thresholds | 90 | | | WARNINGOUT | Warning thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -352,7 +352,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -439,9 +439,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md index 020a06061253..14721382c650 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-dell-md3000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md b/pp/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md index 4fe15ad2e201..77f8ace61002 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-emc-clariion-navisphere.md @@ -390,7 +390,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md index ad90b84aaa41..d8c39c39eb58 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-emc-datadomain-snmp.md @@ -334,7 +334,7 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| -| TRULYALERT | Expression to define an actual alert (default: '%{severity} =~ /emergency\|alert\|warning\|critical/i') | %{severity} =~ /emergency\|alert\|warning\|critical/i | | +| TRULYALERT | Expression to define an actual alert (default: '%\{severity\} =~ /emergency\|alert\|warning\|critical/i') | %\{severity\} =~ /emergency\|alert\|warning\|critical/i | | | WARNINGALERTSCURRENT | Threshold | | | | CRITICALALERTSCURRENT | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -418,8 +418,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -428,8 +428,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Default value | Mandatory | |:----------------|:----------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERMTREENAME | Check MTress by name | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -437,14 +437,14 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Default value | Mandatory | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCIFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{cifsStatus} | | | -| CRITICALCIFSSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{cifsStatus} =~ /enabledNotRunning/'). You can use the following variables: %{cifsStatus} | | | -| WARNINGDDBOOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ddboostStatus} | | | -| CRITICALDDBOOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ddboostStatus} | | | -| WARNINGNFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{nfsStatus} | | | -| CRITICALNFSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{nfsStatus} | | | -| WARNINGVTLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | | | -| CRITICALVTLSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{vtlAdminState} =~ /failed/'). You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | | | +| WARNINGCIFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{cifsStatus\} | | | +| CRITICALCIFSSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{cifsStatus\} =~ /enabledNotRunning/'). You can use the following variables: %\{cifsStatus\} | | | +| WARNINGDDBOOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ddboostStatus\} | | | +| CRITICALDDBOOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ddboostStatus\} | | | +| WARNINGNFSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{nfsStatus\} | | | +| CRITICALNFSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{nfsStatus\} | | | +| WARNINGVTLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | | | +| CRITICALVTLSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{vtlAdminState\} =~ /failed/'). You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -453,8 +453,8 @@ yum install centreon-plugin-Hardware-Storage-Emc-Datadomain-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------|:-----------:| | CUSTOMINSTANCESNAME | Customize the name composition rule for the instances the metrics will be attached to (default: '%(type) %(source) %(destination)'). You can use the following variables: %(type) %(source) %(destination) | %(type) %(source) %(destination) | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /initializing\|recovering/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | %{state} =~ /disabledNeedsResync\|uninitialized/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | %{state} =~ /initializing\|recovering/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /initializing\|recovering/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | %\{state\} =~ /disabledNeedsResync\|uninitialized/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | %\{state\} =~ /initializing\|recovering/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -566,7 +566,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -601,7 +601,7 @@ All available options for each service template are listed below: |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --display-alerts | Display alerts in verbose output. | -| --truly-alert | Expression to define a truly alert (default: '%{severity} =~ /emergency\|alert\|warning\|critical/i'). | +| --truly-alert | Expression to define a truly alert (default: '%\{severity\} =~ /emergency\|alert\|warning\|critical/i'). | | --warning-* --critical-* | Thresholds. Can be: 'alerts-current'. | @@ -711,9 +711,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -754,9 +754,9 @@ All available options for each service template are listed below: |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-mtree-name | Check MTress by name. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'mtrees-detected', 'space-precompression-usage'. | @@ -765,18 +765,18 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --unknown-cifs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{cifsStatus} | -| --warning-cifs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{cifsStatus} | -| --critical-cifs-status | Define the conditions to match for the status to be CRITICAL (default: '%{cifsStatus} =~ /enabledNotRunning/'). You can use the following variables: %{cifsStatus} | -| --unknown-ddboost-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ddboostStatus} | -| --warning-ddboost-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ddboostStatus} | -| --critical-ddboost-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ddboostStatus} | -| --unknown-nfs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{nfsStatus} | -| --warning-nfs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{nfsStatus} | -| --critical-nfs-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{nfsStatus} | -| --unknown-vtl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | -| --warning-vtl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | -| --critical-vtl-status | Define the conditions to match for the status to be CRITICAL (default: '%{vtlAdminState} =~ /failed/'). You can use the following variables: %{vtlAdminState}, %{vtlProcessState} | +| --unknown-cifs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{cifsStatus\} | +| --warning-cifs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{cifsStatus\} | +| --critical-cifs-status | Define the conditions to match for the status to be CRITICAL (default: '%\{cifsStatus\} =~ /enabledNotRunning/'). You can use the following variables: %\{cifsStatus\} | +| --unknown-ddboost-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ddboostStatus\} | +| --warning-ddboost-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ddboostStatus\} | +| --critical-ddboost-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ddboostStatus\} | +| --unknown-nfs-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{nfsStatus\} | +| --warning-nfs-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{nfsStatus\} | +| --critical-nfs-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{nfsStatus\} | +| --unknown-vtl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | +| --warning-vtl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | +| --critical-vtl-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vtlAdminState\} =~ /failed/'). You can use the following variables: %\{vtlAdminState\}, %\{vtlProcessState\} | @@ -789,9 +789,9 @@ All available options for each service template are listed below: | --filter-repl-destination | Check replications by destination. | | --custom-perfdata-instances | Customize the name composition rule for the instances the metrics will be attached to (default: '%(type) %(source) %(destination)'). You can use the following variables: %(type) %(source) %(destination) | | --unit | Select the time unit for thresholds. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks (default: 'd'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /initializing\|recovering/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %{state}, %{status}, %{source}, %{destination}, %{type} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /initializing\|recovering/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /disabledNeedsResync\|uninitialized/i'). You can use the following variables: %\{state\}, %\{status\}, %\{source\}, %\{destination\}, %\{type\} | | --warning-* --critical-* | Thresholds. Can be: 'repl-detected', 'precompression-data-remaining', 'last-insync-time'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md b/pp/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md index 7d41038d77e4..07e2654af1ae 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-fujitsu-eternus-dx-ssh.md @@ -23,8 +23,8 @@ Generate key for centreon-engine user with command: # su - centreon-engine # ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa # ssh-keygen -e -f .ssh/identity.pub > identity.pub.ietf - # telnet - CLI> import ssh-public-key -server -port maintenance -user -filename identity.pub.ietf -account-name centreon + # telnet \ + CLI> import ssh-public-key -server \ -port maintenance -user \ -filename identity.pub.ietf -account-name centreon Password: importing ./identity.pub.ietf from ... CLI> exit @@ -32,7 +32,7 @@ Generate key for centreon-engine user with command: You can now try to connect you without password # su - centreon-engine - # ssh -l centreon + # ssh -l centreon \ ## Centreon Configuration diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md index 1dae89dff2b0..3ba6d37974a8 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-hnas-snmp.md @@ -242,10 +242,10 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:------------| -| UNKNOWNSTATUS | Set unknown threshold for status (Default: '%{state} =~ /unknown/'). You can use the following variables: %{state}, %{display} | %{state} =~ /unknown/ | | +| UNKNOWNSTATUS | Set unknown threshold for status (Default: '%\{state\} =~ /unknown/'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /unknown/ | | | FILTERNAME | Filter node name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{display} | %{state} =~ /offline/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: -). You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} =~ /offline/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: -). You can use the following variables: %\{state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -276,8 +276,8 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -310,8 +310,8 @@ yum install centreon-plugin-Hardware-Storage-Hitachi-Hnas-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:------------| | FILTERNAME | Filter volume name (can be a regexp) | | | -| CRITICALSTATUS | Set critical threshold for status (Default: -). You can use the following variables: %{status}, %{display} | %{status} =~ /needsChecking/i | | -| WARNINGSTATUS | Set warning threshold for status (Default: '%{status} =~ /needsChecking/i'). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: -). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /needsChecking/i | | +| WARNINGSTATUS | Set warning threshold for status (Default: '%\{status\} =~ /needsChecking/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -511,7 +511,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Change storage free perfdata in used: --change-perfdata=free,used,invert() Change storage free perfdata in used: --change-perfdata=used,free,invert() Scale traffic values automaticaly: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Extend perfdata from multiple perfdatas (methods in target are: min, max, average, sum) Syntax: --extend-perfdata-group=searchlabel,newlabel,target\[,\[newuom\],\[m in\],\[max\]\] Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -566,9 +566,9 @@ All modes specific options are listed here: | Option | Description | Type | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------|:-----| | --filter-name | Filter node name (can be a regexp). | Mode | -| --unknown-status | Set unknown threshold for status (Default: '%{state} =~ /unknown/'). You can use the following variables: %{state}, %{display} | Mode | -| --warning-status | Set warning threshold for status (Default: -). You can use the following variables: %{state}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{display} | Mode | +| --unknown-status | Set unknown threshold for status (Default: '%\{state\} =~ /unknown/'). You can use the following variables: %\{state\}, %\{display\} | Mode | +| --warning-status | Set warning threshold for status (Default: -). You can use the following variables: %\{state\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{display\} | Mode | @@ -607,9 +607,9 @@ All modes specific options are listed here: | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'counter'). | Mode | @@ -648,8 +648,8 @@ All modes specific options are listed here: |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:-----| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | Mode | | --filter-name | Filter volume name (can be a regexp). | Mode | -| --warning-status | Set warning threshold for status (Default: '%{status} =~ /needsChecking/i'). You can use the following variables: %{status}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: -). You can use the following variables: %{status}, %{display} | Mode | +| --warning-status | Set warning threshold for status (Default: '%\{status\} =~ /needsChecking/i'). You can use the following variables: %\{status\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: -). You can use the following variables: %\{status\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'usage'. | Mode | | --units | Units of thresholds (Default: '%') ('%', 'B'). | Mode | | --free | Thresholds are on free space left. | Mode | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md index 6e047211c8dd..445e84bf8277 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hitachi-standard-snmp.md @@ -303,7 +303,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md index ea919989a8fa..aea455f746d4 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-3par-ssh.md @@ -298,8 +298,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | CRITICALFLASHCACHEUSAGEPRCT | Define the CRITICAL threshold for the following component: 'flashcache-usage-prct' | | | | WARNINGFLASHCACHEVOLUMEREADHITS | Define the WARNING threshold for the following component: 'flashcache-volume-readhits' | | | | CRITICALFLASHCACHEVOLUMEREADHITS | Define the CRITICAL threshold for the following component: 'flashcache-volume-readhits' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id} | %{status} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\} | %\{status\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -308,30 +308,30 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | Macro | Description | Default value | Mandatory | |:----------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| | FILTERCAGEID | Filter cages by ID (can be a regexp) | | | -| CRITICALBOARDFIRMWARESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | %{status} !~ /Current/i | | -| WARNINGBOARDFIRMWARESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | | | -| CRITICALBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALBOARDFIRMWARESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | %\{status\} !~ /Current/i | | +| WARNINGBOARDFIRMWARESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | | +| CRITICALBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGBOARDPARTNERSTATUS | Define the conditions on partner to match for the status to be WARNING | | | -| CRITICALBOARDSELFSTATUS | Define the conditions on self to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALBOARDSELFSTATUS | Define the conditions on self to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGBOARDSELFSTATUS | Define the conditions on self to match for the status to be WARNING | | | -| CRITICALDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGDRIVEPORTASTATUS | Define the conditions on port A to match for the status to be WARNING | | | -| CRITICALDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGDRIVEPORTBSTATUS | Define the conditions on port B to match for the status to be WARNING | | | -| WARNINGDRIVESTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | | | -| CRITICALDRIVESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | | | +| WARNINGDRIVESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | | +| CRITICALDRIVESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | | | WARNINGDRIVETEMPERATURE | Define WARNING threshold for the temperature of the drives | | | | CRITICALDRIVETEMPERATURE | Define CRITICAL threshold for the temperature of the drives | | | -| CRITICALPSUACSTATUS | Define the conditions on psu ac to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUACSTATUS | Define the conditions on psu ac to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUACSTATUS | Define the conditions on psu ac to match for the status to be WARNING | | | -| CRITICALPSUDCSTATUS | Define the conditions on psu dc to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUDCSTATUS | Define the conditions on psu dc to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUDCSTATUS | Define the conditions on psu dc to match for the status to be WARNING | | | -| CRITICALPSUFANSTATUS | Define the conditions on psu fan to match for the status to be CRITICAL | %{status} !~ /ok/i | | +| CRITICALPSUFANSTATUS | Define the conditions on psu fan to match for the status to be CRITICAL | %\{status\} !~ /ok/i | | | WARNINGPSUFANSTATUS | Define the conditions on psu fan to match for the status to be WARNING | | | -| CRITICALPSUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{cage\_id} | %{status} !~ /Normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{cage\_id} | | | +| CRITICALPSUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{cage_id\} | %\{status\} !~ /Normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{cage_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -376,8 +376,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | Macro | Description | Default value | Mandatory | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter disk name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Warning threshold | | | | WARNINGUSAGEFREE | Warning threshold | | | @@ -394,8 +394,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh | FILTERNODEID | Filter nodes by ID (can be a regexp) | | | | WARNINGCPUUTILIZATION | Warning threshold | | | | CRITICALCPUUTILIZATION | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -405,20 +405,20 @@ yum install centreon-plugin-Hardware-Storage-Hp-3par-Ssh |:-------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-----------:| | FILTERNODEID | Filter nodes by ID (can be a regexp) | | | | FILTERPSUID | Filter power supplies by ID (can be a regexp) | | | -| CRITICALACSTATUS | Set critical threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGACSTATUS | Set warning threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALBATTERYSTATUS | Set critical threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGBATTERYSTATUS | Set warning threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | +| CRITICALACSTATUS | Set critical threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGACSTATUS | Set warning threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALBATTERYSTATUS | Set critical threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGBATTERYSTATUS | Set warning threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | | WARNINGCHARGEREMAINING | Warning threshold | | | | CRITICALCHARGEREMAINING | Critical threshold | | | | WARNINGCHARGEREMAININGMINUTES | Warning threshold | | | | CRITICALCHARGEREMAININGMINUTES | Critical threshold | | | -| CRITICALDCSTATUS | Set critical threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGDCSTATUS | Set warning threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALFANSTATUS | Set critical threshold for fan status . You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGFANSTATUS | Set warning threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | %{status} !~ /ok/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | | | +| CRITICALDCSTATUS | Set critical threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGDCSTATUS | Set warning threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALFANSTATUS | Set critical threshold for fan status . You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGFANSTATUS | Set warning threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | %\{status\} !~ /ok/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). Toutes les options sont listées [ici](#options-disponibles). | --verbose | | @@ -552,7 +552,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -602,7 +602,7 @@ All available options for each service template are listed below: | --filter-volume-name | Filter volumes by name (can be a regexp). | | --unknown-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-status | Define the conditions to match for the status to be WARNING. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{node\_id} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{node_id\} | | --warning-* | Define the WARNING thresholds for the following components: 'flashcache-usage', 'flashcache-usage-free', 'flashcache-usage-prct', 'flashcache-node-readhits', 'flashcache-volume-readhits'. | | --critical-* | Define the CRITICAL thresholds for the following components: 'flashcache-usage', 'flashcache-usage-free', 'flashcache-usage-prct', 'flashcache-node-readhits', 'flashcache-volume-readhits'. | @@ -614,25 +614,25 @@ All available options for each service template are listed below: | --filter-cage-id | Filter cages by ID (can be a regexp). | | --unknown-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-status | Define the conditions to match for the status to be WARNING. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Normal/i') You can use the following variables: %{status}, %{cage\_id} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Normal/i') You can use the following variables: %\{status\}, %\{cage_id\} | | --unknown-board-firmware-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-board-firmware-status | Define the conditions to match for the status to be WARNING. | -| --critical-board-firmware-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Current/i') You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | +| --critical-board-firmware-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Current/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | --unknown-board-\[self\|partner\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-board-\[self\|partner\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-board-\[self\|partner\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{board\_id} | +| --critical-board-\[self\|partner\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{board_id\} | | --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-psu-status | Define the conditions to match for the status to be WARNING. | -| --critical-psu-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | +| --critical-psu-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | --unknown-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{psu\_id} | +| --critical-psu-\[ac\|dc\|fan\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{psu_id\} | | --unknown-drive-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-drive-status | Define the conditions to match for the status to be WARNING. | -| --critical-drive-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | +| --critical-drive-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | --unknown-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be WARNING. | -| --critical-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i') You can use the following variables: %{status}, %{cage\_id}, %{drive\_id} | +| --critical-drive-\[porta\|portb\]-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i') You can use the following variables: %\{status\}, %\{cage_id\}, %\{drive_id\} | | --warning-drive-temperature | Define WARNING threshold for the temperature of the drives. | | --critical-drive-temperature | Define CRITICAL threshold for the temperature of the drives. | @@ -664,8 +664,8 @@ All available options for each service template are listed below: |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter disk name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Warning threshold. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | @@ -674,9 +674,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-node-id | Filter nodes by ID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{node\_id} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{node_id\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization'. | @@ -686,21 +686,21 @@ All available options for each service template are listed below: |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-node-id | Filter nodes by ID (can be a regexp). | | --filter-psu-id | Filter power supplies by ID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-ac-status | Set unknown threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-ac-status | Set warning threshold for AC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-ac-status | Set critical threshold for AC status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-dc-status | Set unknown threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-dc-status | Set warning threshold for DC status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-dc-status | Set critical threshold for DC status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-fan-status | Set unknown threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-fan-status | Set warning threshold for fan status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-fan-status | Set critical threshold for fan status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --unknown-battery-status | Set unknown threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --warning-battery-status | Set warning threshold for battery status. You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | -| --critical-battery-status | Set critical threshold for battery status (default: '%{status} !~ /ok/i'). You can use the following variables: %{status}, %{node\_id}, %{psu\_id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-ac-status | Set unknown threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-ac-status | Set warning threshold for AC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-ac-status | Set critical threshold for AC status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-dc-status | Set unknown threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-dc-status | Set warning threshold for DC status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-dc-status | Set critical threshold for DC status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-fan-status | Set unknown threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-fan-status | Set warning threshold for fan status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-fan-status | Set critical threshold for fan status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --unknown-battery-status | Set unknown threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --warning-battery-status | Set warning threshold for battery status. You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | +| --critical-battery-status | Set critical threshold for battery status (default: '%\{status\} !~ /ok/i'). You can use the following variables: %\{status\}, %\{node_id\}, %\{psu_id\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining', 'charge-remaining-minutes. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md index de80cf996eb0..b4174cbdc3f2 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-lefthand-snmp.md @@ -216,8 +216,8 @@ yum install centreon-plugin-Hardware-Storage-Hp-Lefthand-Snmp | CRITICALREADIOPS | Critical threshold | | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /normal/i | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /normal/i | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Critical threshold | | | | WARNINGWRITE | Warning threshold | | | @@ -263,7 +263,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-write-latency='' \ --critical-write-latency='' \ --warning-replication-status='' \ - --critical-replication-status='%{status} !~ /normal/i' \ + --critical-replication-status='%\{status\} !~ /normal/i' \ --verbose ``` @@ -319,7 +319,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -399,8 +399,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^read\|write$' | | --filter-name | Filter volume name (can be a regexp). | -| --warning-replication-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/i'). You can use the following variables: %{status}, %{display} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'read' (b/s), 'write' (b/s), 'read-iops', 'write-iops', 'read-latency', 'write-latency', 'usage'. | | --critical-* | Critical threshold. Can be: 'read' (b/s), 'write' (b/s), 'read-iops', 'write-iops', 'read-latency', 'write-latency', 'usage'. | | --units | Units of thresholds (default: '%') ('%', 'B'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md index b23894d1a7f5..49ceb2a4dc92 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hp-msa2000-snmp.md @@ -249,7 +249,7 @@ yum install centreon-plugin-Hardware-Storage-Hp-Msa2000-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -334,7 +334,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -419,9 +419,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md index a7318d90366b..b2c2d92790aa 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-hpe-primera-restapi.md @@ -321,8 +321,8 @@ yum install centreon-plugin-Hardware-Storage-Hpe-Primera-Restapi | CRITICALDISKSTOTAL | Thresholds. | | | | WARNINGDISKSUNKNOWN | Thresholds. | | | | CRITICALDISKSUNKNOWN | Thresholds. | | | -| WARNINGSTATUS | Define the condition to match for the returned status to be WARNING. Default: '%{status} =~ /^(new\|degraded\|unknown)$/' | %{status} =~ /^(new\|degraded\|unknown)$/ | | -| CRITICALSTATUS | Define the condition to match for the returned status to be CRITICAL. Default: '%{status} =~ /failed/' | %{status} =~ /failed/ | | +| WARNINGSTATUS | Define the condition to match for the returned status to be WARNING. Default: '%\{status\} =~ /^(new\|degraded\|unknown)$/' | %\{status\} =~ /^(new\|degraded\|unknown)$/ | | +| CRITICALSTATUS | Define the condition to match for the returned status to be CRITICAL. Default: '%\{status\} =~ /failed/' | %\{status\} =~ /failed/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -369,8 +369,8 @@ yum install centreon-plugin-Hardware-Storage-Hpe-Primera-Restapi | Macro | Description | Default value | Mandatory | |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:---------:| | FILTERNODEID | Define which nodes (filtered by regular expression) should be monitored. Example: --filter-node='^(0\|1)$' | | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the %{status} variables. | %{status} ne "online" | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the %{status} variables. | | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the %\{status\} variables. | %\{status\} ne "online" | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the %\{status\} variables. | | | | WARNINGOFFLINE | Thresholds for the number of offline nodes | 0:0 | | | CRITICALOFFLINE | Thresholds for the number of offline nodes | | | | WARNINGONLINE | Thresholds for the number of online nodes | | | @@ -484,7 +484,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -551,9 +551,9 @@ All available options for each service template are listed below: | --filter-model | Define which volumes should be monitored based on the disk model. This option will be treated as a regular expression. | | --filter-serial | Define which volumes should be monitored based on the disk serial number. This option will be treated as a regular expression. | | --filter-position | Define which volumes should be monitored based on the disk position. The position is composed of 3 integers, separated by colons: - Cage number where the physical disk is in. - Magazine number where the physical disk is in. - For DC4 cages, disk position within the magazine. For non-DC4 cages, 0. Example: 7:5:0 This option will be treated as a regular expression. | -| --warning-status | Define the condition to match for the returned status to be WARNING. Default: '%{status} =~ /^(new\|degraded\|unknown)$/' | -| --critical-status | Define the condition to match for the returned status to be CRITICAL. Default: '%{status} =~ /failed/' | -| --unknown-status | Define the condition to match for the returned status to be UNKNOWN. Default: '%{status} =~ /NOT\_DOCUMENTED$/' | +| --warning-status | Define the condition to match for the returned status to be WARNING. Default: '%\{status\} =~ /^(new\|degraded\|unknown)$/' | +| --critical-status | Define the condition to match for the returned status to be CRITICAL. Default: '%\{status\} =~ /failed/' | +| --unknown-status | Define the condition to match for the returned status to be UNKNOWN. Default: '%\{status\} =~ /NOT\_DOCUMENTED$/' | | --warning-* --critical-* | Thresholds. '*' may stand for 'disks-total', 'disks-normal', 'disks-degraded', 'disks-new', 'disks-failed', 'disks-unknown'. | @@ -583,8 +583,8 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:----------------------------------------------------------------------------------------------------------------------------------------| | --filter-node | Define which nodes (filtered by regular expression) should be monitored. Example: --filter-node='^(0\|1)$' | -| --warning-node-status | Define the conditions to match for the status to be WARNING. (default: '%{status} ne "online"'). You can use the %{status} variables. | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL You can use the %{status} variables. | +| --warning-node-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} ne "online"'). You can use the %\{status\} variables. | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL You can use the %\{status\} variables. | | --warning-total | Thresholds for the total number of nodes. | | --critical-total | Thresholds for the total number of nodes. | | --warning-online | Thresholds for the number of online nodes. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md index c3af896e51d8..d64d0fc3d05d 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds3000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md index f990d1ae0790..fc6f2b677986 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds4000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md index d2a24d146744..c7916384549b 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ds5000-smcli.md @@ -27,7 +27,7 @@ When you install the package, choose 'Management Station': 4- Customize... - ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS TO ACCEPT THE + ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS \ TO ACCEPT THE DEFAULT : 2 After install, monitoring engine user needs root privileges to execute the diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md index 6ef0e6e1bc95..424bd12a8ef6 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-storwize-ssh.md @@ -232,8 +232,8 @@ yum install centreon-plugin-Hardware-Storage-Ibm-Storwize-Ssh | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERNAME | Filter pool name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /degraded/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /degraded/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /offline/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /degraded/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /degraded/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /offline/i | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -244,8 +244,8 @@ yum install centreon-plugin-Hardware-Storage-Ibm-Storwize-Ssh | Macro | Description | Default value | Mandatory | |:---------------------------|:-------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERCONSISTENCYGROUPNAME | Filter group name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /idling/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /idling/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -329,7 +329,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -402,8 +402,8 @@ All available options for each service template are listed below: |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter pool name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /degraded/i'). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /degraded/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage'. | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md index 9d4ec21e6e5d..1563c51c33e6 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3100-snmp.md @@ -252,7 +252,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md index b542a1ce03b3..09c90490ebda 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-ibm-ts3200-snmp.md @@ -252,7 +252,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md index 29e0c25e5a56..88ffeb13e3a0 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-lenovo-sseries-snmp.md @@ -221,7 +221,7 @@ yum install centreon-plugin-Hardware-Storage-Lenovo-Sseries-Snmp | CRITICALIN | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -306,7 +306,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -391,9 +391,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md index 361633792b01..31c7c656b32d 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-ontap-restapi.md @@ -295,8 +295,8 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | CRITICALREADIOPS | Thresholds | | | | WARNINGREADLATENCY | Thresholds | | | | CRITICALREADLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALIOPS | Thresholds | | | @@ -322,9 +322,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Default value | Mandatory | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| -| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{link\_status}, %{display} | | | -| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "online"'). You can use the following variables: %{state}, %{link\_status}, %{display} | %{state} ne "online" | | -| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{link\_status}, %{display} | | | +| UNKNOWNNODESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | | +| CRITICALNODESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "online"'). You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | %\{state\} ne "online" | | +| WARNINGNODESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADIOPS | Thresholds | | | @@ -353,9 +353,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERNAME | Filter LUN name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{container\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{container\_state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{container\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -381,9 +381,9 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------|:-----------:| | FILTERNAME | Filter snapmirror name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{healthy} ne "true" or %{state} eq "broken\_off"'). You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | %{healthy} ne "true" or %{state} eq "broken\_off" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{healthy\} ne "true" or %\{state\} eq "broken\_off"'). You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | %\{healthy\} ne "true" or %\{state\} eq "broken\_off" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -392,15 +392,15 @@ yum install centreon-plugin-Hardware-Storage-Netapp-Ontap-Restapi | Macro | Description | Default value | Mandatory | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERNAME | Filter volumes by volume name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADIOPS | Thresholds | | | | CRITICALREADIOPS | Thresholds | | | | WARNINGREADLATENCY | Thresholds | | | | CRITICALREADLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | %{state} !~ /online/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} !~ /online/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -438,7 +438,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-name='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{state} !~ /online/i' \ + --critical-status='%\{state\} !~ /online/i' \ --warning-usage='' \ --critical-usage='' \ --warning-usage-free='' \ @@ -524,7 +524,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -568,9 +568,9 @@ All available options for each service template are listed below: |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter aggregates by aggregate name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'read' (B/s), 'read-iops', 'write' (B/s), 'write-iops', 'read-latency' (ms), 'write-latency' (ms), 'total-latency' (ms), 'other-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | @@ -591,9 +591,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='node-status' | -| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{link\_status}, %{display} | -| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{link\_status}, %{display} | -| --critical-node-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "online"'). You can use the following variables: %{state}, %{link\_status}, %{display} | +| --unknown-node-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | +| --warning-node-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | +| --critical-node-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "online"'). You can use the following variables: %\{state\}, %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization' (%), 'read' (B/s), 'write' (B/s), 'read-iops', 'write-iops', 'read-latency' (ms), 'write-lantency' (ms), 'other-latency' (ms), 'total-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | @@ -612,9 +612,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter LUN name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{container\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{container\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{container\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{container_state\}, %\{display\} | @@ -633,9 +633,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter snapmirror name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{healthy} ne "true" or %{state} eq "broken\_off"'). You can use the following variables: %{healthy}, %{state}, %{transfer\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{healthy\} ne "true" or %\{state\} eq "broken\_off"'). You can use the following variables: %\{healthy\}, %\{state\}, %\{transfer_state\}, %\{display\} | @@ -645,9 +645,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^usage$' | | --filter-name | Filter volumes by volume name (can be a regexp). | | --filter-vserver-name | Filter volumes by vserver name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} !~ /online/i'). You can use the following variables: %{state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} !~ /online/i'). You can use the following variables: %\{state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'read' (B/s), 'read-iops', 'write' (B/s), 'write-iops', 'read-latency' (ms), 'write-latency' (ms), 'total-latency' (ms), 'other-latency' (ms), 'other' (B/s), 'total' (B/s), 'other-iops', 'total-iops'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md index 5901f141b227..142ebc538aa6 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-netapp-santricity-restapi.md @@ -153,8 +153,8 @@ Once the Centreon plugin installed, you can test it directly from the CLI by log --api-password='xxxx' \ --mode='storage-volumes' \ --verbose \ - --warning-volume-status='%{status} =~ /degraded/i' - --critical-volume-status='%{status} =~ /failed/i' + --warning-volume-status='%\{status\} =~ /degraded/i' + --critical-volume-status='%\{status\} =~ /failed/i' ``` Expected command output is shown below: diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md b/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md index 3c9babb29cff..c5dfe990f8ba 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-flasharray-v2-restapi.md @@ -229,8 +229,8 @@ yum install centreon-plugin-Hardware-Storage-Purestorage-Flasharray-V2-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| | FILTERCATEGORY | Filter by category name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} ne "closed" and %{severity} =~ /warning/i') You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | %{state} ne "closed" and %{severity} =~ /warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "closed" and %{severity} =~ /critical/i'). You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | %{state} ne "closed" and %{severity} =~ /critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} ne "closed" and %\{severity\} =~ /warning/i') You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | %\{state\} ne "closed" and %\{severity\} =~ /warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "closed" and %\{severity\} =~ /critical/i'). You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | %\{state\} ne "closed" and %\{severity\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -369,7 +369,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -424,8 +424,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-category | Filter by category name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} ne "closed" and %{severity} =~ /warning/i') You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} ne "closed" and %{severity} =~ /critical/i'). You can use the following variables: %{category}, %{code}, %{severity}, %{opened}, %{state}, %{issue}, %{component\_name} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} ne "closed" and %\{severity\} =~ /warning/i') You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} ne "closed" and %\{severity\} =~ /critical/i'). You can use the following variables: %\{category\}, %\{code\}, %\{severity\}, %\{opened\}, %\{state\}, %\{issue\}, %\{component_name\} | | --memory | Only check new alarms. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md index c9fc2ee6bb51..9df2ce86d2d2 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-purestorage-snmp.md @@ -286,7 +286,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md index 67a989b12ff2..b13572e80d53 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-qnap-snmp.md @@ -327,8 +327,8 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERNAME | Filter pools by name (can be a regexp) | | | -| WARNINGPOOLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /degraded\|warning/i | | -| CRITICALPOOLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /error\|critical/i | | +| WARNINGPOOLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /degraded\|warning/i | | +| CRITICALPOOLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /error\|critical/i | | | WARNINGSPACEUSAGE | Threshold | | | | CRITICALSPACEUSAGE | Threshold | | | | WARNINGSPACEUSAGEFREE | Threshold | | | @@ -371,7 +371,7 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | WARNINGIN | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -386,8 +386,8 @@ yum install centreon-plugin-Hardware-Storage-Qnap-Snmp | CRITICALSPACEUSAGEFREE | Threshold | | | | WARNINGSPACEUSAGEPRCT | Threshold | | | | CRITICALSPACEUSAGEPRCT | Threshold | | | -| WARNINGVOLUMESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /degraded\|warning/i | | -| CRITICALVOLUMESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /critical/i | | +| WARNINGVOLUMESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /degraded\|warning/i | | +| CRITICALVOLUMESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -508,7 +508,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -618,9 +618,9 @@ All available options for each service template are listed below: |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter pools by name (can be a regexp). | -| --unknown-pool-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-pool-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded\|warning/i'). You can use the following variables: %{status}, %{name} | -| --critical-pool-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /error\|critical/i'). You can use the following variables: %{status}, %{name} | +| --unknown-pool-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-pool-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded\|warning/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-pool-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /error\|critical/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage-prct', 'space-usage', 'space-usage-free'. | @@ -649,9 +649,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -681,9 +681,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter volumes by name (can be a regexp). | | --force-counters-legacy | Force to use legacy counters. Should be used when EX/QTS counters are buggy. | -| --unknown-volume-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-volume-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded\|warning/i'). You can use the following variables: %{status}, %{name} | -| --critical-volume-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /critical/i'). You can use the following variables: %{status}, %{name} | +| --unknown-volume-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-volume-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded\|warning/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-volume-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /critical/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage-prct', 'space-usage', 'space-usage-free'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md index 09382f7f6225..e6d169a255f0 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-quantum-scalar-snmp.md @@ -268,7 +268,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md index e1e673e8a541..603e4b4a4b0f 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-synology-snmp.md @@ -354,7 +354,7 @@ yum install centreon-plugin-Hardware-Storage-Synology-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -458,7 +458,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -621,9 +621,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md index e164b962336b..01e92d3d9ac4 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-storage-wd-nas-snmp.md @@ -219,8 +219,8 @@ yum install centreon-plugin-Hardware-Storage-Wd-Nas-Snmp |:--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | WARNINGDRIVETEMPERATURE | Warning threshold for 'drive-temperature' | | | | CRITICALDRIVETEMPERATURE | Critical threshold for 'drive-temperature' | | | -| WARNINGFANSTATUS | Define the conditions to match for the status to be WARNING (default : '%{status} ne "running"'). You can use the following variables: %{status} | | | -| CRITICALFANSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGFANSTATUS | Define the conditions to match for the status to be WARNING (default : '%\{status\} ne "running"'). You can use the following variables: %\{status\} | | | +| CRITICALFANSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSYSTEMTEMPERATURE | Warning threshold for 'system-temperature' | | | | CRITICALSYSTEMTEMPERATURE | Critical threshold for 'system-temperature' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -319,7 +319,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -373,8 +373,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-fan-status | Define the conditions to match for the status to be WARNING (default : '%{status} ne "running"'). You can use the following variables: %{status} | -| --critical-fan-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --warning-fan-status | Define the conditions to match for the status to be WARNING (default : '%\{status\} ne "running"'). You can use the following variables: %\{status\} | +| --critical-fan-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'system-temperature', 'drive-temperature'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md index 0a94a1d9abae..9e5545673b19 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-alpha-snmp.md @@ -196,13 +196,13 @@ yum install centreon-plugin-Hardware-Ups-Alpha-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Warning threshold | | | | CRITICALCURRENT | Critical threshold | | | | WARNINGLOAD | Warning threshold | | | | CRITICALLOAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status} | %{status} =~ /batteryLow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /batteryDepleted/i'). You can use the following variables: %{status} | %{status} =~ /batteryDepleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryLow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /batteryDepleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDepleted/i | | | WARNINGTEMPERATURE | Warning threshold | | | | CRITICALTEMPERATURE | Critical threshold | | | | WARNINGVOLTAGE | Warning threshold | | | @@ -227,9 +227,9 @@ is able to monitor a resource using a command like this one (replace the sample --hostname=10.0.0.1 \ --snmp-version='2c' \ --snmp-community='my-snmp-community' \ - --unknown-status='%{status} =~ /unknown/i' \ - --warning-status='%{status} =~ /batteryLow/i' \ - --critical-status='%{status} =~ /batteryDepleted/i' \ + --unknown-status='%\{status\} =~ /unknown/i' \ + --warning-status='%\{status\} =~ /batteryLow/i' \ + --critical-status='%\{status\} =~ /batteryDepleted/i' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -291,7 +291,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -355,9 +355,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /batteryDepleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /batteryDepleted/i'). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'load', 'voltage', 'current', 'temperature'. | | --critical-* | Critical threshold. Can be: 'load', 'voltage', 'current', 'temperature'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md index 8070cb615ffe..1e991562820a 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-apc-snmp.md @@ -237,14 +237,14 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | Macro | Description | Default value | Mandatory | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{replace} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{status\} =~ /unknown/i | | | REPLACELASTTIMEFORMAT | Define the date format (default: '%m/%d/%Y') | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status}, %{replace} | %{status} =~ /batteryLow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{replace} =~ /yes/i'). You can use the following variables: %{status}, %{replace} | %{replace} =~ /yes/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{status\} =~ /batteryLow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{replace\} =~ /yes/i'). You can use the following variables: %\{status\}, %\{replace\} | %\{replace\} =~ /yes/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGTIME | Thresholds | | | @@ -268,8 +268,8 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | CRITICALLINEPHASEPOWER | Thresholds | | | | WARNINGLINEPHASEVOLTAGE | Thresholds | | | | CRITICALLINEPHASEVOLTAGE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_cause} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_cause} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_cause\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_cause\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -279,15 +279,15 @@ yum install centreon-plugin-Hardware-Ups-Apc-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | | WARNINGLOAD | Thresholds | 90 | | | CRITICALLOAD | Thresholds | 95 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /onLine\|rebooting/i'). You can use the following variables: %{status} | %{status} !~ /onLine\|rebooting/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /onLine\|rebooting/i'). You can use the following variables: %\{status\} | %\{status\} !~ /onLine\|rebooting/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -396,7 +396,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -452,15 +452,15 @@ All available options for each service template are listed below: |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | | --replace-lasttime-format | Define the date format (default: '%m/%d/%Y'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{replace} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /batteryLow/i'). You can use the following variables: %{status}, %{replace} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{replace} =~ /yes/i'). You can use the following variables: %{status}, %{replace} | -| --unknown-battery-pack-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-battery-pack-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-battery-pack-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "OK"'). You can use the following variables: %{status} | -| --unknown-cartridge-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-cartridge-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-cartridge-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} ne "OK"'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /batteryLow/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{replace\} =~ /yes/i'). You can use the following variables: %\{status\}, %\{replace\} | +| --unknown-battery-pack-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-battery-pack-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-battery-pack-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "OK"'). You can use the following variables: %\{status\} | +| --unknown-cartridge-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-cartridge-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-cartridge-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} ne "OK"'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'temperature', 'time', 'replace-lasttime', 'timeon'. | @@ -469,8 +469,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^frequence\|voltage$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{last\_cause} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{last\_cause} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{last_cause\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{last_cause\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence', 'line-frequence', 'line-phase-voltage', 'line-phase-current', 'line-phase-power'. | @@ -479,9 +479,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status\|load$' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /onLine\|rebooting/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /onLine\|rebooting/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'frequence'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md index c20dd32a4834..d83aa1f577b0 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-cyberpower-snmp.md @@ -203,11 +203,11 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Default value | Mandatory | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | %{status} =~ /unknown\|notPresent/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown\|notPresent/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -219,11 +219,11 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -233,7 +233,7 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -242,8 +242,8 @@ yum install centreon-plugin-Hardware-Ups-Cyberpower-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -268,7 +268,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /normal/' \ + --critical-status='%\{status\} !~ /normal/' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -334,7 +334,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -388,9 +388,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'voltage' (V), 'temperature' (C). | @@ -398,9 +398,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence'. | @@ -408,9 +408,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power', 'frequence'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md index 6a6a34056c0b..72883d395b76 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-ees-snmp.md @@ -224,9 +224,9 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Default value | Mandatory | |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------|:-----------:| -| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{battery\_mode} | %{battery\_mode} =~ /unknown/i | | -| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be WARNING. You can use the following variables: %{battery\_mode} | %{battery_mode} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|ManualBoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostCharging\|MasterBateryTesting/i | | -| CRITICALBATTERYMODE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{battery\_mode} | %{battery\_mode} =~ /ACFailTesting\|ACFail/i | | +| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /unknown/i | | +| UNKNOWNBATTERYMODE | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|ManualBoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostCharging\|MasterBateryTesting/i | | +| CRITICALBATTERYMODE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{battery_mode\} | %\{battery_mode\} =~ /ACFailTesting\|ACFail/i | | | WARNINGCAPACITY | Thresholds | | | | CRITICALCAPACITY | Thresholds | | | | WARNINGCURRENT | Thresholds | | | @@ -258,8 +258,8 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | CRITICALCOMMUNICATING | Thresholds | | | | WARNINGINSTALLED | Thresholds | | | | CRITICALINSTALLED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | %{installed} != %{communicating} | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | %\{installed\} != %\{communicating\} | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | | | | WARNINGUSEDCAPACITY | Thresholds | | | | CRITICALUSEDCAPACITY | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -269,11 +269,11 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /unknown\|unma\_status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /unknown\|unma\_status} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /warning\|minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system\_status}, %{communication\_status} | %{system\_status} =~ /major\|critical/i \|\| %{communication\_status} =~ /interrupt/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /warning\|minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\}, %\{communication_status\} | %\{system_status\} =~ /major\|critical/i \|\| %\{communication_status\} =~ /interrupt/i | | | WARNINGUSEDCAPACITY | Thresholds | | | | CRITICALUSEDCAPACITY | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -285,9 +285,9 @@ yum install centreon-plugin-Hardware-Ups-Ees-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNALARMSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /fail/i | | -| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /low/i | | -| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{alarm\_status}, %{type}, %{name} | %{alarm\_status} =~ /high/i | | +| UNKNOWNALARMSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /fail/i | | +| WARNINGALARMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /low/i | | +| CRITICALALARMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | %\{alarm_status\} =~ /high/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -376,7 +376,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -431,9 +431,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Thresholds: voltage (V), current (A), capacity (%), nominal-capacity (Ah) | -| --unknown-battery-mode | Define the conditions to match for the status to be UNKNOWN (default: '%{battery\_mode} =~ /unknown/i'). You can use the following variables: %{battery\_mode} | -| --warning-battery-mode | Define the conditions to match for the status to be WARNING (default: '%{battery\_mode} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|Manual BoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostC harging\|MasterBateryTesting/i'). You can use the following variables: %{battery\_mode} | -| --critical-battery-mode | Define the conditions to match for the status to be CRITICAL (default: '%{battery\_mode} =~ /ACFailTesting\|ACFail/i'). You can use the following variables: %{battery\_mode} | +| --unknown-battery-mode | Define the conditions to match for the status to be UNKNOWN (default: '%\{battery_mode\} =~ /unknown/i'). You can use the following variables: %\{battery_mode\} | +| --warning-battery-mode | Define the conditions to match for the status to be WARNING (default: '%\{battery_mode\} =~ /ShortTest\|BoostChargingForTest\|ManualTesting\|PlanTesting\|Manual BoostCharging\|AutoBoostCharging\|CyclicBoostCharging\|MasterBoostC harging\|MasterBateryTesting/i'). You can use the following variables: %\{battery_mode\} | +| --critical-battery-mode | Define the conditions to match for the status to be CRITICAL (default: '%\{battery_mode\} =~ /ACFailTesting\|ACFail/i'). You can use the following variables: %\{battery_mode\} | @@ -447,9 +447,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{installed} != %{communicating}'). You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{installed}, %{communicating}, %{used\_capacity} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{installed\} != %\{communicating\}'). You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{installed\}, %\{communicating\}, %\{used_capacity\} | | --warning-* --critical-* | Thresholds. Can be: 'used-capacity', 'installed', 'communicating' | @@ -457,9 +457,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{system\_status} =~ /unknown\|unmanaged\|restricted\|testing\|disabled/i \|\| %{communication\_status} =~ /unknown/i'). You can use the following variables: %{system\_status}, %{communication\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{system\_status} =~ /warning\|minor/i'). You can use the following variables: %{system\_status}, %{communication\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{system\_status} =~ /major\|critical/i \|\| %{communication\_status} =~ /interrupt/i'). You can use the following variables: %{system\_status}, %{communication\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{system_status\} =~ /unknown\|unmanaged\|restricted\|testing\|disabled/i \|\| %\{communication_status\} =~ /unknown/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{system_status\} =~ /warning\|minor/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{system_status\} =~ /major\|critical/i \|\| %\{communication_status\} =~ /interrupt/i'). You can use the following variables: %\{system_status\}, %\{communication_status\} | | --warning-* --critical-* | Thresholds: voltage (V), current (A), used-capacity (%) | @@ -467,9 +467,9 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN (default: '%{alarm\_status} =~ /fail/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | -| --warning-alarm-status | Define the conditions to match for the status to be WARNING (default: '%{alarm\_status} =~ /low/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | -| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%{alarm\_status} =~ /high/i'). You can use the following variables: %{alarm\_status}, %{type}, %{name} | +| --unknown-alarm-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{alarm_status\} =~ /fail/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | +| --warning-alarm-status | Define the conditions to match for the status to be WARNING (default: '%\{alarm_status\} =~ /low/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | +| --critical-alarm-status | Define the conditions to match for the status to be CRITICAL (default: '%\{alarm_status\} =~ /high/i'). You can use the following variables: %\{alarm_status\}, %\{type\}, %\{name\} | | --warning-temperature --critical-temperature | Thresholds: temperature (C) | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md index ded257a0724a..1712c4292c90 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-himoinsa-snmp.md @@ -260,16 +260,16 @@ yum install centreon-plugin-Hardware-Ups-Himoinsa-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGALARMSTATUS | Warning threshold for alarm (default: '%{status} =~ /^alarm/'). Can use special variables like: %{status} | %{status} =~ /^alarm/ | | -| CRITICALALARMSTATUS | Critical threshold for alarm. Can use special variables like: %{status} | | | -| WARNINGCLOSEDCOMMUTATOR | Warning threshold for commutator currently closed. Can use special variables like: %{status} | | | -| CRITICALCLOSEDCOMMUTATOR | Critical threshold for commutator currently closed. Can use special variables like: %{status} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%{status} =~ /mains/i' | | | -| WARNINGMODESTATUS | Warning threshold for commutator mode status. Can use special variables like: %{status} | | | -| CRITICALMODESTATUS | Critical threshold for commutator mode status. Can use special variables like: %{status} | | | -| WARNINGMOTORSTATUS | Warning threshold for motor status. Can use special variables like: %{status} | | | -| CRITICALMOTORSTATUS | Critical threshold for motor status. Can use special variables like: %{status} | | | -| WARNINGTRANSFERPUMPSTATUS | Warning threshold for transfer pump status. Can use special variables like: %{status} | | | -| CRITICALTRANSFERPUMPSTATUS | Critical threshold for transfer pump status. Can use special variables like: %{status} | | | +| WARNINGALARMSTATUS | Warning threshold for alarm (default: '%\{status\} =~ /^alarm/'). Can use special variables like: %\{status\} | %\{status\} =~ /^alarm/ | | +| CRITICALALARMSTATUS | Critical threshold for alarm. Can use special variables like: %\{status\} | | | +| WARNINGCLOSEDCOMMUTATOR | Warning threshold for commutator currently closed. Can use special variables like: %\{status\} | | | +| CRITICALCLOSEDCOMMUTATOR | Critical threshold for commutator currently closed. Can use special variables like: %\{status\} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%\{status\} =~ /mains/i' | | | +| WARNINGMODESTATUS | Warning threshold for commutator mode status. Can use special variables like: %\{status\} | | | +| CRITICALMODESTATUS | Critical threshold for commutator mode status. Can use special variables like: %\{status\} | | | +| WARNINGMOTORSTATUS | Warning threshold for motor status. Can use special variables like: %\{status\} | | | +| CRITICALMOTORSTATUS | Critical threshold for motor status. Can use special variables like: %\{status\} | | | +| WARNINGTRANSFERPUMPSTATUS | Warning threshold for transfer pump status. Can use special variables like: %\{status\} | | | +| CRITICALTRANSFERPUMPSTATUS | Critical threshold for transfer pump status. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -402,7 +402,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,16 +478,16 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-alarm-status | Warning threshold for alarm (default: '%{status} =~ /^alarm/'). Can use special variables like: %{status} | -| --critical-alarm-status | Critical threshold for alarm. Can use special variables like: %{status} | -| --warning-motor-status | Warning threshold for motor status. Can use special variables like: %{status} | -| --critical-motor-status | Critical threshold for motor status. Can use special variables like: %{status} | -| --warning-mode-status | Warning threshold for commutator mode status. Can use special variables like: %{status} | -| --critical-mode-status | Critical threshold for commutator mode status. Can use special variables like: %{status} | -| --warning-closed-commutator | Warning threshold for commutator currently closed. Can use special variables like: %{status} | -| --critical-closed-commutator | Critical threshold for commutator currently closed. Can use special variables like: %{status} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%{status} =~ /mains/i' | -| --warning-transfer-pump-status | Warning threshold for transfer pump status. Can use special variables like: %{status} | -| --critical-transfer-pump-status | Critical threshold for transfer pump status. Can use special variables like: %{status} | +| --warning-alarm-status | Warning threshold for alarm (default: '%\{status\} =~ /^alarm/'). Can use special variables like: %\{status\} | +| --critical-alarm-status | Critical threshold for alarm. Can use special variables like: %\{status\} | +| --warning-motor-status | Warning threshold for motor status. Can use special variables like: %\{status\} | +| --critical-motor-status | Critical threshold for motor status. Can use special variables like: %\{status\} | +| --warning-mode-status | Warning threshold for commutator mode status. Can use special variables like: %\{status\} | +| --critical-mode-status | Critical threshold for commutator mode status. Can use special variables like: %\{status\} | +| --warning-closed-commutator | Warning threshold for commutator currently closed. Can use special variables like: %\{status\} | +| --critical-closed-commutator | Critical threshold for commutator currently closed. Can use special variables like: %\{status\} For example if you want to get an alert if the closed commutator is mains: --critical-closed-commutator='%\{status\} =~ /mains/i' | +| --warning-transfer-pump-status | Warning threshold for transfer pump status. Can use special variables like: %\{status\} | +| --critical-transfer-pump-status | Critical threshold for transfer pump status. Can use special variables like: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md index fa9a84e7665b..edd0cb83f4f9 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-hp-snmp.md @@ -214,15 +214,15 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | %{status} =~ /batteryDischarging/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDischarging/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -262,7 +262,7 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| UNKNOWNSOURCE | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{source} | | | +| UNKNOWNSOURCE | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{source\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -271,8 +271,8 @@ yum install centreon-plugin-Hardware-Ups-Hp-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSOURCE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{source} | %{source} !~ /normal/i | | -| WARNINGSOURCE | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{source} | | | +| CRITICALSOURCE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{source\} | %\{source\} !~ /normal/i | | +| WARNINGSOURCE | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{source\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -361,7 +361,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -416,9 +416,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V). | @@ -440,9 +440,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{source}. | -| --warning-source | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{source}. | -| --critical-source | Define the conditions to match for the status to be CRITICAL (default: '%{source} !~ /normal/i'). You can use the following variables: %{source}. | +| --unknown-source | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{source\}. | +| --warning-source | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{source\}. | +| --critical-source | Define the conditions to match for the status to be CRITICAL (default: '%\{source\} !~ /normal/i'). You can use the following variables: %\{source\}. | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md index b0c8f0f0fe11..b21614e4f917 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp.md @@ -235,8 +235,8 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| | WARNINGALARMSCURRENT | Thresholds | | | | CRITICALALARMSCURRENT | Thresholds | | | -| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneWarning\|aborted/ | | -| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneError/ | | +| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneWarning\|aborted/ | | +| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneError/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -244,13 +244,13 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNING | Thresholds | | | | CRITICAL | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -307,9 +307,9 @@ yum install centreon-plugin-Hardware-Ups-Sputnik-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /other/') You can use the following variables: %{status} | %{status} =~ /other/ | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | %{status} =~ /bypass\|battery\|booster\|reducer/ | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /none/') You can use the following variables: %{status} | %{status} =~ /none/ | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | %\{status\} =~ /other/ | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | %\{status\} =~ /bypass\|battery\|booster\|reducer/ | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | %\{status\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -448,9 +448,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --display-alarms | Display alarms in verbose output. | -| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{detail} | -| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | -| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | +| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{detail\} | +| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | +| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | | --warning-* --critical-* | Thresholds. Can be: 'alarms-current'. | @@ -458,9 +458,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -495,9 +495,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /other/') You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /none/') You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md index d397bfd49433..9069fb16a727 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-mge-snmp.md @@ -358,7 +358,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -431,8 +431,8 @@ All available options for each service template are listed below: |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* | Warning threshold. Can be: 'frequence', 'voltage', 'current'. | | --critical-* | Critical threshold. Can be: 'frequence', 'voltage', 'current'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{badstatus}, %{failcause} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{badstatus} =~ /yes/'). You can use the following variables: %{badstatus}, %{failcause} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{badstatus\}, %\{failcause\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{badstatus\} =~ /yes/'). You can use the following variables: %\{badstatus\}, %\{failcause\} | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md index 4bfdef033f79..b15a8f4fb3cc 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-nitram-snmp.md @@ -203,11 +203,11 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Default value | Mandatory | |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | %{status} =~ /unknown\|notPresent/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown\|notPresent/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -219,11 +219,11 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | | | | WARNINGFREQUENCE | Thresholds | | | | CRITICALFREQUENCE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -233,7 +233,7 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGFREQUENCE | Thresholds | | | @@ -242,8 +242,8 @@ yum install centreon-plugin-Hardware-Ups-Nitram-Snmp | CRITICALLOAD | Thresholds | | | | WARNINGPOWER | Thresholds | | | | CRITICALPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | %{status} !~ /normal/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | %\{status\} !~ /normal/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -268,7 +268,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} !~ /normal/' \ + --critical-status='%\{status\} !~ /normal/' \ --warning-load='' \ --critical-load='' \ --warning-current='' \ @@ -334,7 +334,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -388,9 +388,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown\|notPresent/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown\|notPresent/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'voltage' (V), 'temperature' (C). | @@ -398,9 +398,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /normal/'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /normal/'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'voltage', 'frequence'. | @@ -408,9 +408,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBattery\|onBypass/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power', 'frequence'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md index fe76d295bbd4..380ac7be90d5 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-phoenixtec-snmp.md @@ -203,8 +203,8 @@ yum install centreon-plugin-Hardware-Ups-Phoenixtec-Snmp | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -229,8 +229,8 @@ yum install centreon-plugin-Hardware-Ups-Phoenixtec-Snmp | CRITICALFREQUENCE | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBypass/i'). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /onBattery/i'). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBypass/i'). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /onBattery/i'). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | @@ -310,7 +310,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -365,9 +365,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'temperature' (C), 'voltage' (V). | @@ -382,9 +382,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /rebooting\|onBypass/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /onBattery/i'). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /rebooting\|onBypass/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /onBattery/i'). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current', 'power'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md index 3abdcf2b6a00..769a6566ad4f 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-powerware-snmp.md @@ -253,15 +253,15 @@ yum install centreon-plugin-Hardware-Ups-Powerware-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCHARGEREMAINING | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | WARNINGCURRENT | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALCURRENT | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryDischarging/i'). You can use the following variables: %{status} | %{status} =~ /batteryDischarging/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryDischarging/i'). You can use the following variables: %\{status\} | %\{status\} =~ /batteryDischarging/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | CRITICALVOLTAGE | Thresholds. : 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -405,7 +405,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -481,9 +481,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status\|current' | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /batteryDischarging/i'). You can use the following variables: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /batteryDischarging/i'). You can use the following variables: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}. | | --warning-* --critical-* | Thresholds. Can be: Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V). | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md index 0bfa2ebfd42b..73658c82872e 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-riello-snmp.md @@ -210,15 +210,15 @@ yum install centreon-plugin-Hardware-Ups-Riello-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -247,8 +247,8 @@ yum install centreon-plugin-Hardware-Ups-Riello-Snmp | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -327,7 +327,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -388,9 +388,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -406,9 +406,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------| | --ignore-zero-counters | Ignore counters equals to 0. | -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md index 8188a6b143c7..a893df6e0387 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-socomec-netvision-snmp.md @@ -213,15 +213,15 @@ yum install centreon-plugin-Hardware-Ups-Socomec-Netvision-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCHARGEREMAINING | Thresholds | | | | CRITICALCHARGEREMAINING | Thresholds | | | | WARNINGCHARGEREMAININGMINUTES | Thresholds | | | | CRITICALCHARGEREMAININGMINUTES | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted\|failure/i'). You can use the following variables: %{status} | %{status} =~ /depleted\|failure/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted\|failure/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted\|failure/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -246,13 +246,13 @@ yum install centreon-plugin-Hardware-Ups-Socomec-Netvision-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGVOLTAGE | Thresholds | | | | CRITICALVOLTAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -343,7 +343,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -404,9 +404,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /depleted\|failure/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /depleted\|failure/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -422,9 +422,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| | --ignore-zero-counters | Ignore counters equals to 0. | -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'load', 'voltage', 'current'. | diff --git a/pp/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md b/pp/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md index 16981d688535..88b279e85fe5 100644 --- a/pp/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md +++ b/pp/integrations/plugin-packs/procedures/hardware-ups-standard-rfc1628-snmp.md @@ -215,8 +215,8 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| | WARNINGALARMSCURRENT | Thresholds | | | | CRITICALALARMSCURRENT | Thresholds | | | -| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneWarning\|aborted/ | | -| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | %{status} =~ /doneError/ | | +| WARNINGTESTSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneWarning\|aborted/ | | +| CRITICALTESTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | %\{status\} =~ /doneError/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -224,13 +224,13 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | | WARNING | Thresholds | | | | CRITICAL | Thresholds | | | | WARNINGCURRENT | Thresholds | | | | CRITICALCURRENT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | %{status} =~ /low/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | %{status} =~ /depleted/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | %\{status\} =~ /low/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | %\{status\} =~ /depleted/i | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGVOLTAGE | Thresholds | | | @@ -276,9 +276,9 @@ yum install centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-----------:| -| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /other/') You can use the following variables: %{status} | %{status} =~ /other/ | | -| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | %{status} =~ /bypass\|battery\|booster\|reducer/ | | -| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /none/') You can use the following variables: %{status} | %{status} =~ /none/ | | +| UNKNOWNSOURCESTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | %\{status\} =~ /other/ | | +| WARNINGSOURCESTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | %\{status\} =~ /bypass\|battery\|booster\|reducer/ | | +| CRITICALSOURCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | %\{status\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -355,7 +355,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -410,9 +410,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --display-alarms | Display alarms in verbose output. | -| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{detail} | -| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /doneWarning\|aborted/'). You can use the following variables: %{status}, %{detail} | -| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /doneError/'). You can use the following variables: %{status}, %{detail} | +| --unknown-test-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{detail\} | +| --warning-test-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /doneWarning\|aborted/'). You can use the following variables: %\{status\}, %\{detail\} | +| --critical-test-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /doneError/'). You can use the following variables: %\{status\}, %\{detail\} | | --warning-* --critical-* | Thresholds. Can be: 'alarms-current'. | @@ -420,9 +420,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /low/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /depleted/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /low/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /depleted/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'charge-remaining' (%), 'charge-remaining-minutes', 'current' (A), 'voltage' (V), 'temperature' (C). | @@ -448,9 +448,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} =~ /other/') You can use the following variables: %{status} | -| --warning-source-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %{status} | -| --critical-source-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /none/') You can use the following variables: %{status} | +| --unknown-source-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} =~ /other/') You can use the following variables: %\{status\} | +| --warning-source-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /bypass\|battery\|booster\|reducer/') You can use the following variables: %\{status\} | +| --critical-source-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /none/') You can use the following variables: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md b/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md index 5172f3417001..23e0fc682479 100644 --- a/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md +++ b/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nrpe.md @@ -295,7 +295,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md b/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md index 189bbd3bbb08..25df0ed0ed5e 100644 --- a/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md +++ b/pp/integrations/plugin-packs/procedures/infrastructure-active-directory-nsclient-05-restapi.md @@ -300,7 +300,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-3com-snmp.md b/pp/integrations/plugin-packs/procedures/network-3com-snmp.md index 7663d650c07e..3c0d6f15946b 100644 --- a/pp/integrations/plugin-packs/procedures/network-3com-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-3com-snmp.md @@ -286,7 +286,7 @@ yum install centreon-plugin-Network-3com-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -373,7 +373,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -475,9 +475,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-acmepacket-snmp.md b/pp/integrations/plugin-packs/procedures/network-acmepacket-snmp.md index 72560a285cab..0116f8466e5a 100644 --- a/pp/integrations/plugin-packs/procedures/network-acmepacket-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-acmepacket-snmp.md @@ -348,8 +348,8 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -461,7 +461,7 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | Macro | Description | Default value | Mandatory | |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| | FILTERNAME | Filter by SIP name (can be a regexp) | | | -| STATUS | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %{status} | | | +| STATUS | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %\{status\} | | | | WARNINGASR | Warning threshold | | | | CRITICALASR | Critical threshold | | | | WARNINGINSESSIONSRATE | Warning threshold | | | @@ -470,7 +470,7 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALLATENCY | Critical threshold | | | | WARNINGOUTSESSIONSRATE | Warning threshold | | | | CRITICALOUTSESSIONSRATE | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -490,8 +490,8 @@ yum install centreon-plugin-Network-Acmepacket-Snmp | CRITICALLICENSEUSAGE | Critical threshold | | | | WARNINGMEMORYUSAGE | Warning threshold | | | | CRITICALMEMORYUSAGE | Critical threshold | | | -| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{replication\_state} | %{replication\_state} =~ /outOfService/i | | -| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{replication\_state} | | | +| CRITICALREPLICATIONSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{replication_state\} | %\{replication_state\} =~ /outOfService/i | | +| WARNINGREPLICATIONSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{replication_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -514,7 +514,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} =~ /outOfService|constraintsViolation|inServiceTimedOut/i' \ + --critical-status='%\{status\} =~ /outOfService|constraintsViolation|inServiceTimedOut/i' \ --warning-in-sessions-rate='' \ --critical-in-sessions-rate='' \ --warning-out-sessions-rate='' \ @@ -588,7 +588,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -683,9 +683,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -786,8 +786,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i'). You can use the following variables: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: -). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /outOfService\|constraintsViolation\|inServiceTimedOut/i'). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'in-sessions-rate', 'out-sessions-rate', 'latency', 'asr'. | | --critical-* | Critical threshold. Can be: 'in-sessions-rate', 'out-sessions-rate', 'latency', 'asr'. | | --filter-name | Filter by SIP name (can be a regexp). | @@ -798,8 +798,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | -| --warning-replication-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{replication\_state} | -| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%{replication\_state} =~ /outOfService/i'). You can use the following variables: %{replication\_state} | +| --warning-replication-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{replication_state\} | +| --critical-replication-status | Define the conditions to match for the status to be CRITICAL (default: '%\{replication_state\} =~ /outOfService/i'). You can use the following variables: %\{replication_state\} | | --warning-* | Warning threshold. Can be: 'license-usage' (%), 'memory-usage' (%), 'cpu-load' (%), 'health-score' (%), 'current-sessions', 'current-calls'. | | --critical-* | Critical threshold. Can be: 'license-usage' (%), 'memory-usage' (%), 'cpu-load' (%), 'health-score' (%), 'current-sessions', 'current-calls'. | diff --git a/pp/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md b/pp/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md index 7b90b34159a0..6e3dc33bb96d 100644 --- a/pp/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-adva-fsp150-snmp.md @@ -216,8 +216,8 @@ yum install centreon-plugin-Network-Adva-Fsp150-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: {description}, %{object}, %{severity}, %{type}, %{label}, %{since} | %{severity} eq "serviceAffecting" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{label}, %{since} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} eq "serviceAffecting" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -248,8 +248,8 @@ yum install centreon-plugin-Network-Adva-Fsp150-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --use-new-perfdata --verbose --no-skipped-counters | | @@ -283,7 +283,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{severity} eq "serviceAffecting"' \ + --critical-status='%\{severity\} eq "serviceAffecting"' \ --verbose ``` @@ -343,7 +343,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -409,8 +409,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{label}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} eq "serviceAffecting"'). You can use the following variables: {description}, %{object}, %{severity}, %{type}, %{label}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} eq "serviceAffecting"'). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | @@ -449,9 +449,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md b/pp/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md index f3e3535030fb..80ce52c63d4f 100644 --- a/pp/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-adva-fsp3000-snmp.md @@ -236,8 +236,8 @@ yum install centreon-plugin-Network-Adva-Fsp3000-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning\|minor/i') You can use the following variables: %{severity}, %{type}, %{label}, %{since} | %{severity} =~ /warning\|minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{type}, %{label}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning\|minor/i') You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} =~ /warning\|minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -260,8 +260,8 @@ yum install centreon-plugin-Network-Adva-Fsp3000-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALOPERDOWN | Thresholds | | | @@ -334,7 +334,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-optical \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-traffic-in='' \ --critical-traffic-in='' \ --warning-traffic-out='' \ @@ -419,7 +419,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -485,8 +485,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /warning\|minor/i') You can use the following variables: %{severity}, %{type}, %{label}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{type}, %{label}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /warning\|minor/i') You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{type\}, %\{label\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | @@ -510,9 +510,9 @@ All available options for each service template are listed below: | --add-status | Check interface status. | | --add-traffic | Check interface traffic. | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'laser-temp', 'input-power', 'output-power', 'traffic-in', 'traffic-out'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --interface | Set the interface (number expected) example: 1,2,... (empty means 'check all interfaces'). | diff --git a/pp/integrations/plugin-packs/procedures/network-aerohive-snmp.md b/pp/integrations/plugin-packs/procedures/network-aerohive-snmp.md index 71f2a3c3c63f..2dc283b9fe29 100644 --- a/pp/integrations/plugin-packs/procedures/network-aerohive-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-aerohive-snmp.md @@ -226,7 +226,7 @@ yum install centreon-plugin-Network-Aerohive-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -309,7 +309,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -393,9 +393,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-allied-snmp.md b/pp/integrations/plugin-packs/procedures/network-allied-snmp.md index b81506385e90..9fef680645b1 100644 --- a/pp/integrations/plugin-packs/procedures/network-allied-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-allied-snmp.md @@ -267,8 +267,8 @@ yum install centreon-plugin-Network-Allied-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -356,7 +356,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -449,9 +449,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md b/pp/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md index eb69f5342ccf..b3c734cbfba9 100644 --- a/pp/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-alvarion-breezeaccess-snmp.md @@ -246,8 +246,8 @@ yum install centreon-plugin-Network-Alvarion-Breezeaccess-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -361,7 +361,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -435,9 +435,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md b/pp/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md index cdecf1e40486..eb00eec8fb95 100644 --- a/pp/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-aruba-aoscx-snmp.md @@ -290,8 +290,8 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose --no-skipped-counters | | @@ -311,14 +311,14 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp |:------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| | WARNINGCPUUTILIZATION | Thresholds | | | | CRITICALCPUUTILIZATION | Thresholds | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i'). You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | %{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i'). You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | | | | WARNINGMEMBERSTOTAL | Thresholds | | | | CRITICALMEMBERSTOTAL | Thresholds | | | | WARNINGMEMORYUSAGEPRCT | Thresholds | | | | CRITICALMEMORYUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /no\_split/i'). You can use the following variables: %{status} | %{status} !~ /no\_split/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /no\_split/i'). You can use the following variables: %\{status\} | %\{status\} !~ /no\_split/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -326,20 +326,20 @@ yum install centreon-plugin-Network-Aruba-Aoscx-Snmp | Macro | Description | Default value | Mandatory | |:----------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------|:-----------:| -| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{config\_sync} | | | -| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{config\_sync} | | | +| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{config_sync\} | | | +| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{config_sync\} | | | | WARNINGISLPACKETSIN | Thresholds | | | | CRITICALISLPACKETSIN | Thresholds | | | | WARNINGISLPACKETSOUT | Thresholds | | | | CRITICALISLPACKETSOUT | Thresholds | | | -| CRITICALISLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{isl\_status} =~ /outSync/'). You can use the following variables: %{isl\_status} | %{isl\_status} =~ /outSync/ | | -| WARNINGISLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{isl\_status} | | | +| CRITICALISLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{isl_status\} =~ /outSync/'). You can use the following variables: %\{isl_status\} | %\{isl_status\} =~ /outSync/ | | +| WARNINGISLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{isl_status\} | | | | WARNINGKEEPALIVEPACKETSIN | Thresholds | | | | CRITICALKEEPALIVEPACKETSIN | Thresholds | | | | WARNINGKEEPALIVEPACKETSOUT | Thresholds | | | | CRITICALKEEPALIVEPACKETSOUT | Thresholds | | | -| CRITICALKEEPALIVESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{keepalive\_status} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %{keepalive\_status} | %{keepalive\_status} =~ /outofSyncEstablished\|failed/ | | -| WARNINGKEEPALIVESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{keepalive\_status} | | | +| CRITICALKEEPALIVESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{keepalive_status\} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %\{keepalive_status\} | %\{keepalive_status\} =~ /outofSyncEstablished\|failed/ | | +| WARNINGKEEPALIVESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{keepalive_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -437,7 +437,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -531,9 +531,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -579,12 +579,12 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /no\_split/i'). You can use the following variables: %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast} \|\| %{status} !~ /ready\|booting/i'). You can use the following variables: %{status}, %{role}, %{roleLast}, %{id} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /no\_split/i'). You can use the following variables: %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} !~ /ready\|booting/i'). You can use the following variables: %\{status\}, %\{role\}, %\{roleLast\}, %\{id\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total', 'memory-usage-prct', 'cpu-utilization'. | @@ -604,15 +604,15 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{config\_sync} | -| --warning-device-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{config\_sync} | -| --critical-device-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{config\_sync} | -| --unknown-isl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{isl\_status} | -| --warning-isl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{isl\_status} | -| --critical-isl-status | Define the conditions to match for the status to be CRITICAL (Default: '%{isl\_status} =~ /outSync/'). You can use the following variables: %{isl\_status} | -| --unknown-keepalive-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{keepalive\_status} | -| --warning-keepalive-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{keepalive\_status} | -| --critical-keepalive-status | Define the conditions to match for the status to be CRITICAL (Default: '%{keepalive\_status} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %{keepalive\_status} | +| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{config_sync\} | +| --warning-device-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{config_sync\} | +| --critical-device-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{config_sync\} | +| --unknown-isl-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{isl_status\} | +| --warning-isl-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{isl_status\} | +| --critical-isl-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{isl_status\} =~ /outSync/'). You can use the following variables: %\{isl_status\} | +| --unknown-keepalive-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{keepalive_status\} | +| --warning-keepalive-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{keepalive_status\} | +| --critical-keepalive-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{keepalive_status\} =~ /outofSyncEstablished\|failed/'). You can use the following variables: %\{keepalive_status\} | | --warning-* --critical-* | Thresholds. Can be: 'isl-packets-in', 'isl-packets-out', 'keepalive-packets-in', 'keepalive-packets-out'. | diff --git a/pp/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md b/pp/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md index 4597022f6a58..90aac016cb8a 100644 --- a/pp/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-aruba-cppm-snmp.md @@ -309,8 +309,8 @@ yum install centreon-plugin-Network-Aruba-Cppm-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -468,7 +468,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -561,9 +561,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | Mode | diff --git a/pp/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md b/pp/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md index 6ae1a6e16a47..a5974c64a423 100644 --- a/pp/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-aruba-instant-snmp.md @@ -209,8 +209,8 @@ yum install centreon-plugin-Network-Aruba-Instant-Snmp | CRITICALMEMUSAGEFREE | Thresholds | | | | WARNINGMEMUSAGEPRCT | Thresholds | | | | CRITICALMEMUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -219,8 +219,8 @@ yum install centreon-plugin-Network-Aruba-Instant-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter SSID name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /enable/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /enable/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /enable/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /enable/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -243,7 +243,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /up/i' \ + --critical-status='%\{status\} !~ /up/i' \ --warning-cpu='' \ --critical-cpu='' \ --warning-clients='' \ @@ -308,7 +308,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -364,8 +364,8 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^cpu$' | | --filter-name | Filter access point name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-ap', 'cpu', 'clients', 'mem-usage' (B), 'mem-usage-free' (B), 'mem-usage-prct' (%). | @@ -374,8 +374,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter SSID name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /enable/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /enable/i'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md b/pp/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md index 77e2d3a45a44..09720fc13bbe 100644 --- a/pp/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-aruba-orchestrator-restapi.md @@ -194,8 +194,8 @@ yum install centreon-plugin-Network-Aruba-Orchestrator-Restapi | CRITICALSEVERITYMAJOR | Thresholds | | | | WARNINGSEVERITYMINOR | Thresholds | | | | CRITICALSEVERITYMINOR | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | %{severity} =~ /minor\|warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | %{severity} =~ /major\|critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /minor\|warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | %\{severity\} =~ /major\|critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -203,13 +203,13 @@ yum install centreon-plugin-Network-Aruba-Orchestrator-Restapi | Macro | Description | Default value | Mandatory | |:---------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{hostname} | %{state} =~ /unknown\|unreachable/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{hostname\} | %\{state\} =~ /unknown\|unreachable/i | | | FILTERHOSTNAME | Filter appliances by hostname | | | | FILTERGROUP | Filter appliances by group | | | | WARNINGAPPLIANCESDETECTED | Thresholds | | | | CRITICALAPPLIANCESDETECTED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{hostname} | %{state} =~ /unsupportedVersion\|outOfSynchronization/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{hostname} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{hostname\} | %\{state\} =~ /unsupportedVersion\|outOfSynchronization/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{hostname\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -233,8 +233,8 @@ is able to monitor a resource using a command like this one (replace the sample --access-token='XXXX' \ --filter-hostname='' \ --filter-group='' \ - --unknown-status='%{state} =~ /unknown|unreachable/i' \ - --warning-status='%{state} =~ /unsupportedVersion|outOfSynchronization/i' \ + --unknown-status='%\{state\} =~ /unknown|unreachable/i' \ + --warning-status='%\{state\} =~ /unsupportedVersion|outOfSynchronization/i' \ --critical-status='' \ --warning-appliances-detected='' \ --critical-appliances-detected='' \ @@ -298,7 +298,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -341,8 +341,8 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-hostname | Filter alarms by hostname (can be a regexp). | | --timezone | Set timezone for creation time (default is 'UTC'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/i'). You can use the following variables: %{severity}, %{hostname}, %{name}, %{timeraised} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/i'). You can use the following variables: %\{severity\}, %\{hostname\}, %\{name\}, %\{timeraised\} | | --warning-* --critical-* | Thresholds. Can be: 'severity-minor', 'severity-warning', 'severity-major', 'severity-critical'. | @@ -353,9 +353,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-hostname | Filter appliances by hostname. | | --filter-group | Filter appliances by group. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{state} =~ /unknown\|unreachable/i'). You can use the following variables: %{state}, %{hostname} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} =~ /unsupportedVersion\|outOfSynchronization/i'). You can use the following variables: %{state}, %{hostname} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{hostname} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{state\} =~ /unknown\|unreachable/i'). You can use the following variables: %\{state\}, %\{hostname\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} =~ /unsupportedVersion\|outOfSynchronization/i'). You can use the following variables: %\{state\}, %\{hostname\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{hostname\} | | --warning-* --critical-* | Thresholds. Can be: 'appliances-detected'. | diff --git a/pp/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md b/pp/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md index 16f731c8c10a..e9929339fd12 100644 --- a/pp/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-athonet-epc-snmp.md @@ -336,12 +336,12 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp |:------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTERNAME | Filter interfaces by name (can be a regexp) | | | | FILTEROWNER | Filter interfaces by owner (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{owner} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{owner} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | -| CRITICALTRANSPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | %{transport\_status} =~ /down/i | | -| WARNINGTRANSPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | | | +| CRITICALTRANSPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | %\{transport_status\} =~ /down/i | | +| WARNINGTRANSPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -352,8 +352,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | FILTERNAME | Filter interfaces by name (can be a regexp) | | | | FILTERLOCALADDRESS | Filter interfaces by local address (can be a regexp) | | | | FILTERPEERADDRESS | Filter interfaces by peer address (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -366,8 +366,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | FILTESOURCEADDRESS | Filter interfaces by source address (can be a regexp) | | | | FILTERDESTINATIONADDRESS | Filter interfaces by destination address (can be a regexp) | | | | FILTERTYPE | Filter interfaces by type (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -398,8 +398,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | CRITICALREQUESTSUECONTEXTRELEASETOTAL | Thresholds | | | | WARNINGSESSIONSACTIVE | Thresholds | | | | CRITICALSESSIONSACTIVE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | %{sctp\_status} =~ /down/i \|\| %{s1ap\_status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | %\{sctp_status\} =~ /down/i \|\| %\{s1ap_status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -438,8 +438,8 @@ yum install centreon-plugin-Network-Athonet-Epc-Snmp | CRITICALLICENSEUSIMUSAGE | Thresholds | | | | WARNINGLICENSEUSIMUSAGEPRCT | Thresholds | | | | CRITICALLICENSEUSIMUSAGEPRCT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status} | %{status} =~ /expired\|invalid/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\} | %\{status\} =~ /expired\|invalid/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -567,7 +567,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -665,12 +665,12 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='transport' | | --filter-name | Filter interfaces by name (can be a regexp). | | --filter-owner | Filter interfaces by owner (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{owner} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{owner} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{name}, %{owner} | -| --unknown-transport-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | -| --warning-transport-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | -| --critical-transport-status | Define the conditions to match for the status to be CRITICAL (default: '%{transport\_status} =~ /down/i'). You can use the following variables: %{transport\_status}, %{transport\_type}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{name\}, %\{owner\} | +| --unknown-transport-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | +| --warning-transport-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | +| --critical-transport-status | Define the conditions to match for the status to be CRITICAL (default: '%\{transport_status\} =~ /down/i'). You can use the following variables: %\{transport_status\}, %\{transport_type\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -681,9 +681,9 @@ All available options for each service template are listed below: | --filter-name | Filter interfaces by name (can be a regexp). | | --filter-local-address | Filter interfaces by local address (can be a regexp). | | --filter-peer-address | Filter interfaces by peer address (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{local\_address}, %{peer\_address}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{local_address\}, %\{peer_address\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -694,9 +694,9 @@ All available options for each service template are listed below: | --filter-source-address | Filter interfaces by source address (can be a regexp). | | --filter-destination-address | Filter interfaces by destination address (can be a regexp). | | --filter-type | Filter interfaces by type (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{source\_address}, %{destination\_address} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{source_address\}, %\{destination_address\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -718,9 +718,9 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='users' | | --filter-name | Filter interfaces by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{sctp\_status} =~ /down/i \|\| %{s1ap\_status} =~ /down/i'). You can use the following variables: %{sctp\_status}, %{s1ap\_status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{sctp_status\} =~ /down/i \|\| %\{s1ap_status\} =~ /down/i'). You can use the following variables: %\{sctp_status\}, %\{s1ap_status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'users-connected', 'users-idle', 'sessions-active', 'traffic-in', 'traffic-out', 'requests-ue-context-release-total', 'requests-ue-context-release-radio-lost', 'requests-attach-success', 'requests-attach-success-prct', 'requests-pdn-context-activation', 'requests-pdn-context-activation-prct', 'requests-pdn-context-rej-insufres', 'requests-pdn-context-rej-noapn', 'requests-pdn-context-rej-nosub'. | @@ -729,8 +729,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='users' | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /expired\|invalid/i'). Can use special variables like: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /expired\|invalid/i'). Can use special variables like: %\{status\} | | --unit | Select the time unit for the expiration threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | | --warning-* --critical-* | Thresholds. Can be: 'expires', 'license-users-usage', 'license-users-free', 'license-users-usage-prct', 'license-sessions-usage', 'license-sessions-free', 'license-sessions-usage-prct', 'license-usim-usage', 'license-usim-free', 'license-usim-usage-prct'. | diff --git a/pp/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md b/pp/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md index 49c1d93c4884..efa18ef4b1c7 100644 --- a/pp/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-atto-fibrebridge-snmp.md @@ -196,8 +196,8 @@ yum install centreon-plugin-Network-Atto-Fibrebridge-Snmp | CRITICALINVALIDCRC | Thresholds | | | | WARNINGSIGNALLOSS | Thresholds | | | | CRITICALSIGNALLOSS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin}, %{status}, %{display} | %{admin} =~ /enabled/ and %{status} !~ /online/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | %\{admin\} =~ /enabled/ and %\{status\} !~ /online/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -289,7 +289,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -358,8 +358,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'invalid-crc', 'signal-loss'. | | --filter-name | Filter name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{admin}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin} =~ /enabled/ and %{status} !~ /online/'). You can use the following variables: %{admin}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin\} =~ /enabled/ and %\{status\} !~ /online/'). You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/network-audiocodes-snmp.md b/pp/integrations/plugin-packs/procedures/network-audiocodes-snmp.md index ddeae1dce6f5..8be2f5aa7152 100644 --- a/pp/integrations/plugin-packs/procedures/network-audiocodes-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-audiocodes-snmp.md @@ -309,8 +309,8 @@ yum install centreon-plugin-Network-Audiocodes-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -371,8 +371,8 @@ yum install centreon-plugin-Network-Audiocodes-Snmp | CRITICALCOUNTCALLS | Thresholds | | | | WARNINGMAXCALLS | Thresholds | | | | CRITICALMAXCALLS | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | %{state} =~ /activated/ and %{alarm} !~ /greenActive/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | %\{state\} =~ /activated/ and %\{alarm\} !~ /greenActive/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -452,7 +452,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -545,9 +545,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -615,8 +615,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | | --filter-name | Filter by name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /activated/ and %{alarm} !~ /greenActive/i'). You can use the following variables: %{display}, %{alarm}, %{dchannel}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /activated/ and %\{alarm\} !~ /greenActive/i'). You can use the following variables: %\{display\}, %\{alarm\}, %\{dchannel\}, %\{state\} | | --warning-* --critical-* | Thresholds. Can be: 'avg-calls', 'max-calls', 'count-calls'. | diff --git a/pp/integrations/plugin-packs/procedures/network-backbox-restapi.md b/pp/integrations/plugin-packs/procedures/network-backbox-restapi.md index 935461ef4b6b..88dded361283 100644 --- a/pp/integrations/plugin-packs/procedures/network-backbox-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-backbox-restapi.md @@ -322,7 +322,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md b/pp/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md index 93121705130b..bf140386ccb7 100644 --- a/pp/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-barracuda-bma-snmp.md @@ -318,7 +318,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md b/pp/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md index ea82c4bced69..23407173a9bc 100644 --- a/pp/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-barracuda-cloudgen-snmp.md @@ -320,8 +320,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | IFLTERNAME | Filter by service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /^started$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^started$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -410,8 +410,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -464,8 +464,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | IFLTERNAME | Filter by service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} !~ /^started$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^started$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -497,8 +497,8 @@ yum install centreon-plugin-Network-Barracuda-Cloudgen-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter by VPN name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /^down$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /^down$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -593,7 +593,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -647,8 +647,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^started$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^started$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by service name (can be a regexp). | @@ -719,9 +719,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -769,8 +769,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^started$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^started$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by service name (can be a regexp). | @@ -841,8 +841,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^down$/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^down$/i'). You can use the following variables: %\{status\}, %\{display\} | | --filter-name | Filter by VPN name (can be a regexp). | diff --git a/pp/integrations/plugin-packs/procedures/network-beeware-snmp.md b/pp/integrations/plugin-packs/procedures/network-beeware-snmp.md index ba14a072bb3b..fd7db81d48e2 100644 --- a/pp/integrations/plugin-packs/procedures/network-beeware-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-beeware-snmp.md @@ -200,8 +200,8 @@ yum install centreon-plugin-Network-Beeware-Snmp | CRITICALMEMORY | Critical threshold | | | | WARNINGNBCHILDS | Warning threshold | | | | CRITICALNBCHILDS | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{status} | %{status} !~ /running/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{status\} | %\{status\} !~ /running/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -224,7 +224,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --filter-name='' \ --warning-status='' \ - --critical-status='%{status} !~ /running/i' \ + --critical-status='%\{status\} !~ /running/i' \ --warning-memory='' \ --critical-memory='' \ --warning-cpu='' \ @@ -287,7 +287,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -333,8 +333,8 @@ All available options for each service template are listed below: | --snmp-tls-trust-cert | A trusted CA certificate used to verify a remote host's certificate. If you use this option, you must also define --snmp-tls-their-hostname. | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^cpu\|memory$' | | --filter-name | Filter reverse proxy (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /running/i'). You can use the following variables: %{display}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /running/i'). You can use the following variables: %\{display\}, %\{status\} | | --warning-* | Warning threshold. Can be: 'cpu', 'memory' (B), 'nbchilds'. | | --critical-* | Critical threshold. Can be: 'cpu', 'memory' (B), 'nbchilds'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md b/pp/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md index 63fae3fc9b0d..ccc862c03129 100644 --- a/pp/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cambium-cnpilot-snmp.md @@ -260,8 +260,8 @@ yum install centreon-plugin-Network-Cambium-cnPilot-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up|dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -283,8 +283,8 @@ yum install centreon-plugin-Network-Cambium-cnPilot-Snmp | CRITICALCLIENTS | | | | | WARNINGINTERFERENCE | Thresholds | | | | CRITICALINTERFERENCE | Thresholds | | | -| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %{status}, %{name} | | | -| CRITICALSTATUS | Set critical threshold for status (Default: '%{status} eq "expired"'). Can used special variables like: %{status}, %{name} | | | +| WARNINGSTATUS | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Set critical threshold for status (Default: '%\{status\} eq "expired"'). Can used special variables like: %\{status\}, %\{name\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -315,7 +315,7 @@ is able to monitor a server using a command like this one (replace the sample va --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -384,7 +384,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | Output | | --debug | Display debug messages. | Output | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | Output | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | Output | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | Output | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Change storage free perfdata in used: --change-perfdata=free,used,invert() Change storage free perfdata in used: --change-perfdata=used,free,invert() Scale traffic values automaticaly: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | Output | | --extend-perfdata-group | Extend perfdata from multiple perfdatas (methods in target are: min, max, average, sum) Syntax: --extend-perfdata-group=searchlabel,newlabel,target\[,\[newuom\],\[m in\],\[max\]\] Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | Output | @@ -438,8 +438,8 @@ All modes specific options are listed here: | Option | Description | Type | |:-----------------------------|:------------------------------------------------------------------------------------------|:-----| | --filter-ap | Filter on one or several AP. | Mode | -| --warning-connection-status | Set warning threshold for status. Can used special variables like: %{status}, %{name} | Mode | -| --critical-connection-status | Set critical threshold for status. Can used special variables like: %{status}, %{name} | Mode | +| --warning-connection-status | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | +| --critical-connection-status | Set critical threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | @@ -475,9 +475,9 @@ All modes specific options are listed here: | --add-cast | Check interface cast. | Mode | | --add-speed | Check interface speed. | Mode | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | Mode | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | Mode | -| --warning-status | Set warning threshold for status. Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). Can used special variables like: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | Mode | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | Mode | +| --warning-status | Set warning threshold for status. Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). Can used special variables like: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | Mode | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | Mode | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'counter'). | Mode | @@ -527,8 +527,8 @@ All modes specific options are listed here: | --statefile-cipher | Cipher to encrypt cache (Default: 'AES'). | Retention | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | Mode | | --filter-name | Filter interface by MACAdress | Mode | -| --warning-status | Set warning threshold for status. Can used special variables like: %{status}, %{name} | Mode | -| --critical-status | Set critical threshold for status (Default: '%{status} eq "expired"'). Can used special variables like: %{status}, %{name} | Mode | +| --warning-status | Set warning threshold for status. Can used special variables like: %\{status\}, %\{name\} | Mode | +| --critical-status | Set critical threshold for status (Default: '%\{status\} eq "expired"'). Can used special variables like: %\{status\}, %\{name\} | Mode | | --warning-* --critical-* | Thresholds. Can be: 'clients-connected', 'noise-floor', 'interference', 'traffic-in', 'traffic-out'. | Mode | diff --git a/pp/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md b/pp/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md index 07d0e1b01806..337cb0c0992d 100644 --- a/pp/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cambium-epmp-snmp.md @@ -263,8 +263,8 @@ yum install centreon-plugin-Network-Cambium-Epmp-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -272,9 +272,9 @@ yum install centreon-plugin-Network-Cambium-Epmp-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | %{status} =~ /unknown/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /validation fail\|not provided/i'). You can use the following variables: %{status} | %{status} =~ /validation fail\|not provided/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /not valid/i'). You can use the following variables: %{status} | %{status} =~ /not valid/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | %\{status\} =~ /unknown/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /validation fail\|not provided/i'). You can use the following variables: %\{status\} | %\{status\} =~ /validation fail\|not provided/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /not valid/i'). You can use the following variables: %\{status\} | %\{status\} =~ /not valid/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -310,7 +310,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -383,7 +383,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -473,9 +473,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -501,9 +501,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /validation fail\|not provided/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /not valid/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /validation fail\|not provided/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /not valid/i'). You can use the following variables: %\{status\} | diff --git a/pp/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md b/pp/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md index 3b2485b18f2d..2f68e1d24f44 100644 --- a/pp/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-chapsvision-crossing-snmp.md @@ -220,8 +220,8 @@ yum install centreon-plugin-Network-Chapsvision-Crossing-Snmp | CRITICALDATABASELASTUPDATE | Thresholds | | | | WARNINGLICENSEEXPIRES | Thresholds | | | | CRITICALLICENSEEXPIRES | Thresholds | | | -| WARNINGVERSION | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %{version}, %{name} | | | -| CRITICALVERSION | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %{version}, %{name} | | | +| WARNINGVERSION | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %\{version\}, %\{name\} | | | +| CRITICALVERSION | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %\{version\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Chapsvision-Crossing-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -354,7 +354,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -411,9 +411,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='version' | | --antivirus1-date-format | Define the date format for the first antivirus (default: '%Y/%m/%d'). | | --antivirus2-date-format | Define the date format for the second antivirus (default: '%Y/%m/%d'). | -| --unknown-version | Define the conditions the version must match for the status to be UNKNOWN. You can use the following variables: %{version}, %{name} | -| --warning-version | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %{version}, %{name} | -| --critical-version | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %{version}, %{name} | +| --unknown-version | Define the conditions the version must match for the status to be UNKNOWN. You can use the following variables: %\{version\}, %\{name\} | +| --warning-version | Define the conditions the version must match for the status to be WARNING. You can use the following variables: %\{version\}, %\{name\} | +| --critical-version | Define the conditions the version must match for the status to be CRITICAL. You can use the following variables: %\{version\}, %\{name\} | | --unit | Select the unit for the expired license threshold. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'license-expires', 'database-last-update'. | @@ -442,9 +442,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md index d4d83a97b571..468bfa8564f6 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-apic-restapi.md @@ -181,8 +181,8 @@ yum install centreon-plugin-Network-Cisco-Apic-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHEALTH | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | | | -| CRITICALHEALTH | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | | | +| WARNINGHEALTH | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | | | +| CRITICALHEALTH | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -204,8 +204,8 @@ yum install centreon-plugin-Network-Cisco-Apic-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHEALTH | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | | | -| CRITICALHEALTH | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | | | +| WARNINGHEALTH | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | | | +| CRITICALHEALTH | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -290,7 +290,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -341,8 +341,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-health | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | -| --critical-health | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | +| --warning-health | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | +| --critical-health | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | @@ -359,8 +359,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-tenant | Regexp filter on the tenant name | -| --warning-health | Set warning for the health level You can use the following variables: %{current}, %{previous}. example: --warning-health='%{previous} \< %{current}' | -| --critical-health | Set critical for the health level You can use the following variables: %{current}, %{previous}. example: --critical-health='%{current} \< 98' | +| --warning-health | Set warning for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --warning-health='%\{previous\} \< %\{current\}' | +| --critical-health | Set critical for the health level You can use the following variables: %\{current\}, %\{previous\}. example: --critical-health='%\{current\} \< 98' | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md index 97f95cdbff7a..18a431da28ee 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-snmp.md @@ -235,8 +235,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | CRITICALPHONESREJECTED | Thresholds | | | | WARNINGPHONESUNREGISTERED | Thresholds | | | | CRITICALPHONESUNREGISTERED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/'). You can use the following variables: %{status}, %{display} | %{status} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -244,8 +244,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALPARTIALLYREGISTERED | Warning threshold | | | | CRITICALTOTALPARTIALLYREGISTERED | Critical threshold | | | | WARNINGTOTALREGISTERED | Warning threshold | | | @@ -263,8 +263,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALPARTIALLYREGISTERED | | | | | CRITICALTOTALPARTIALLYREGISTERED | Critical threshold | | | | WARNINGTOTALREGISTERED | | | | @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Cisco-Callmanager-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{name}, %{description} | %{status} !~ /^registered/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{description} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{name\}, %\{description\} | %\{status\} !~ /^registered/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{description\} | | | | WARNINGTOTALPARTIALLYREGISTERED | Thresholds | | | | CRITICALTOTALPARTIALLYREGISTERED | Thresholds | | | | WARNINGTOTALREGISTERED | Thresholds | | | @@ -315,7 +315,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-status='' \ - --critical-status='%{status} !~ /^registered/' \ + --critical-status='%\{status\} !~ /^registered/' \ --warning-total-registered='' \ --critical-total-registered='' \ --warning-total-unregistered='' \ @@ -383,7 +383,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -438,8 +438,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='phone' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /up/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'phones-registered', 'phones-unregistered', 'phones-rejected', 'gateways-registered', 'gateways-unregistered', 'gateways-rejected', 'mediadevices-registered', 'mediadevices-unregistered', 'mediadevices-rejected'. | @@ -448,8 +448,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. | | --critical-* | Critical threshold. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | @@ -459,8 +459,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. | | --critical-* | Critical threshold. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | @@ -472,8 +472,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter phone by name (can be a regexp). | | --filter-description | Filter phone by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{description} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /^registered/'). You can use the following variables: %{status}, %{name}, %{description} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{description\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /^registered/'). You can use the following variables: %\{status\}, %\{name\}, %\{description\} | | --warning-* --critical-* | Thresholds. Can be: 'total-registered', 'total-unregistered', 'total-rejected', 'total-unknown', 'total-partiallyregistered'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md b/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md index 5cfc90ea5991..c5a8f9306453 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-callmanager-sxml.md @@ -278,7 +278,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md index 3b73f7e6881f..f27c4b93f746 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-esa-restapi.md @@ -278,7 +278,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md index 250d513718cd..5e2623caf8c0 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-esa-xmlapi.md @@ -177,7 +177,7 @@ yum install centreon-plugin-Network-Cisco-Esa-Xmlapi | Macro | Description | Default value | Mandatory | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| -| UNKNOWNHTTPSTATUS | Threshold unknown for http response code (default: '%{http_code} < 200 or %{http_code} >= 300') | | | +| UNKNOWNHTTPSTATUS | Threshold unknown for http response code (default: '%\{http_code\} < 200 or %\{http_code\} >= 300') | | | | WARNINGCONNECTIONSIN | Warning threshold for 'connections-in' | | | | CRITICALCONNECTIONSIN | Critical threshold for 'connections-in' | | | | WARNINGCONNECTIONSOUT | Warning threshold for 'connections-out' | | | @@ -204,8 +204,8 @@ yum install centreon-plugin-Network-Cisco-Esa-Xmlapi | CRITICALQUEUEDISK | Critical threshold for 'queuedisk' (%) | | | | WARNINGRESOURCECONSERVATION | Warning threshold for 'resource-conservation' | | | | CRITICALRESOURCECONSERVATION | Critical threshold for 'resource-conservation' | | | -| CRITICALSYSTEMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system_status} | %{system\_status} !~ /online/i | | -| WARNINGSYSTEMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{system_status} | | | +| CRITICALSYSTEMSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\} | %\{system_status\} !~ /online/i | | +| WARNINGSYSTEMSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{system_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -232,7 +232,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-http-status='' \ --critical-http-status='' \ --warning-system-status='' \ - --critical-system-status='%{system_status} !~ /online/i' \ + --critical-system-status='%\{system_status\} !~ /online/i' \ --warning-memory='' \ --critical-memory='' \ --warning-cpu-total='' \ @@ -312,7 +312,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -357,11 +357,11 @@ All available options for each service template are listed below: | --username | Specify the username for authentication | | --password | Specify the password for authentication | | --timeout | Threshold for HTTP timeout | -| --unknown-http-status | Threshold unknown for http response code (default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-http-status | Threshold unknown for http response code (default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-http-status | Warning threshold for http response code | | --critical-http-status | Critical threshold for http response code | -| --warning-system-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{system\_status} | -| --critical-system-status | Define the conditions to match for the status to be CRITICAL (default: '%{system\_status} !~ /online/i'). You can use the following variables: %{system\_status} | +| --warning-system-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{system_status\} | +| --critical-system-status | Define the conditions to match for the status to be CRITICAL (default: '%\{system_status\} !~ /online/i'). You can use the following variables: %\{system_status\} | | --warning-* --critical-* | Warning threshold. Can be: 'memory' (%), 'cpu-total' (%), 'diskio' (%), 'log' (%), 'resource-conservation', 'connections-in', 'connections-out', 'queue-active-recipients', 'messages-quarantine', 'messages-workqueue', 'queuedisk' (%), 'messages-received'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md index bdd3cfb9f24f..a2144cae7428 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-firepower-fmc-restapi.md @@ -171,7 +171,7 @@ yum install centreon-plugin-Network-Cisco-Firepower-Fmc-Restapi |:----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | FILTERDOMAINNAME | Filter devices by domain name (can be a regexp) | | | | FILTERDEVICENAME | Filter devices by name (can be a regexp) | | | -| UNKNOWNDEVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNDEVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGDEVICESSTATUSBLACK | Warning thresholds for 'devices-status-black' | | | | CRITICALDEVICESSTATUSBLACK | Critical thresholds for 'devices-status-black' | | | | WARNINGDEVICESSTATUSBLUE | Warning thresholds for 'devices-status-blue' | | | @@ -182,8 +182,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Fmc-Restapi | CRITICALDEVICESSTATUSRED | Critical thresholds for 'devices-status-red' | | | | WARNINGDEVICESSTATUSYELLOW | Warning thresholds for 'devices-status-yellow' | | | | CRITICALDEVICESSTATUSYELLOW | Critical thresholds for 'devices-status-yellow' | | | -| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/i | | -| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /red\|black/i | | +| WARNINGDEVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/i | | +| CRITICALDEVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red\|black/i | | | WARNINGDEVICESTOTAL | Warning thresholds for 'devices-total' | | | | CRITICALDEVICESTOTAL | Critical thresholds for 'devices-total' | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -223,8 +223,8 @@ is able to monitor a resource using a command like this one (replace the sample --warning-devices-status-yellow='' \ --critical-devices-status-yellow='' \ --unknown-device-status='' \ - --warning-device-status='%{status} =~ /yellow/i' \ - --critical-device-status='%{status} =~ /red|black/i' \ + --warning-device-status='%\{status\} =~ /yellow/i' \ + --critical-device-status='%\{status\} =~ /red|black/i' \ --verbose ``` @@ -289,7 +289,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -335,9 +335,9 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-domain-name | Filter devices by domain name (can be a regexp). | | --filter-device-name | Filter devices by name (can be a regexp). | -| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-device-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /yellow/i'). You can use the following variables: %{status}, %{name} | -| --critical-device-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /red\|black/i'). You can use the following variables: %{status}, %{name} | +| --unknown-device-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /yellow/i'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /red\|black/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'devices-total', 'devices-status-green', 'devices-status-black', 'devices-status-blue', 'devices-status-red', 'devices-status-yellow'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md index 266cee1b9dac..4dbb560898c1 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-firepower-snmp.md @@ -288,8 +288,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Snmp | CRITICALFAULTSMINOR | Critical threshold for 'faults-info' | | | | WARNINGFAULTSTOTAL | Warning threshold for 'faults-total' | | | | CRITICALFAULTSTOTAL | Critical threshold for 'faults-total' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{acknowledged}, %{since} | %{severity} =~ /minor\|warning/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{since} | %{severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{acknowledged\}, %\{since\} | %\{severity\} =~ /minor\|warning/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{since\} | %\{severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -320,8 +320,8 @@ yum install centreon-plugin-Network-Cisco-Firepower-Snmp | CRITICALOUTERROR | Critical threshold for 'out-error' | | | | WARNINGOUTTRAFFIC | Warning threshold for 'out-traffic' | | | | CRITICALOUTTRAFFIC | Critical threshold for 'out-traffic' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -421,7 +421,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -495,8 +495,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/). You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{acknowledged}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /major\|critical/'). You can use the following variables: %{description}, %{object}, %{severity}, %{type}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{acknowledged\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /major\|critical/'). You can use the following variables: %\{description\}, %\{object\}, %\{severity\}, %\{type\}, %\{since\} | | --timezone | Timezone options (the date from the equipment overload that option). Default is 'GMT'. | | --memory | Only check new alarms. | | --warning-* --critical-* | Thresholds. Can be: 'faults-total', 'faults-critical', 'faults-major', 'faults-warning', 'faults-minor', 'faults-info'. | @@ -538,9 +538,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md index 972867309fd4..70b480dec318 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-ironport-snmp.md @@ -276,7 +276,7 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | | WARNINGDNSREQUESTSOUTSTANDING | Warning threshold | | | | CRITICALDNSREQUESTSOUTSTANDING | Warning threshold | | | | WARNINGDNSREQUESTSPENDING | Warning threshold | | | @@ -285,8 +285,8 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | CRITICALFDOPENED | Warning threshold | | | | WARNINGMESSAGESWORKQUEUE | Warning threshold | | | | CRITICALMESSAGESWORKQUEUE | Warning threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{resource\_conservation} =~ /memoryShortage\|queueSpaceShortage/i \|\| %{queue\_status} =~ /queueSpaceShortage/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{resource\_conservation} =~ /queueFull/i \|\| %{queue\_status} =~ /queueFull/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{resource_conservation\} =~ /memoryShortage\|queueSpaceShortage/i \|\| %\{queue_status\} =~ /queueSpaceShortage/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{resource_conservation\} =~ /queueFull/i \|\| %\{queue_status\} =~ /queueFull/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | | | WARNINGTHREADSMAIL | Warning threshold | | | | CRITICALTHREADSMAIL | Warning threshold | | | | WARNINGTIMEEXPIRATION | Warning threshold | | | @@ -363,7 +363,7 @@ yum install centreon-plugin-Network-Cisco-Ironport-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -452,7 +452,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -538,9 +538,9 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{queue\_status}, %{resource\_conservation} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{resource\_conservation} =~ /memoryShortage\|queueSpaceShortage/i \|\| %{queue\_status} =~ /queueSpaceShortage/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{resource\_conservation} =~ /queueFull/i \|\| %{queue\_status} =~ /queueFull/i'). You can use the following variables: %{queue\_status}, %{resource\_conservation} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{resource_conservation\} =~ /memoryShortage\|queueSpaceShortage/i \|\| %\{queue_status\} =~ /queueSpaceShortage/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{resource_conservation\} =~ /queueFull/i \|\| %\{queue_status\} =~ /queueFull/i'). You can use the following variables: %\{queue_status\}, %\{resource_conservation\} | | --warning-* --critical-* | Warning threshold. Can be: 'messages-workqueue', 'dns-requests-outstanding', 'dns-requests-pending', 'fd-opened', 'threads-mail', 'update-failures', 'time-expiration'. | @@ -596,9 +596,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md index ece97d6c4695..b394988fbe09 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-meraki-restapi.md @@ -407,18 +407,18 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | CRITICALLINKLATENCY | Thresholds | | | | WARNINGLINKLOSS | Thresholds | | | | CRITICALLINKLOSS | Thresholds | | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | | WARNINGPORTTRAFFICIN | Thresholds | | | | CRITICALPORTTRAFFICIN | Thresholds | | | | WARNINGPORTTRAFFICOUT | Thresholds | | | | CRITICALPORTTRAFFICOUT | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALALERTING | Thresholds | | | | CRITICALTOTALALERTING | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -462,18 +462,18 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | CRITICALLINKLOSS | Thresholds | | | | WARNINGLINKSINEFFECTIVE | Thresholds | | | | CRITICALLINKSINEFFECTIVE | Thresholds | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{link\_status}, %{display} | %{link\_status} =~ /failed/i | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} =~ /failed/i | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGLOAD | Thresholds | | | | CRITICALLOAD | Thresholds | | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | | | WARNINGPORTTRAFFICIN | Thresholds | | | | CRITICALPORTTRAFFICIN | Thresholds | | | | WARNINGPORTTRAFFICOUT | Thresholds | | | | CRITICALPORTTRAFFICOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /alerting/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /alerting/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALALERTING | Thresholds | | | | CRITICALTOTALALERTING | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -544,8 +544,8 @@ yum install centreon-plugin-Network-Cisco-Meraki-Restapi | FILTERORGANIZATIONID | Filter VPN tunnels by organization ID (can be a regexp) | | | | FILTERORGANIZATIONNAME | Filter VPN tunnels by organization name (can be a regexp) | | | | FILTERDEVICESERIAL | Filter VPN tunnels by device serial (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | %{status} =~ /offline/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | %\{status\} =~ /offline/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | | | | WARNINGTOTALDORMANT | Thresholds | | | | CRITICALTOTALDORMANT | Thresholds | | | | WARNINGTOTALOFFLINE | Thresholds | | | @@ -573,8 +573,8 @@ is able to monitor a resource using a command like this one (replace the sample --api-token='12345abcd6789efgh0123abcd4567efgh8901abcd' \ --proxyurl='http://proxy.mycompany:8080' \ --filter-device-name='centreon-par-training-ap' \ - --critical-status='%{status} =~ /alerting/i' \ - --critical-link-status='%{link_status} =~ /failed/i' \ + --critical-status='%\{status\} =~ /alerting/i' \ + --critical-link-status='%\{link_status\} =~ /failed/i' \ --verbose ``` @@ -649,7 +649,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -732,15 +732,15 @@ All available options for each service template are listed below: | --skip-performance | Don't monitor appliance performance score. | | --skip-connections | Don't monitor connection stats. | | --skip-traffic-disconnect-port | Skip port traffic counters if port status is disconnected. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-online-prct', 'total-offline', 'total-offline-prct', 'total-alerting', 'traffic-in', 'traffic-out', 'connections-success', 'connections-auth', 'connections-assoc', 'connections-dhcp', 'connections-dns', 'load', 'links-ineffective', 'link-latency' (ms), ''link-loss' (%), 'port-traffic-in', 'port-traffic-out'. | @@ -760,15 +760,15 @@ All available options for each service template are listed below: | --skip-performance | Don't monitor appliance performance score. | | --skip-connections | Don't monitor connection stats. | | --skip-traffic-disconnect-port | Skip port traffic counters if port status is disconnected. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /alerting/i'). You can use the following variables: %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} =~ /failed/i'). You can use the following variables: %{link\_status}, %{display} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{port\_enabled} == 1 and %{port\_status} !~ /^connected/i'). You can use the following variables: %{port\_status}, %{port\_enabled}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /alerting/i'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} =~ /failed/i'). You can use the following variables: %\{link_status\}, %\{display\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{port_enabled\} == 1 and %\{port_status\} !~ /^connected/i'). You can use the following variables: %\{port_status\}, %\{port_enabled\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-online-prct', 'total-offline', 'total-offline-prct', 'total-alerting', 'traffic-in', 'traffic-out', 'connections-success', 'connections-auth', 'connections-assoc', 'connections-dhcp', 'connections-dns', 'load', 'links-ineffective', 'link-latency' (ms), ''link-loss' (%), 'port-traffic-in', 'port-traffic-out'. | @@ -800,9 +800,9 @@ All available options for each service template are listed below: | --filter-organization-id | Filter VPN tunnels by organization ID (can be a regexp). | | --filter-organization-name | Filter VPN tunnels by organization name (can be a regexp). | | --filter-device-serial | Filter VPN tunnels by device serial (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{deviceSerial}, %{mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /offline/i'). You can use the following variables: %{status}, %{deviceSerial}, %{mode} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /offline/i'). You can use the following variables: %\{status\}, %\{deviceSerial\}, %\{mode\} | | --warning-* --critical-* | Thresholds. Can be: 'total-online', 'total-offline', 'total-dormant'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md index 084bdade5cdd..97c9218e3687 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-meraki-snmp.md @@ -295,7 +295,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -360,8 +360,8 @@ All available options for each service template are listed below: | --speed-in | Set interface speed for incoming traffic (in Mb). | | --speed-out | Set interface speed for outgoing traffic (in Mb). | | --units-traffic | Units of thresholds for the traffic (default: '%') ('%', 'b/s'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /offline/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /offline/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'total-devices', 'clients', 'in', 'out'. | | --critical-* | Critical threshold. Can be: 'total-devices', 'clients', 'in', 'out'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md index a2f3e854968c..25ab7630d80f 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-prime-restapi.md @@ -170,8 +170,8 @@ yum install centreon-plugin-Network-Cisco-Prime-Restapi | CRITICALAPCLIENTS | Critical threshold | | | | WARNINGAPLWAPPUPTIME | Warning threshold | | | | CRITICALAPLWAPPUPTIME | Critical threshold | | | -| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | %{admin\_status} =~ /enable/i && %{status} =~ /minor\|warning/i | | -| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | %{admin\_status} =~ /enable/i && %{status} =~ /major\|critical/i | | +| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | %\{admin_status\} =~ /enable/i && %\{status\} =~ /minor\|warning/i | | +| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | %\{admin_status\} =~ /enable/i && %\{status\} =~ /major\|critical/i | | | WARNINGAPUPTIME | Warning threshold | | | | CRITICALAPUPTIME | Critical threshold | | | | WARNINGCTRLAPCOUNT | Warning threshold | | | @@ -198,8 +198,8 @@ is able to monitor a resource using a command like this one (replace the sample --password='' \ --filter-ap='.*' \ --filter-controller='.*' \ - --warning-ap-status='%{admin_status} =~ /enable/i && %{status} =~ /minor|warning/i' \ - --critical-ap-status='%{admin_status} =~ /enable/i && %{status} =~ /major|critical/i' \ + --warning-ap-status='%\{admin_status\} =~ /enable/i && %\{status\} =~ /minor|warning/i' \ + --critical-ap-status='%\{admin_status\} =~ /enable/i && %\{status\} =~ /major|critical/i' \ --warning-ap-clients='' \ --critical-ap-clients='' \ --warning-ap-uptime='' \ @@ -267,7 +267,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -317,8 +317,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^total-error$' | | --warning-* | Warning threshold. Can be: 'ap-clients', 'ap-uptime', 'ap-lwappuptime', 'ctrl-ap-count'. | | --critical-* | Critical threshold. Can be: 'ap-clients', 'ap-uptime', 'ap-lwappuptime', 'ctrl-ap-count'. | -| --warning-ap-status | Define the conditions to match for the status to be WARNING (default: '%{admin\_status} =~ /enable/i && %{status} =~ /minor\|warning/i') You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | -| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} =~ /enable/i && %{status} =~ /major\|critical/i'). You can use the following variables: %{name}, %{status}, %{controller}, %{admin\_status} | +| --warning-ap-status | Define the conditions to match for the status to be WARNING (default: '%\{admin_status\} =~ /enable/i && %\{status\} =~ /minor\|warning/i') You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | +| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} =~ /enable/i && %\{status\} =~ /major\|critical/i'). You can use the following variables: %\{name\}, %\{status\}, %\{controller\}, %\{admin_status\} | | --reload-cache-time | Time in minutes before reloading cache file (default: 5). | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md index 48d2808d7b8b..0aa481836c23 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp.md @@ -432,8 +432,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALAUTHROUNDTRIPTIME | Thresholds | | | | WARNINGAUTHTRANSACTIONSSUCEEDED | Thresholds | | | | CRITICALAUTHTRANSACTIONSSUCEEDED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /dead/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /dead/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -448,7 +448,7 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | WARNINGINUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -475,8 +475,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALPEERSDETECTED | Thresholds | | | | WARNINGPEERUPDATELAST | Thresholds | | | | CRITICALPEERUPDATELAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | %{adminStatus} =~ /start/ && %{state} !~ /established/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | %\{adminStatus\} =~ /start/ && %\{state\} !~ /established/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -484,8 +484,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | %{running\_last\_changed} \> %{running\_last\_saved} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | %\{running_last_changed\} \> %\{running_last_saved\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -586,8 +586,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -624,8 +624,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Default value | Mandatory | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter partition name (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Thresholds | | | | CRITICALUSAGE | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -661,8 +661,8 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -688,10 +688,10 @@ yum install centreon-plugin-Network-Cisco-Standard-Snmp | CRITICALREMOVED | Set thresholds for members count for each states. | | | | WARNINGSDMMISMATCH | Set thresholds for members count for each states. | | | | CRITICALSDMMISMATCH | Set thresholds for members count for each states. | | | -| CRITICALSTACKSTATUS | Set critical threshold for stack status. You can use the following variables: %{stack\_status} | %{stack\_status} =~ /notredundant/ | | -| WARNINGSTACKSTATUS | Set warning threshold for stack status. You can use the following variables: %{stack\_status} | | | -| CRITICALSTATUS | Set critical threshold for member status. You can use the following variables: %{name}, %{role}, %{state} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed' | %{state} !~ /ready/ && %{state} !~ /provisioned/ | | -| WARNINGSTATUS | Set warning threshold for members status. You can use the following variables: %{name}, %{role}, %{state} | | | +| CRITICALSTACKSTATUS | Set critical threshold for stack status. You can use the following variables: %\{stack_status\} | %\{stack_status\} =~ /notredundant/ | | +| WARNINGSTACKSTATUS | Set warning threshold for stack status. You can use the following variables: %\{stack_status\} | | | +| CRITICALSTATUS | Set critical threshold for member status. You can use the following variables: %\{name\}, %\{role\}, %\{state\} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed' | %\{state\} !~ /ready/ && %\{state\} !~ /provisioned/ | | +| WARNINGSTATUS | Set warning threshold for members status. You can use the following variables: %\{name\}, %\{role\}, %\{state\} | | | | WARNINGVERSIONMISMATCH | Set thresholds for members count for each states. | | | | CRITICALVERSIONMISMATCH | Set thresholds for members count for each states. | | | | WARNINGWAITING | Set thresholds for members count for each states. | | | @@ -814,7 +814,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -882,9 +882,9 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='auth' | | --filter-name | Filter AAA server by name (Example: 10.199.126.100:1812:1813. Format: \[address\]:\[authPort\]:\[accPort\]). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /dead/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /dead/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'auth-requests', 'auth-requests-timeout', 'auth-transactions-suceeded', 'auth-roundtrip-time', 'acc-requests', 'acc-requests-timeout', 'acc-transactions-suceeded', 'acc-roundtrip-time'. | @@ -915,9 +915,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-qos-limit | Check QoS traffic limit rate. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-traffic-limit', 'out-traffic-limit', 'in-crc', 'in-fcserror', 'out-fc-wait', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -964,9 +964,9 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-remote-as | Filter based on remote AS number (regexp allowed) | | --filter-remote-addr | Filter based on IP of peers (regexp allowed) | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminStatus} =~ /start/ && %{state} !~ /established/'). You can use the following variables: %{adminStatus}, %{state}, %{localAddr}, %{remoteAddr}, %{remoteAs} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminStatus\} =~ /start/ && %\{state\} !~ /established/'). You can use the following variables: %\{adminStatus\}, %\{state\}, %\{localAddr\}, %\{remoteAddr\}, %\{remoteAs\} | | --warning-* --critical-* | Thresholds. Can be: 'peers-detected', 'peer-update-last', 'peer-prefixes-accepted', 'peer-prefixes-denied'. | @@ -974,8 +974,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{running\_last\_changed} \> %{running\_last\_saved}'). You can use the following variables: %{running\_last\_changed}, %{running\_last\_saved}, %{startup\_last\_changed} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{running_last_changed\} \> %\{running_last_saved\}'). You can use the following variables: %\{running_last_changed\}, %\{running_last_saved\}, %\{startup_last_changed\} | @@ -1037,9 +1037,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-qos-limit | Check QoS traffic limit rate. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-traffic-limit', 'out-traffic-limit', 'in-crc', 'in-fcserror', 'out-fc-wait', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -1095,9 +1095,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /readOnly/i'). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /readOnly/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%). | | --filter-name | Filter partition name (can be a regexp). | @@ -1132,8 +1132,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -1141,10 +1141,10 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Set thresholds for members count for each states.can be: 'waiting', 'progressing', 'added', 'ready', 'sdm-mismatch', 'version-mismatch', 'feature-mismatch', 'new-master-init', 'provisioned', 'invalid', 'removed') | -| --warning-stack-status | Set warning threshold for stack status (default: ''). You can use the following variables: %{stack\_status} | -| --critical-stack-status | Set critical threshold for stack status (default: '%{stack\_status} =~ /notredundant/'). You can use the following variables: %{stack\_status} | -| --warning-status | Set warning threshold for members status (default: ''). You can use the following variables: %{name}, %{role}, %{state} | -| --critical-status | Set critical threshold for member status (default: '%{state} !~ /ready/ && %{state} !~ /provisioned/'). You can use the following variables: %{name}, %{role}, %{state} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed'. | +| --warning-stack-status | Set warning threshold for stack status (default: ''). You can use the following variables: %\{stack_status\} | +| --critical-stack-status | Set critical threshold for stack status (default: '%\{stack_status\} =~ /notredundant/'). You can use the following variables: %\{stack_status\} | +| --warning-status | Set warning threshold for members status (default: ''). You can use the following variables: %\{name\}, %\{role\}, %\{state\} | +| --critical-status | Set critical threshold for member status (default: '%\{state\} !~ /ready/ && %\{state\} !~ /provisioned/'). You can use the following variables: %\{name\}, %\{role\}, %\{state\} Role can be: 'master', 'member', 'notMember', 'standby'. State can be: 'waiting', 'progressing', 'added', 'ready', 'sdmMismatch', 'verMismatch', 'featureMismatch', 'newMasterInit', 'provisioned', 'invalid', 'removed'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md b/pp/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md index 3cb2740c64fb..97fe1be8e788 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-standard-ssh.md @@ -201,9 +201,9 @@ yum install centreon-plugin-Network-Cisco-Standard-Ssh | Macro | Description | Default value | Mandatory | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERNAME | Filter name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | %{admin} eq "up" and %{oper} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | %\{admin\} eq "up" and %\{oper\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALOPERATIONALUP | Thresholds | | | @@ -292,7 +292,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -347,9 +347,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin} eq "up" and %{oper} eq "down"'). You can use the following variables: %{admin}, %{oper}, %{keepalive}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin\} eq "up" and %\{oper\} eq "down"'). You can use the following variables: %\{admin\}, %\{oper\}, %\{keepalive\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-operational-up'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md index 09376dcd8e8d..6ccf202d46e6 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-umbrella-snmp.md @@ -261,8 +261,8 @@ yum install centreon-plugin-Network-Cisco-Umbrella-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /yellow/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /red/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /yellow/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -270,14 +270,14 @@ yum install centreon-plugin-Network-Cisco-Umbrella-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| WARNINGADSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALADSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGCLOUDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALCLOUDSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | -| WARNINGLOCALDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | %{status} =~ /yellow/ | | -| CRITICALLOCALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{status} =~ /red/ | | +| WARNINGADSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALADSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGCLOUDSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALCLOUDSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | +| WARNINGLOCALDNSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /yellow/ | | +| CRITICALLOCALDNSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -425,7 +425,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,16 +479,16 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /yellow/') You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /red/'). You can use the following variables: %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /yellow/') You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\} | | Option | Description | |:-------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /yellow/'). Can be: 'dns-status', 'localdns-status', 'cloud-status', 'ad-status'. Can use special variables like: %{status}, %{display} | -| --critical-* | Define the conditions to match for the status to be CRITICAL. (default: %{status} =~ /red/). Can be: 'dns-connectivity', 'localdns-connectivity', 'cloud-connectivity', 'ad-connectivity'. Can use special variables like: %{status}, %{display} | +| --warning-* | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /yellow/'). Can be: 'dns-status', 'localdns-status', 'cloud-status', 'ad-status'. Can use special variables like: %\{status\}, %\{display\} | +| --critical-* | Define the conditions to match for the status to be CRITICAL. (default: %\{status\} =~ /red/). Can be: 'dns-connectivity', 'localdns-connectivity', 'cloud-connectivity', 'ad-connectivity'. Can use special variables like: %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md b/pp/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md index eaa3de329ab7..0fa779efc8d1 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-vcs-restapi.md @@ -277,8 +277,8 @@ yum install centreon-plugin-Network-Cisco-Vcs-Restapi | CRITICALRESPONSES4XX | Threshold | | | | WARNINGRESPONSES5XX | Threshold | | | | CRITICALRESPONSES5XX | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status} | %{status} ne "Active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\} | %\{status\} ne "Active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -296,8 +296,8 @@ yum install centreon-plugin-Network-Cisco-Vcs-Restapi | CRITICALSEARCHESMAXTARGETSEXCEEDED | Thresholds | | | | WARNINGSEARCHESTOTAL | Thresholds | | | | CRITICALSEARCHESTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %{status}, %{type}, %{name} | %{status} ne "Active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status}, %{type}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Can use special variables like: %\{status\}, %\{type\}, %\{name\} | %\{status\} ne "Active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\}, %\{type\}, %\{name\} | | | | WARNINGZONECALLSCURRENT | Thresholds | | | | CRITICALZONECALLSCURRENT | Thresholds | | | | WARNINGZONESCOUNT | Thresholds | | | @@ -327,7 +327,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-counters='' \ --filter-zone-name='' \ --warning-status='' \ - --critical-status='%{status} ne "Active"' \ + --critical-status='%\{status\} ne "Active"' \ --warning-zone-calls-current='' \ --critical-zone-calls-current='' \ --warning-searches-total='' \ @@ -399,7 +399,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -483,8 +483,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). (example: --filter-counters='responses') | | --warning-* --critical-* | Threshold. Can be: 'connections-client', 'connections-server', 'requests-completed', 'requests-get', 'requests-post', 'responses-1xx', 'responses-2xx', 'responses-3xx', 'responses-4xx', 'responses-5xx'. | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "Active"'). Can use special variables like: %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "Active"'). Can use special variables like: %\{status\}. | @@ -505,8 +505,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-zone-name | Filter zones by name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'zones-count', 'zone-calls-current', 'searches-total', 'searches-dropped', 'searches-maxsub-exceeded', 'searches-maxtargets-exceeded'. | -| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %{status}, %{type}, %{name}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} ne "Active"'). Can use special variables like: %{status}, %{type}, %{name}. | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: ''). Can use special variables like: %\{status\}, %\{type\}, %\{name\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} ne "Active"'). Can use special variables like: %\{status\}, %\{type\}, %\{name\}. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md index 5cacb512a48c..c63f51352bba 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-voice-gateway-snmp.md @@ -268,7 +268,7 @@ yum install centreon-plugin-Network-Cisco-Voice-Gateway-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -368,7 +368,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -464,9 +464,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md index 3b76c007cec2..edd5520f51e3 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-wap-snmp.md @@ -281,8 +281,8 @@ yum install centreon-plugin-Network-Cisco-Wap-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -309,9 +309,9 @@ yum install centreon-plugin-Network-Cisco-Wap-Snmp | Macro | Description | Default value | Mandatory | |:--------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------|:-----------:| | FILTERAPDESCRIPTION | Filter virtual access points by description (can be a regexp) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} eq "up" and %{operational\_status} eq "down"'). You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | %{admin\_status} eq "up" and %{operational\_status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} eq "up" and %\{operational_status\} eq "down"'). You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | %\{admin_status\} eq "up" and %\{operational_status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -394,7 +394,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -485,9 +485,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -547,9 +547,9 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-description | Filter virtual access points by description (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_status} eq "up" and %{operational\_status} eq "down"'). You can use the following variables: %{description}, %{admin\_status}, %{operational\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_status\} eq "up" and %\{operational_status\} eq "down"'). You can use the following variables: %\{description\}, %\{admin_status\}, %\{operational_status\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | diff --git a/pp/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md b/pp/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md index 84d51eb125e3..525cf4ad63ed 100644 --- a/pp/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cisco-wlc-snmp.md @@ -383,8 +383,8 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -396,10 +396,10 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | FILTERGROUP | Filter access point group (can be a regexp) | | | | WARNINGRADIOINTERFACECHANNELSUTILIZATION | Threshold | | | | CRITICALRADIOINTERFACECHANNELSUTILIZATION | Threshold | | | -| CRITICALRADIOSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} eq "down" | | -| WARNINGRADIOSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALRADIOSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} eq "down" | | +| WARNINGRADIOSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | WARNINGTOTALASSOCIATED | Threshold | | | @@ -486,8 +486,8 @@ yum install centreon-plugin-Network-Cisco-Wlc-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -613,7 +613,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -672,10 +672,10 @@ All available options for each service template are listed below: | --filter-name | Filter access point name (can be a regexp). | | --filter-group | Filter access point group (can be a regexp). | | --add-radio-interfaces | Monitor radio interfaces channels utilization. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-associated', 'total-disassociating', 'total-downloading', 'total-enabled', 'total-disabled', 'radio-interface-channels-utilization' (%). | @@ -687,10 +687,10 @@ All available options for each service template are listed below: | --filter-name | Filter access point name (can be a regexp). | | --filter-group | Filter access point group (can be a regexp). | | --add-radio-interfaces | Monitor radio interfaces channels utilization. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} !~ /associated\|downloading/'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "down"'). You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} !~ /associated\|downloading/'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --warning-radio-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-radio-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "down"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-associated', 'total-disassociating', 'total-downloading', 'total-enabled', 'total-disabled', 'radio-interface-channels-utilization' (%). | @@ -763,9 +763,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md b/pp/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md index d7ca4ae37bd8..cf8581905d6b 100644 --- a/pp/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-citrix-appacceleration-snmp.md @@ -326,7 +326,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md b/pp/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md index 5a021e537202..f61cc69fb2b2 100644 --- a/pp/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-citrix-sdx-snmp.md @@ -235,8 +235,8 @@ yum install centreon-plugin-Network-Citrix-Sdx-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter storage repository name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /good/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /good/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSAGE | Warning threshold | | | | CRITICALUSAGE | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -335,7 +335,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -425,8 +425,8 @@ All available options for each service template are listed below: |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^read\|write$' | | --filter-name | Filter storage repository name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /good/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /good/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'usage'. | | --critical-* | Critical threshold. Can be: 'usage'. | | --units | Units of thresholds (default: '%') ('%', 'B'). | diff --git a/pp/integrations/plugin-packs/procedures/network-colubris-snmp.md b/pp/integrations/plugin-packs/procedures/network-colubris-snmp.md index e39a82ddc9da..f3f682b70125 100644 --- a/pp/integrations/plugin-packs/procedures/network-colubris-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-colubris-snmp.md @@ -251,8 +251,8 @@ yum install centreon-plugin-Network-Colubris-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | FILTERNAME | Filter AP name with regexp | | | -| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | %{state} eq "disconnected" | | -| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALAPSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | %\{state\} eq "disconnected" | | +| WARNINGAPSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | WARNINGAPUSERS | Warning threshold | | | | CRITICALAPUSERS | Critical threshold | | | | WARNINGTOTALAP | Warning threshold | | | @@ -296,8 +296,8 @@ yum install centreon-plugin-Network-Colubris-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -413,7 +413,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -483,8 +483,8 @@ All available options for each service template are listed below: | --check-device-without-ctrl | Check device even if it doesn't belongs to an controller team. | | --warning-* | Warning threshold. Can be: 'total-ap', 'total-users', 'ap-users'. | | --critical-* | Critical threshold. Can be: 'total-ap', 'total-users', 'ap-users'. | -| --warning-ap-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "disconnected"'). You can use the following variables: %{state}, %{display} | +| --warning-ap-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-ap-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "disconnected"'). You can use the following variables: %\{state\}, %\{display\} | @@ -520,9 +520,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-cyberoam-snmp.md b/pp/integrations/plugin-packs/procedures/network-cyberoam-snmp.md index f2740e210371..5b4c040b8f48 100644 --- a/pp/integrations/plugin-packs/procedures/network-cyberoam-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-cyberoam-snmp.md @@ -320,7 +320,7 @@ yum install centreon-plugin-Network-Cyberoam-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -434,7 +434,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -536,9 +536,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dell-6200-snmp.md b/pp/integrations/plugin-packs/procedures/network-dell-6200-snmp.md index 0dd5da6690b8..88fe0bfac8f9 100644 --- a/pp/integrations/plugin-packs/procedures/network-dell-6200-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dell-6200-snmp.md @@ -386,7 +386,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -495,9 +495,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md index 7f65041164b4..7ee2e6bf2c06 100644 --- a/pp/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dell-nseries-snmp.md @@ -292,8 +292,8 @@ yum install centreon-plugin-Network-Dell-Nseries-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -418,7 +418,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -482,9 +482,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dell-os10-snmp.md b/pp/integrations/plugin-packs/procedures/network-dell-os10-snmp.md index 01b0930467b0..9b93f0a98239 100644 --- a/pp/integrations/plugin-packs/procedures/network-dell-os10-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dell-os10-snmp.md @@ -357,8 +357,8 @@ yum install centreon-plugin-Network-Dell-Os10-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -429,7 +429,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -506,7 +506,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -647,9 +647,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md index 355ce9a8e6c6..53b1e028ad61 100644 --- a/pp/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dell-sseries-snmp.md @@ -289,7 +289,7 @@ yum install centreon-plugin-Network-Dell-Sseries-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -376,7 +376,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,9 +479,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-denyall-snmp.md b/pp/integrations/plugin-packs/procedures/network-denyall-snmp.md index 8a7561b6af1e..7badd1f85073 100644 --- a/pp/integrations/plugin-packs/procedures/network-denyall-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-denyall-snmp.md @@ -312,8 +312,8 @@ yum install centreon-plugin-Network-Denyall-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -362,8 +362,8 @@ yum install centreon-plugin-Network-Denyall-Snmp | CRITICALMEMORYUSAGE | Threshold | | | | WARNINGREQUESTS | Threshold | | | | CRITICALREQUESTS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{uid} | %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{uid} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{uid\} | %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{uid\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -514,7 +514,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -580,9 +580,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -633,9 +633,9 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-uid | Filter reverse proxy by UID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{uid} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{uid} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{uid} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{uid\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{uid\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{uid\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'memory-usage', 'requests'. | diff --git a/pp/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md b/pp/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md index a79cc6bf304a..a0eaa661485f 100644 --- a/pp/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-digi-anywhereusb-snmp.md @@ -231,7 +231,7 @@ yum install centreon-plugin-Network-Digi-AnywhereUSB-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -320,7 +320,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -410,9 +410,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md b/pp/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md index 4beccb163ac3..1c798ab6e474 100644 --- a/pp/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-digi-portserverts-snmp.md @@ -231,7 +231,7 @@ yum install centreon-plugin-Network-Digi-Portserverts-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -319,7 +319,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -409,9 +409,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md b/pp/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md index ca6ab257084c..28e890f0f830 100644 --- a/pp/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-digi-sarian-snmp.md @@ -257,10 +257,10 @@ yum install centreon-plugin-Network-Digi-Sarian-Snmp |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------|:-----------:| | WARNINGSIGNAL | Warning threshold for signal strength | | | | CRITICALSIGNAL | Critical threshold for signal strength | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{registered}, %{attachement} | %{attachement} eq "attached" and %{registered} !~ /registeredHostNetwork\|registeredRoaming/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{registered}, %{attachement} | | | -| CRITICALTECHNOLOGY | Set critical threshold for technology. Use special variables %{technology} | %{technology} !~ /2G\|3G\|4G/ | | -| WARNINGTECHNOLOGY | Set warning threshold for technology. Use special variables %{technology} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{registered\}, %\{attachement\} | %\{attachement\} eq "attached" and %\{registered\} !~ /registeredHostNetwork\|registeredRoaming/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{registered\}, %\{attachement\} | | | +| CRITICALTECHNOLOGY | Set critical threshold for technology. Use special variables %\{technology\} | %\{technology\} !~ /2G\|3G\|4G/ | | +| WARNINGTECHNOLOGY | Set warning threshold for technology. Use special variables %\{technology\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -295,7 +295,7 @@ yum install centreon-plugin-Network-Digi-Sarian-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -408,7 +408,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -450,10 +450,10 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='signal\|technology' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{registered}, %{attachement} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{attachement} eq "attached" and %{registered} !~ /registeredHostNetwork\|registeredRoaming/' You can use the following variables: %{registered}, %{attachement} | -| --warning-technology | Set warning threshold for technology. Use special variables %{technology}. | -| --critical-technology | Set critical threshold for technology (default: '%{technology} !~ /2G\|3G\|4G/' Use special variables %{technology}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{registered\}, %\{attachement\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{attachement\} eq "attached" and %\{registered\} !~ /registeredHostNetwork\|registeredRoaming/' You can use the following variables: %\{registered\}, %\{attachement\} | +| --warning-technology | Set warning threshold for technology. Use special variables %\{technology\}. | +| --critical-technology | Set critical threshold for technology (default: '%\{technology\} !~ /2G\|3G\|4G/' Use special variables %\{technology\}. | | --warning-signal | Warning threshold for signal strength. | | --critical-signal | Critical threshold for signal strength. | @@ -500,9 +500,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md b/pp/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md index 106a226fa39d..2913fcd95ec7 100644 --- a/pp/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dlink-dgs3100-snmp.md @@ -239,7 +239,7 @@ yum install centreon-plugin-Network-Dlink-Dgs3100-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -326,7 +326,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -419,9 +419,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md index 522dc8d0bcb4..67cf2f26f74c 100644 --- a/pp/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-dlink-standard-snmp.md @@ -283,8 +283,8 @@ yum install centreon-plugin-Network-Dlink-Standard-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --use-new-perfdata --verbose --no-skipped-counters | | @@ -305,12 +305,12 @@ yum install centreon-plugin-Network-Dlink-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------|:-----------:| -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{status} =~ /unknown/i | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{status}, %{display} | %{status} eq "down" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /codeUpdate/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{status} =~ /codeUpdate/i | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | %{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{status\} =~ /unknown/i | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "down" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /codeUpdate/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{status\} =~ /codeUpdate/i | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i | | | WARNINGMEMBERSTOTAL | Thresholds | | | | CRITICALMEMBERSTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -397,7 +397,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -492,9 +492,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{errdisable}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{errdisable\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -537,12 +537,12 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /codeUpdate/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %{role}, %{roleLast}, %{status}, %{display} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /codeUpdate/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} =~ /unsupported\|codeMismatch/i'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{status\}, %\{display\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total'. | diff --git a/pp/integrations/plugin-packs/procedures/network-efficientip-snmp.md b/pp/integrations/plugin-packs/procedures/network-efficientip-snmp.md index 3622c06fbdfa..0e6a27d430dc 100644 --- a/pp/integrations/plugin-packs/procedures/network-efficientip-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-efficientip-snmp.md @@ -614,8 +614,8 @@ yum install centreon-plugin-Network-Efficientip-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------|:-----------:| -| WARGNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /upgrading\|split-brain/') Can be used with special variables like: %{status}, %{role} | %{status} =~ /upgrading\|split-brain/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %{status}, %{role} | %{status} =~ /invalid credentials\|replication stopped\|timeout/ | | +| WARGNINGSTATUS | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /upgrading\|split-brain/') Can be used with special variables like: %\{status\}, %\{role\} | %\{status\} =~ /upgrading\|split-brain/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %\{status\}, %\{role\} | %\{status\} =~ /invalid credentials\|replication stopped\|timeout/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -707,7 +707,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -887,8 +887,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%{status} =~ /upgrading\|split-brain/') Can be used with special variables like: %{status}, %{role} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{status} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %{status}, %{role} | +| --warning-status | Define the conditions to match for the status to be WARNING. (default: '%\{status\} =~ /upgrading\|split-brain/') Can be used with special variables like: %\{status\}, %\{role\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{status\} =~ /invalid credentials\|replication stopped\|timeout/') Can be used with special variables like: %\{status\}, %\{role\} | diff --git a/pp/integrations/plugin-packs/procedures/network-enterasys-snmp.md b/pp/integrations/plugin-packs/procedures/network-enterasys-snmp.md index e2b1aae66cde..6783897c9012 100644 --- a/pp/integrations/plugin-packs/procedures/network-enterasys-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-enterasys-snmp.md @@ -286,8 +286,8 @@ yum install centreon-plugin-Network-Enterasys-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -438,7 +438,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -488,9 +488,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md b/pp/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md index 557e2d8a5496..bbf80fdd7d87 100644 --- a/pp/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-evertz-fc7800-snmp.md @@ -326,7 +326,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -353,7 +353,7 @@ All generic options are listed here: | --filter | Exclude some parts (comma separated list) You can also exclude items from specific instances: --filter=psu,1 | | --absent-problem | Return an error if a component is not 'present' (default is skipping). It can be set globally or for a specific instance: --absent-problem='component\_name' or --absent-problem='component\_name,instance\_value'. | | --no-component | Define the expected status if no components are found (default: critical). | -| --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='psu,OK,notAvailable' package network::evertz::FC7800::snmp::mode::components::psu; use strict; use warnings; my %map\_psu\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_psu = { powerSupply1Status =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.3', map =\> \%map\_psu\_status }, powerSupply2Status =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.4', map =\> \%map\_psu\_status }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, $mapping\_psu-\>{powerSupply1Status}-\>{oid} . '.0', $mapping\_psu-\>{powerSupply2Status}-\>{oid} . '.0'; } sub check\_psu { my ($self, %options) = @\_; return if (!defined($options{status})); return if ($self-\>check\_filter(section =\> 'psu', instance =\> $options{instance})); $self-\>{components}-\>{psu}-\>{total}++; $self-\>{output}-\>output\_add(long\_msg =\> sprintf("power supply '%s' status is '%s' \[instance = %s\]", $options{instance}, $options{status}, $options{instance})); my $exit = $self-\>get\_severity(section =\> 'psu', value =\> $options{status}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Power supply '%s' status is '%s'", $options{instance}, $options{status})); } } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking poer supplies"); $self-\>{components}-\>{psu} = {name =\> 'psus', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'psu')); my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping\_psu, results =\> $self-\>{results}, instance =\> '0'); check\_psu($self, status =\> $result-\>{powerSupply1Status}, instance =\> 1); check\_psu($self, status =\> $result-\>{powerSupply2Status}, instance =\> 2); } 1; package network::evertz::FC7800::snmp::mode::components::frameline; use strict; use warnings; my %map\_frameline\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_frameline = { frameStatusLine =\> { oid =\> '.1.3.6.1.4.1.6827.10.232.4.2', map =\> \%map\_frameline\_status }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, $mapping\_frameline-\>{frameStatusLine}-\>{oid} . '.0'; } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking frame line"); $self-\>{components}-\>{frameline} = {name =\> 'frameline', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'frameline')); my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping\_frameline, results =\> $self-\>{results}, instance =\> '0'); return if (!defined($result-\>{frameStatusLine})); $self-\>{components}-\>{frameline}-\>{total}++; $self-\>{output}-\>output\_add(long\_msg =\> sprintf("frame line status is '%s' \[instance = %s\]", $result-\>{frameStatusLine}, '0')); my $exit = $self-\>get\_severity(section =\> 'frameline', value =\> $result-\>{frameStatusLine}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Frame line status is '%s'", $result-\>{frameStatusLine})); } } 1; | +| --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='psu,OK,notAvailable' package network::evertz::FC7800::snmp::mode::components::psu; use strict; use warnings; my %map\_psu\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_psu = \{ powerSupply1Status =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.3', map =\> \%map\_psu\_status \}, powerSupply2Status =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.4', map =\> \%map\_psu\_status \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}\}, $mapping\_psu-\>\{powerSupply1Status\}-\>\{oid\} . '.0', $mapping\_psu-\>\{powerSupply2Status\}-\>\{oid\} . '.0'; \} sub check\_psu \{ my ($self, %options) = @\_; return if (!defined($options\{status\})); return if ($self-\>check\_filter(section =\> 'psu', instance =\> $options\{instance\})); $self-\>\{components\}-\>\{psu\}-\>\{total\}++; $self-\>\{output\}-\>output\_add(long\_msg =\> sprintf("power supply '%s' status is '%s' \[instance = %s\]", $options\{instance\}, $options\{status\}, $options\{instance\})); my $exit = $self-\>get\_severity(section =\> 'psu', value =\> $options\{status\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Power supply '%s' status is '%s'", $options\{instance\}, $options\{status\})); \} \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking poer supplies"); $self-\>\{components\}-\>\{psu\} = \{name =\> 'psus', total =\> 0, skip =\> 0\}; return if ($self-\>check\_filter(section =\> 'psu')); my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping\_psu, results =\> $self-\>\{results\}, instance =\> '0'); check\_psu($self, status =\> $result-\>\{powerSupply1Status\}, instance =\> 1); check\_psu($self, status =\> $result-\>\{powerSupply2Status\}, instance =\> 2); \} 1; package network::evertz::FC7800::snmp::mode::components::frameline; use strict; use warnings; my %map\_frameline\_status = (1 =\> 'false', 2 =\> 'true', 3 =\> 'notAvailable'); my $mapping\_frameline = \{ frameStatusLine =\> \{ oid =\> '.1.3.6.1.4.1.6827.10.232.4.2', map =\> \%map\_frameline\_status \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}\}, $mapping\_frameline-\>\{frameStatusLine\}-\>\{oid\} . '.0'; \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking frame line"); $self-\>\{components\}-\>\{frameline\} = \{name =\> 'frameline', total =\> 0, skip =\> 0\}; return if ($self-\>check\_filter(section =\> 'frameline')); my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping\_frameline, results =\> $self-\>\{results\}, instance =\> '0'); return if (!defined($result-\>\{frameStatusLine\})); $self-\>\{components\}-\>\{frameline\}-\>\{total\}++; $self-\>\{output\}-\>output\_add(long\_msg =\> sprintf("frame line status is '%s' \[instance = %s\]", $result-\>\{frameStatusLine\}, '0')); my $exit = $self-\>get\_severity(section =\> 'frameline', value =\> $result-\>\{frameStatusLine\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add(severity =\> $exit, short\_msg =\> sprintf("Frame line status is '%s'", $result-\>\{frameStatusLine\})); \} \} 1; | | --warning | Define the warning threshold for temperatures (syntax: type,instance,threshold) Example: --warning='temperature,.*,30' | | --critical | Define the critical threshold for temperatures (syntax: type,instance,threshold) Example: --critical='temperature,.*,40' | | --warning-count-* | Define the warning threshold for the number of components of one type (replace '*' with the component type). | diff --git a/pp/integrations/plugin-packs/procedures/network-extreme-snmp.md b/pp/integrations/plugin-packs/procedures/network-extreme-snmp.md index dfde726ea146..15438e4d88dd 100644 --- a/pp/integrations/plugin-packs/procedures/network-extreme-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-extreme-snmp.md @@ -274,12 +274,12 @@ yum install centreon-plugin-Network-Extreme-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{role}, %{roleLast} | | | -| UNKNOWNPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} eq "mismatch"'). You can use the following variables: %{role}, %{roleLast} | %{status} eq "mismatch" | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} eq "down"'). You can use the following variables: %{role}, %{roleLast} | %{role} ne %{roleLast} \|\| %{status} eq "down" | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} ne "up"'). You can use the following variables: %{link\_status}, %{display} | %{link\_status} ne "up" | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{role\}, %\{roleLast\} | | | +| UNKNOWNPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "mismatch"'). You can use the following variables: %\{role\}, %\{roleLast\} | %\{status\} eq "mismatch" | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down"'). You can use the following variables: %\{role\}, %\{roleLast\} | %\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down" | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} ne "up"'). You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} ne "up" | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -316,7 +316,7 @@ yum install centreon-plugin-Network-Extreme-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -404,7 +404,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Only keep perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -500,12 +500,12 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-member-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{role}, %{roleLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%{status} eq "mismatch"'). You can use the following variables: %{role}, %{roleLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} \|\| %{status} eq "down"'). You can use the following variables: %{role}, %{roleLast} | -| --unknown-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{link\_status}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} ne "up"'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{role\}, %\{roleLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "mismatch"'). You can use the following variables: %\{role\}, %\{roleLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} \|\| %\{status\} eq "down"'). You can use the following variables: %\{role\}, %\{roleLast\} | +| --unknown-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} ne "up"'). You can use the following variables: %\{link_status\}, %\{display\} | @@ -532,9 +532,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-congdropped', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-fiberstore-snmp.md b/pp/integrations/plugin-packs/procedures/network-fiberstore-snmp.md index 1100c931d28b..6fd39d4fe817 100644 --- a/pp/integrations/plugin-packs/procedures/network-fiberstore-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fiberstore-snmp.md @@ -262,8 +262,8 @@ yum install centreon-plugin-Network-Fiberstore-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -303,7 +303,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -376,7 +376,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -469,9 +469,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md index 4673f115f965..8ece14e743fb 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-arkoon-snmp.md @@ -324,7 +324,7 @@ yum install centreon-plugin-Network-Firewalls-Arkoon-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -370,7 +370,7 @@ yum install centreon-plugin-Network-Firewalls-Arkoon-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -462,7 +462,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -556,9 +556,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -653,9 +653,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md index 383cb42349bd..c6cb8c4ebedb 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-checkpoint-snmp.md @@ -318,8 +318,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| | NOHASTATUS | Status to return when HA not running or not installed (default: 'UNKNOWN') | UNKNOWN | | -| WARNINGSTATUS | Trigger warning on %{role} or %{hastate} values. Example: --warning-status '%{role} !~ /master/' will warn when failover occurs | %{hastate} !~ /(UP\|working)/ | | -| CRITICALSTATUS | Trigger critical on %{role} or %{hastate} values (default: '%{hastate} !~ /(UP\|working)/') | | | +| WARNINGSTATUS | Trigger warning on %\{role\} or %\{hastate\} values. Example: --warning-status '%\{role\} !~ /master/' will warn when failover occurs | %\{hastate\} !~ /(UP\|working)/ | | +| CRITICALSTATUS | Trigger critical on %\{role\} or %\{hastate\} values (default: '%\{hastate\} !~ /(UP\|working)/') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -365,7 +365,7 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -373,8 +373,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "permanent" and %{status} =~ /down/i'). You can use the following variables: %{type}, %{status}, %{display} | %{type} eq "permanent" and %{status} =~ /down/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "permanent" and %\{status\} =~ /down/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | %\{type\} eq "permanent" and %\{status\} =~ /down/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -382,8 +382,8 @@ yum install centreon-plugin-Network-Firewalls-Checkpoint-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "up" and %{operState} ne %{operStateLast}'). You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | %{adminState} eq "up" and %{operState} ne %{operStateLast} | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\}'). You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | %\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\} | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -479,7 +479,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -560,8 +560,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Trigger warning on %{role} or %{hastate} values. Example: --warning-status '%{role} !~ /master/' will warn when failover occurs. | -| --critical-status | Trigger critical on %{role} or %{hastate} values (default: '%{hastate} !~ /(UP\|working)/'). | +| --warning-status | Trigger warning on %\{role\} or %\{hastate\} values. Example: --warning-status '%\{role\} !~ /master/' will warn when failover occurs. | +| --critical-status | Trigger critical on %\{role\} or %\{hastate\} values (default: '%\{hastate\} !~ /(UP\|working)/'). | | --no-ha-status | Status to return when HA not running or not installed (default: 'UNKNOWN'). | @@ -621,9 +621,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -650,8 +650,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter vpn name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{type}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{type} eq "permanent" and %{status} =~ /down/i'). You can use the following variables: %{type}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{type\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{type\} eq "permanent" and %\{status\} =~ /down/i'). You can use the following variables: %\{type\}, %\{status\}, %\{display\} | | --buggy-snmp | Checkpoint snmp can be buggy. Test that option if no response. | | --warning-* --critical-* | Thresholds. Can be: 'tunnels-total'. | @@ -672,8 +672,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "up" and %{operState} ne %{operStateLast}'). You can use the following variables: %{adminState}, %{operStateLast}, %{operState}, %{masterIpAddr} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "up" and %\{operState\} ne %\{operStateLast\}'). You can use the following variables: %\{adminState\}, %\{operStateLast\}, %\{operState\}, %\{masterIpAddr\} | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md index 5c71fd4e9397..1d2441c77a47 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-cisco-asa-snmp.md @@ -327,8 +327,8 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | WARNINGACTIVEUNITS | Warning threshold | | | | CRITICALACTIVEUNITS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -408,7 +408,7 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -465,7 +465,7 @@ yum install centreon-plugin-Network-Firewalls-Cisco-Asa-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -555,7 +555,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -630,8 +630,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{primaryStateLast}, %{secondaryStateLast}, %{primaryState}, %{secondaryState} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{primaryStateLast\}, %\{secondaryStateLast\}, %\{primaryState\}, %\{secondaryState\} | | --warning-* | Warning threshold. Can be: 'active-units'. | | --critical-* | Critical threshold. Can be: 'active-units'. | @@ -693,9 +693,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -774,9 +774,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md index 6fc28dfeedb7..46535851fe5b 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-fortinet-fortigate-snmp.md @@ -365,8 +365,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALCPUUTILIZATION | Set thresholds | | | | WARNINGMEMORYUSAGE | Set thresholds | | | | CRITICALMEMORYUSAGE | Set thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/'). You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | %{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/'). You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | %\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | | | | WARNINGSYNCHRONIZED | Set thresholds | | | | CRITICALSYNCHRONIZED | Set thresholds | | | | WARNINGTOTALCHECKSUMS | Set thresholds | | | @@ -445,8 +445,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALJITTER | Thresholds | | | | WARNINGLATENCY | Thresholds | | | | CRITICALLATENCY | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | | | | WARNINGTRAFFICBI | Thresholds | | | | CRITICALTRAFFICBI | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -482,7 +482,7 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -548,8 +548,8 @@ yum install centreon-plugin-Network-Firewalls-Fortinet-Fortigate-Snmp | CRITICALSESSIONSACTIVE | Thresholds | | | | WARNINGSESSIONSRATE | Thresholds | | | | CRITICALSESSIONSRATE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -668,7 +668,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -734,8 +734,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{role} ne %{roleLast} or %{sync\_status} =~ /unsynchronized/'). You can use the following variables: %{serial}, %{hostname}, %{sync\_status}, %{role}, %{roleLast} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{role\} ne %\{roleLast\} or %\{sync_status\} =~ /unsynchronized/'). You can use the following variables: %\{serial\}, %\{hostname\}, %\{sync_status\}, %\{role\}, %\{roleLast\} | | --warning-* --critical-* | Set thresholds. Can be: 'total-nodes', 'synchronized', 'unsynchronized', 'total-checksums', 'cpu-utilization', 'memory-usage'. | @@ -816,9 +816,9 @@ All available options for each service template are listed below: | --filter-id | Define which SD-WAN links should be monitored based on their IDs. This option will be treated as a regular expression. | | --filter-name | Define which SD-WAN links should be monitored based on their names. This option will be treated as a regular expression. | | --filter-vdom | Define which virtual domains should be monitored based on their names. This option will be treated as a regular expression. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{vdom}, %{id}, %{name}, %{ifName} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{vdom\}, %\{id\}, %\{name\}, %\{ifName\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'traffic-bi', 'latency', 'jitter', 'packetloss'. | @@ -853,9 +853,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -899,9 +899,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -945,9 +945,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -986,8 +986,8 @@ All available options for each service template are listed below: | --filter-* | Filter name with regexp. Can be ('vdomain', 'vpn') | | --warning-* | Warning on counters. Can be ('users', 'sessions', 'tunnels', 'traffic-in', 'traffic-out') | | --critical-* | Warning on counters. Can be ('users', 'sessions', 'tunnels', 'traffic-in', 'traffic-out') | -| --warning-status | Define the conditions to match for the status to be WARNING. Use "%{state}" as a special variable. Useful to be notified when tunnel is up "%{state} eq 'up'" | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Use "%{state}" as a special variable. Useful to be notified when tunnel is up "%{state} eq 'up'" | +| --warning-status | Define the conditions to match for the status to be WARNING. Use "%\{state\}" as a special variable. Useful to be notified when tunnel is up "%\{state\} eq 'up'" | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Use "%\{state\}" as a special variable. Useful to be notified when tunnel is up "%\{state\} eq 'up'" | @@ -1010,8 +1010,8 @@ All available options for each service template are listed below: | --add-traffic | Add traffic usage by virtual domain. | | --add-policy | Add number of policies by virtual domain. | | --policy-cache-time | Time in minutes before reloading cache file (default: 60). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{op\_mode}, %{ha\_state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{op_mode\}, %\{ha_state\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'sessions-active', 'session-rate', 'memory-usage-prct', 'license-usage', 'license-free', 'license-usage-prct', 'traffic-in', 'traffic-out', 'policies-active'. | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md index 46111c603372..805b8bbbbdf0 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-mag-snmp.md @@ -364,7 +364,7 @@ yum install centreon-plugin-Network-Juniper-Mag-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -408,7 +408,7 @@ is able to monitor a resource using a command like this one (replace the sample --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -474,7 +474,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -599,9 +599,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -647,9 +647,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md index 2ff25849584a..f7c702ce2eb0 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-sa-snmp.md @@ -383,7 +383,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Sa-Snmp | WARNINGIN | Thresholds | | | | CRITICALOUT | Thresholds | | | | WARNINGOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -493,7 +493,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -630,9 +630,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -679,9 +679,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md index cd55a8c690eb..e5923316239b 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-srx-snmp.md @@ -426,7 +426,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Srx-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -538,7 +538,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -710,9 +710,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds (will superseed --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md index 5bb96d27de90..611cb2eff909 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-juniper-ssg-snmp.md @@ -324,7 +324,7 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Ssg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -333,8 +333,8 @@ yum install centreon-plugin-Network-Firewalls-Juniper-Ssg-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------|:-----------:| | FILTERNAME | Check only VPNs whose name match the given regular expression. | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{p1state} eq "inactive" \|\| %{p2state} eq "inactive"'). You can use the following variables: %{p1state}, %{p2state} | %{p1state} eq "inactive" \|\| %{p2state} eq "inactive" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{p1state}, %{p2state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive"'). You can use the following variables: %\{p1state\}, %\{p2state\} | %\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{p1state\}, %\{p2state\} | | | | WARNINGUPDATETIME | Warning threshold for update time (in secondes) | | | | CRITICALUPDATETIME | Critical threshold for update time (in secondes) | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -436,7 +436,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -559,9 +559,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -588,8 +588,8 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Check only VPNs whose name match the given regular expression. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{p1state}, %{p2state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{p1state} eq "inactive" \|\| %{p2state} eq "inactive"'). You can use the following variables: %{p1state}, %{p2state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{p1state\}, %\{p2state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{p1state\} eq "inactive" \|\| %\{p2state\} eq "inactive"'). You can use the following variables: %\{p1state\}, %\{p2state\} | | --warning-update-time | Warning threshold for update time (in secondes). | | --critical-update-time | Critical threshold for update time (in secondes). | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md index 3e1e9fb47a0d..9979153e47c4 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-snmp.md @@ -349,8 +349,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -377,8 +377,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /not-connected/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /not-connected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /not-connected/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /not-connected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -485,7 +485,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -590,9 +590,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -648,8 +648,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /not-connected/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /not-connected/i'). You can use the following variables: %\{status\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md b/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md index d3112587c4ca..ce8101ddf925 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-paloalto-standard-ssh.md @@ -223,15 +223,15 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------|:-----------:| -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{status}, %{display} | | | -| UNKNOWNSYNCSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{enabled}, %{status} | | | -| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{state}, %{stateLast} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "up"'). Can use special variables like: %{status}, %{display} | %{status} ne "up" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{status}, %{display} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast}'). Can use special variables like: %{state}, %{stateLast} | %{state} ne %{stateLast} | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{state}, %{stateLast} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{status} ne "synchronized"'). Can use special variables like: %{enabled}, %{status} | %{enabled} eq "yes" and %{status} ne "synchronized" | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{enabled}, %{status} | | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{status\}, %\{display\} | | | +| UNKNOWNSYNCSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | | | +| UNKNOWNMEMBERSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "up"'). Can use special variables like: %\{status\}, %\{display\} | %\{status\} ne "up" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{status\}, %\{display\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\}'). Can use special variables like: %\{state\}, %\{stateLast\} | %\{state\} ne %\{stateLast\} | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{status\} ne "synchronized"'). Can use special variables like: %\{enabled\}, %\{status\} | %\{enabled\} eq "yes" and %\{status\} ne "synchronized" | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -240,9 +240,9 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter interface name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "active"'). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | %{state} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "active"'). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | %\{state\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -252,11 +252,11 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Default value | Mandatory | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | | | | WARNINGIPSECTOTAL | Thresholds | | | | CRITICALIPSECTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ike\_phase1\_state} eq "down" or %{state} ne "active"'). You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | %{ike\_phase1\_state} eq "down" or %{state} ne "active" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ike_phase1_state\} eq "down" or %\{state\} ne "active"'). You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | %\{ike_phase1_state\} eq "down" or %\{state\} ne "active" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | FILTERFEATURE | Filter license by feature (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%{expired} eq "yes"'). Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | %{expired} eq "yes" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. (default: '%\{expired\} eq "yes"'). Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | %\{expired\} eq "yes" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -276,8 +276,8 @@ yum install centreon-plugin-Network-Firewalls-Paloalto-Standard-Ssh |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| | WARNINGAVUPDATE | Thresholds | | | | CRITICALAVUPDATE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_mode} !~ /normal/i'). You can use the following variables: %{oper\_mode} | %{oper\_mode} !~ /normal/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_mode} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_mode\} !~ /normal/i'). You can use the following variables: %\{oper_mode\} | %\{oper_mode\} !~ /normal/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_mode\} | | | | WARNINGTHREATUPDATE | Thresholds | | | | CRITICALTHREATUPDATE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -380,7 +380,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -450,15 +450,15 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-sync-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{enabled}, %{status} | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{enabled}, %{status} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{status} ne "synchronized"'). Can use special variables like: %{enabled}, %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast}'). Can use special variables like: %{state}, %{stateLast} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %{status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %{status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "up"'). Can use special variables like: %{status}, %{display} | +| --unknown-sync-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{enabled\}, %\{status\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{status\} ne "synchronized"'). Can use special variables like: %\{enabled\}, %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\}'). Can use special variables like: %\{state\}, %\{stateLast\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN (default: ''). Can use special variables like: %\{status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING (default: ''). Can use special variables like: %\{status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "up"'). Can use special variables like: %\{status\}, %\{display\} | @@ -466,9 +466,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter interface name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne "active"'). You can use the following variables: %{state}, %{type}, %{ha\_state}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne "active"'). You can use the following variables: %\{state\}, %\{type\}, %\{ha_state\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | @@ -477,9 +477,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter tunnels by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ike\_phase1\_state} eq "down" or %{state} ne "active"'). You can use the following variables: %{ike\_phase1\_state}, %{state}, %{monitor\_status}, %{display}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ike_phase1_state\} eq "down" or %\{state\} ne "active"'). You can use the following variables: %\{ike_phase1_state\}, %\{state\}, %\{monitor_status\}, %\{display\}. | | --warning-* --critical-* | Thresholds. Can be: 'ipsec-total'. | @@ -488,8 +488,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-feature | Filter license by feature (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%{expired} eq "yes"'). Can use special variables like: %{expired}, %{expiry\_days}, %{feature} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. (default: '%\{expired\} eq "yes"'). Can use special variables like: %\{expired\}, %\{expiry_days\}, %\{feature\} | @@ -510,8 +510,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --timezone | Timezone options. Default is 'GMT'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{oper\_mode} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{oper\_mode} !~ /normal/i'). You can use the following variables: %{oper\_mode} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{oper_mode\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{oper_mode\} !~ /normal/i'). You can use the following variables: %\{oper_mode\} | | --warning-* --critical-* | Thresholds. Can be: 'av-update' (s), 'threat-update' (s), 'sessions-traffic' (b/s), 'sessions-total-active'. | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md index db8b6ab1fc37..d3f4e9f0dcef 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-pfsense-snmp.md @@ -443,7 +443,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md b/pp/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md index df603121b967..87143645bbac 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-sonicwall-snmp.md @@ -325,7 +325,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md b/pp/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md index be7101ce90f6..9242d7258a00 100644 --- a/pp/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md +++ b/pp/integrations/plugin-packs/procedures/network-firewalls-stonesoft.md @@ -386,7 +386,7 @@ yum install centreon-plugin-Network-Firewalls-Stonesoft | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -478,7 +478,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -538,9 +538,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{node\_status} =~ /unknown/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{node\_status} =~ /lockedOnline/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{node\_status} =~ /^(?:offline\|goingOffline\|lockedOffline\|goingLockedOffline\|stand by\|goingStandby)$/i'). You can use the following variables: %{node\_status}, %{node\_member\_id}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{node_status\} =~ /unknown/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{node_status\} =~ /lockedOnline/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{node_status\} =~ /^(?:offline\|goingOffline\|lockedOffline\|goingLockedOffline\|stand by\|goingStandby)$/i'). You can use the following variables: %\{node_status\}, %\{node_member_id\}. | @@ -672,9 +672,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -720,9 +720,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md index 62aecb2dc8ef..6cf70f49beaa 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiadc-snmp.md @@ -311,8 +311,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -329,8 +329,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| CRITICALDDOSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} eq "attacking" | | -| WARNINGDDOSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALDDOSSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} eq "attacking" | | +| WARNINGDDOSSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -349,8 +349,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiadc-Snmp |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERNAME | Filter virtual servers by name | | | | FILTERVDOM | Filter virtual servers by vdom name | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | %{status} eq "unhealthy" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | %\{status\} eq "unhealthy" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | | | | WARNINGVIRTUALSERVERCONNECTIONS | Threshold | | | | CRITICALVIRTUALSERVERCONNECTIONS | Threshold | | | | WARNINGVIRTUALSERVERSDETECTED | Threshold | | | @@ -380,7 +380,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-version='2c' \ --snmp-community='my-snmp-community' \ --warning-ddos-status='' \ - --critical-ddos-status='%{status} eq "attacking"' + --critical-ddos-status='%\{status\} eq "attacking"' ``` The expected command output is shown below: @@ -466,7 +466,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -532,9 +532,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -582,8 +582,8 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-ddos-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-ddos-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "attacking"'). You can use the following variables: %{status} | +| --warning-ddos-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-ddos-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "attacking"'). You can use the following variables: %\{status\} | @@ -619,9 +619,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter virtual servers by name. | | --filter-vdom | Filter virtual servers by vdom name. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "unhealthy"'). You can use the following variables: %{status}, %{state}, %{name}, %{vdom} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "unhealthy"'). You can use the following variables: %\{status\}, %\{state\}, %\{name\}, %\{vdom\} | | --warning-* --critical-* | Thresholds. Can be: 'virtualservers-detected', 'virtualservers-healthy', 'virtualserver-connections', 'virtualserver-throughput'. | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md index 022b1238ffb1..62b21918435e 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiauthenticator-snmp.md @@ -302,7 +302,7 @@ yum install centreon-plugin-Network-Fortinet-Fortiauthenticator-Snmp | Macro | Description | Default value | Mandatory | |:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------|:-----------:| | UNKNOWNHASTATUS | Threshold | | | -| CRITICALHASTATUS | Threshold | %{ha\_status} ne %{ha\_status\_last} | | +| CRITICALHASTATUS | Threshold | %\{ha_status\} ne %\{ha_status_last\} | | | WARNINGHASTATUS | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -326,8 +326,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiauthenticator-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -462,7 +462,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -518,8 +518,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | @@ -546,9 +546,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md index bb5958c35c5b..49b2fc87364d 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortigate-restapi.md @@ -217,8 +217,8 @@ yum install centreon-plugin-Network-Fortinet-Fortigate-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------|:-----------:| | FILTERVDOM | Filter vdom by name | | | -| CRITICALHEALTH | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /success/i'). You can use the following variables: %{status}, %{name} | %{status} !~ /success/i | | -| WARNINGHEALTH | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALHEALTH | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /success/i'). You can use the following variables: %\{status\}, %\{name\} | %\{status\} !~ /success/i | | +| WARNINGHEALTH | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -230,8 +230,8 @@ yum install centreon-plugin-Network-Fortinet-Fortigate-Restapi | UNIT | Select the time unit for thresholds. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds | | | | WARNINGEXPIRES | Thresholds | | | | CRITICALEXPIRES | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /expired/i'). You can use the following variables: %{name}, %{status} | %{status} =~ /expired/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{name\}, %\{status\} | %\{status\} =~ /expired/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -333,7 +333,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -384,9 +384,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-vdom | Filter vdom by name. | -| --unknown-health | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-health | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-health | Define the conditions to match for the status to be CRITICAL (Default: '%{status} !~ /success/i'). You can use the following variables: %{status}, %{name} | +| --unknown-health | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-health | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-health | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} !~ /success/i'). You can use the following variables: %\{status\}, %\{name\} | @@ -394,8 +394,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter licenses by name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{status}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /expired/i'). You can use the following variables: %{name}, %{status}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{status\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /expired/i'). You can use the following variables: %\{name\}, %\{status\}. | | --unit | Select the unit for expires threshold. May be 's' for seconds,'m' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'expires'. | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md index da2212ec7dd1..0cbc0b563c8b 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortimail-snmp.md @@ -283,8 +283,8 @@ yum install centreon-plugin-Network-Fortinet-Fortimail-Snmp | Macro | Description | Default value | Mandatory | |:-----------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------|:-----------:| -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | %{ha\_status} ne %{ha\_status\_last} | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | %\{ha_status\} ne %\{ha_status_last\} | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -336,8 +336,8 @@ yum install centreon-plugin-Network-Fortinet-Fortimail-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -469,7 +469,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -550,8 +550,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (Default: 'AES'). | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{ha\_status\_last} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} ne %{ha\_status\_last}'). You can use the following variables: %{ha\_status}, %{ha\_status\_last} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} ne %\{ha_status_last\}'). You can use the following variables: %\{ha_status\}, %\{ha_status_last\} | @@ -591,9 +591,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md index 0a6379e879a1..6cce38595324 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortimanager-snmp.md @@ -235,16 +235,16 @@ yum install centreon-plugin-Network-Fortinet-Fortimanager-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERNAME | Filter by device name (can be a regexp) | | | -| WARNINGDEVICECONFIGSTATUS | Set warning threshold for device configuration status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICECONFIGSTATUS | Set critical threshold for device configuration status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICECONSTATUS | Set critical threshold for device connection status. You can use the following variables: %{status}, %{name} | %{status} =~ /down/i | | -| WARNINGDEVICECONSTATUS | Set warning threshold for device connection status. You can use the following variables: %{status}, %{name} | | | -| WARNINGDEVICEDBSTATUS | Set warning threshold for device DB status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICEDBSTATUS | Set critical threshold for device DB status. You can use the following variables: %{status}, %{name} | | | -| WARNINGDEVICEPOLICYSTATUS | Set warning threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | | | -| CRITICALDEVICEPOLICYSTATUS | Set critical threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | | | -| WARNINGDEVICESTATUS | Set warning threshold for device status. You can use the following variables: %{status}, %{name} | | | -| CRITICALDEVICESTATUS | Set critical threshold for device status You can use the following variables: %{status}, %{name} | | | +| WARNINGDEVICECONFIGSTATUS | Set warning threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICECONFIGSTATUS | Set critical threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICECONSTATUS | Set critical threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /down/i | | +| WARNINGDEVICECONSTATUS | Set warning threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | | | +| WARNINGDEVICEDBSTATUS | Set warning threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICEDBSTATUS | Set critical threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | | | +| WARNINGDEVICEPOLICYSTATUS | Set warning threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | | | +| CRITICALDEVICEPOLICYSTATUS | Set critical threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | | | +| WARNINGDEVICESTATUS | Set warning threshold for device status. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALDEVICESTATUS | Set critical threshold for device status You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -287,7 +287,7 @@ is able to monitor a resource using a command like this one (replace the sample --warning-device-status='' \ --critical-device-status='' \ --warning-device-con-status='' \ - --critical-device-con-status='%{status} =~ /down/i' \ + --critical-device-con-status='%\{status\} =~ /down/i' \ --warning-device-db-status='' \ --critical-device-db-status='' \ --warning-device-config-status='' \ @@ -380,7 +380,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -423,16 +423,16 @@ All available options for each service template are listed below: |:----------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-name | Filter by device name (can be a regexp). | -| --warning-device-status | Set warning threshold for device status. You can use the following variables: %{status}, %{name} | -| --critical-device-status | Set critical threshold for device status You can use the following variables: %{status}, %{name} | -| --warning-device-con-status | Set warning threshold for device connection status. You can use the following variables: %{status}, %{name} | -| --critical-device-con-status | Set critical threshold for device connection status (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{name} | -| --warning-device-db-status | Set warning threshold for device DB status. You can use the following variables: %{status}, %{name} | -| --critical-device-db-status | Set critical threshold for device DB status. You can use the following variables: %{status}, %{name} | -| --warning-device-config-status | Set warning threshold for device configuration status. You can use the following variables: %{status}, %{name} | -| --critical-device-config-status | Set critical threshold for device configuration status. You can use the following variables: %{status}, %{name} | -| --warning-device-policy-package-status | Set warning threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | -| --critical-device-policy-package-status | Set critical threshold for device policy package status. You can use the following variables: %{status}, %{package\_name} | +| --warning-device-status | Set warning threshold for device status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-status | Set critical threshold for device status You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-con-status | Set warning threshold for device connection status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-con-status | Set critical threshold for device connection status (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-db-status | Set warning threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-db-status | Set critical threshold for device DB status. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-config-status | Set warning threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | +| --critical-device-config-status | Set critical threshold for device configuration status. You can use the following variables: %\{status\}, %\{name\} | +| --warning-device-policy-package-status | Set warning threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | +| --critical-device-policy-package-status | Set critical threshold for device policy package status. You can use the following variables: %\{status\}, %\{package_name\} | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md index db3fa3381ec8..df5b4f0ef163 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiswitch-snmp.md @@ -300,8 +300,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -350,7 +350,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -424,7 +424,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -521,9 +521,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md index 01e2509e3d09..d1022ec8c3f9 100644 --- a/pp/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-fortinet-fortiweb-snmp.md @@ -238,8 +238,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiweb-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -264,8 +264,8 @@ yum install centreon-plugin-Network-Fortinet-Fortiweb-Snmp | CRITICALCPULOAD | Thresholds | | | | WARNINGDISKUSAGE | Thresholds | | | | CRITICALDISKUSAGE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_mode} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_mode} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_mode\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_mode\} | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -350,7 +350,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -424,9 +424,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -461,8 +461,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='memory-usage' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_mode} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_mode} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_mode\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_mode\} | | --warning-* --critical-* | Thresholds. Can be: 'disk-usage' (%), 'memory-usage' (%), 'cpu-load' (%). | diff --git a/pp/integrations/plugin-packs/procedures/network-freebox-restapi.md b/pp/integrations/plugin-packs/procedures/network-freebox-restapi.md index 569608c7120e..d750be81cc9d 100644 --- a/pp/integrations/plugin-packs/procedures/network-freebox-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-freebox-restapi.md @@ -85,10 +85,10 @@ You have to authorize the client and generate an app_id and a token to monitor y `curl http:///api/v4/login/authorize -d '{"app_id":"centreon","app_name":"centreon","app_version":"3.0","device_name":"Freebox"}'` - Validate within the Freebox UI and keep the token safe -- Navigate to http:///api/v4/login/authorize/ +- Navigate to http://\/api/v4/login/authorize/\ - Check on the webpage that the application is authorized. -Keep your and obtained token with you as you will need it during the host configuration. +Keep your \ and obtained token with you as you will need it during the host configuration. ## Installing the monitoring connector @@ -235,8 +235,8 @@ yum install centreon-plugin-Network-Freebox-Restapi | Macro | Description | Default value | Mandatory | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------|:-----------:| -| CRITICALDISKSTATUS | Set critical threshold for disk status (default: '%{status} =~ /error/i'). You can use the following variables: %{status} | %{status} =~ /error/i | | -| WARNINGDISKSTATUS | Set warning threshold for disk status. You can use the following variables: %{status} | | | +| CRITICALDISKSTATUS | Set critical threshold for disk status (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\} | %\{status\} =~ /error/i | | +| WARNINGDISKSTATUS | Set warning threshold for disk status. You can use the following variables: %\{status\} | | | | WARNINGFANSPEED | Thresholds | | | | CRITICALFANSPEED | Thresholds | | | | WARNINGTEMPERATURECPUB | Thresholds | | | @@ -245,8 +245,8 @@ yum install centreon-plugin-Network-Freebox-Restapi | CRITICALTEMPERATURECPUM | Thresholds | | | | WARNINGTEMPERATURESWITCH | Thresholds | | | | CRITICALTEMPERATURESWITCH | Thresholds | | | -| WARNINGWIFISTATUS | Set warning threshold for wifi status (default: '%{status} =~ /bad\_param/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /bad\_param/i | | -| CRITICALWIFISTATUS | Set critical threshold for wifi status (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{display} | %{status} =~ /failed/i | | +| WARNINGWIFISTATUS | Set warning threshold for wifi status (default: '%\{status\} =~ /bad\_param/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /bad\_param/i | | +| CRITICALWIFISTATUS | Set critical threshold for wifi status (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /failed/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -332,7 +332,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -391,10 +391,10 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^temperature-cpum$' | -| --warning-wifi-status | Set warning threshold for wifi status (default: '%{status} =~ /bad\_param/i'). You can use the following variables: %{status}, %{display} | -| --critical-wifi-status | Set critical threshold for wifi status (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{display} | -| --warning-disk-status | Set warning threshold for disk status. You can use the following variables: %{status} | -| --critical-disk-status | Set critical threshold for disk status (default: '%{status} =~ /error/i'). You can use the following variables: %{status} | +| --warning-wifi-status | Set warning threshold for wifi status (default: '%\{status\} =~ /bad\_param/i'). You can use the following variables: %\{status\}, %\{display\} | +| --critical-wifi-status | Set critical threshold for wifi status (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-disk-status | Set warning threshold for disk status. You can use the following variables: %\{status\} | +| --critical-disk-status | Set critical threshold for disk status (default: '%\{status\} =~ /error/i'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature-cpum', 'temperature-cpub', 'temperature-switch', 'fan-speed'. | diff --git a/pp/integrations/plugin-packs/procedures/network-fritzbox-upnp.md b/pp/integrations/plugin-packs/procedures/network-fritzbox-upnp.md index 5469a8a71f1b..89ea062e3e0e 100644 --- a/pp/integrations/plugin-packs/procedures/network-fritzbox-upnp.md +++ b/pp/integrations/plugin-packs/procedures/network-fritzbox-upnp.md @@ -275,7 +275,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -322,8 +322,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='uptime' | -| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %{connection\_status}, %{link\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} !~ /^up$/i and %{connection\_status} !~ /^connected$/i'). Can use special variables like: %{connection\_status}, %{link\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING. Can use special variables like: %\{connection_status\}, %\{link_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} !~ /^up$/i and %\{connection_status\} !~ /^connected$/i'). Can use special variables like: %\{connection_status\}, %\{link_status\} | | --unit | Select the unit for uptime threshold. May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is days. | | --warning-* --critical-* | Thresholds. Can be: 'uptime'. | diff --git a/pp/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md b/pp/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md index e6eb972e71c3..eedcf4b58d78 100644 --- a/pp/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-generic-bluecoat-snmp.md @@ -395,7 +395,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-h3c-snmp.md b/pp/integrations/plugin-packs/procedures/network-h3c-snmp.md index a0b293e5b755..0bfc58880f4a 100644 --- a/pp/integrations/plugin-packs/procedures/network-h3c-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-h3c-snmp.md @@ -318,7 +318,7 @@ yum install centreon-plugin-Network-H3c-Snmp | WARNINGIN | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -424,7 +424,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -552,9 +552,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'voltage' (mV), 'module-temperature' (C). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md b/pp/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md index 1e5a69ad76d6..950449e1e48d 100644 --- a/pp/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-hp-moonshot-snmp.md @@ -249,8 +249,8 @@ yum install centreon-plugin-Network-Hp-Moonshot-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -290,7 +290,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -361,7 +361,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -442,9 +442,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-hp-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-hp-standard-snmp.md index 69c70ca0b189..89d3cb4be9a1 100644 --- a/pp/integrations/plugin-packs/procedures/network-hp-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-hp-standard-snmp.md @@ -296,7 +296,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTMCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -317,7 +317,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTMCAST | Thresholds | | | | WARNINGOUTUCAST | Thresholds | | | | CRITICALOUTUCAST | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -376,7 +376,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -385,8 +385,8 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -423,7 +423,7 @@ yum install centreon-plugin-Network-Hp-Standard-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -522,7 +522,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -596,9 +596,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -716,9 +716,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -745,8 +745,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -773,9 +773,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-hp-vc-snmp.md b/pp/integrations/plugin-packs/procedures/network-hp-vc-snmp.md index 8effff77d31a..75c8e1cb013d 100644 --- a/pp/integrations/plugin-packs/procedures/network-hp-vc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-hp-vc-snmp.md @@ -245,7 +245,7 @@ yum install centreon-plugin-Network-Hp-Vc-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -330,7 +330,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -414,9 +414,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-huawei-snmp.md b/pp/integrations/plugin-packs/procedures/network-huawei-snmp.md index fd72cbe51fc7..144841a4b374 100644 --- a/pp/integrations/plugin-packs/procedures/network-huawei-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-huawei-snmp.md @@ -267,8 +267,8 @@ yum install centreon-plugin-Network-Huawei-Snmp | CRITICALOUTPUTPOWER | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | | WARNINGOUTTRAFFIC | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | | CRITICALOUTTRAFFIC | Thresholds (will supersede --\[warning-critical\]-errors). : 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -313,7 +313,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -395,7 +395,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,9 +478,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical metrics. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will supersede --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | diff --git a/pp/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md b/pp/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md index 316e0e29b5cd..acb0216eeff7 100644 --- a/pp/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ibm-bladecenter-snmp.md @@ -344,7 +344,7 @@ yum install centreon-plugin-Network-Ibm-Bladecenter-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -402,7 +402,7 @@ yum install centreon-plugin-Network-Ibm-Bladecenter-Snmp | CRITICALINTRAFFIC | Thresholds | 90 | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -501,7 +501,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -600,9 +600,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -690,9 +690,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-infoblox-snmp.md b/pp/integrations/plugin-packs/procedures/network-infoblox-snmp.md index 816ee2dc3fc8..21e96e5fb509 100644 --- a/pp/integrations/plugin-packs/procedures/network-infoblox-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-infoblox-snmp.md @@ -318,8 +318,8 @@ yum install centreon-plugin-Network-Infoblox-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -340,8 +340,8 @@ yum install centreon-plugin-Network-Infoblox-Snmp | CRITICALCPU2TEMPERATURE | Thresholds | | | | WARNINGCPULOAD | Thresholds | | | | CRITICALCPULOAD | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\} | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | | WARNINGSWAPUSAGE | Thresholds | | | @@ -372,7 +372,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -447,7 +447,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -569,9 +569,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -609,8 +609,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^memory-usage$' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'cpu-load' (%), 'cpu1-temperature', 'cpu2-temperature', 'swap-usage' (%), 'memory-usage' (%). | diff --git a/pp/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md b/pp/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md index 0689f9362890..98359f02b671 100644 --- a/pp/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-juniper-ggsn-snmp.md @@ -303,7 +303,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md b/pp/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md index 3d0cd50e38d0..700c296e5818 100644 --- a/pp/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-juniper-isg-snmp.md @@ -277,7 +277,7 @@ yum install centreon-plugin-Network-Juniper-Isg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -365,7 +365,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -488,9 +488,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md b/pp/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md index 0770b5cb63c1..a88695cf9253 100644 --- a/pp/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-juniper-trapeze-snmp.md @@ -216,8 +216,8 @@ yum install centreon-plugin-Network-Juniper-Trapeze-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{opstatus}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{opstatus} !~ /init\|redundant\|operationnal/'). You can use the following variables: %{opstatus}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{opstatus\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{opstatus\} !~ /init\|redundant\|operationnal/'). You can use the following variables: %\{opstatus\}, %\{display\} | | | | WARNINGTOTAL | Set warning threshold for number of AP linked to the WLC | | | | CRITICALTOTAL | Set critical threshold for number of AP linked to the WLC | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -343,7 +343,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -398,8 +398,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter AP name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{opstatus} !~ /init\|redundant\|operationnal/'). You can use the following variables: %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{opstatus\} !~ /init\|redundant\|operationnal/'). You can use the following variables: %\{opstatus\}, %\{display\} | | --warning-total | Set warning threshold for number of AP linked to the WLC | | --critical-total | Set critical threshold for number of AP linked to the WLC | diff --git a/pp/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md b/pp/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md index 4a21f9fb64c0..768aa7e95fb6 100644 --- a/pp/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-keysight-nvos-restapi.md @@ -268,15 +268,15 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | Macro | Description | Default value | Mandatory | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{class} | %{status} eq "unknown" | | +| UNKNOWNTEMPERATURESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "unknown" | | | WARNINGFANSFAILED | Threshold | | | | CRITICALFANSFAILED | Threshold | | | -| CRITICALPSUSTATUS | Threshold | %{status} eq "bad" | | -| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| CRITICALPSUSTATUS | Threshold | %\{status\} eq "bad" | | +| WARNINGPSUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | WARNINGTEMPERATURE | Threshold | | | | CRITICALTEMPERATURE | Threshold | | | -| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{class} | %{status} eq "warn" | | -| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{class} | %{status} eq "hot" | | +| WARNINGTEMPERATURESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "warn" | | +| CRITICALTEMPERATURESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{class\} | %\{status\} eq "hot" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -284,9 +284,9 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | %{status} =~ /MINOR/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} =~ /MAJOR\|CRITICAL/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | %\{status\} =~ /MINOR/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} =~ /MAJOR\|CRITICAL/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -296,10 +296,10 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------|:-----------:| | FILTERNAME | Filter ports by name (can be a regexp) | | | | FILTERTYPE | Filter ports by type (can be a regexp). You can use the following types: 'Network Port', 'Port Group' and 'Tool Port' | | | -| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /invalid\_software\_version/ | | -| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | %{adminStatus} eq "enabled" and %{operationalStatus} ne "up" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | | | +| WARNINGLICENSESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /invalid\_software\_version/ | | +| CRITICALLICENSESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | %\{adminStatus\} eq "enabled" and %\{operationalStatus\} ne "up" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | | | | WARNINGPACKETSDROPPED | Threshold | | | | CRITICALPACKETSDROPPED | Threshold | | | | WARNINGPACKETSIN | Threshold | | | @@ -328,7 +328,7 @@ yum install centreon-plugin-Network-Keysight-Nvos-Restapi | TIMEZONE | Override the timezone of distant equipment. Can use format: 'Europe/London' or '+0100' | | | | NTPHOSTNAME | Set the NTP hostname (if not set, localtime is used) | | | | NTPPORT | Set the NTP port (default: 123) | | | -| CRITICALNTPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in\_reach\|in\_sync/i') You can use the following variables: %{status} | %{status} !~ /in\_reach\|in\_sync/ | | +| CRITICALNTPSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in\_reach\|in\_sync/i') You can use the following variables: %\{status\} | %\{status\} !~ /in\_reach\|in\_sync/ | | | WARNINGNTPSTATUS | Define the conditions to match for the status to be WARNING | | | | WARNINGOFFSET | Define the time offset (in seconds) that will trigger a WARNING status | | | | CRITICALOFFSET | Define the time offset (in seconds) that will trigger a CRITICAL status | | | @@ -364,15 +364,15 @@ is able to monitor a resource using a command like this one (replace the sample --port='8000' \ --api-username='username' \ --api-password='*****' \ - --unknown-temperature-status='%{status} eq "unknown"' \ - --warning-temperature-status='%{status} eq "warn"' \ - --critical-temperature-status='%{status} eq "hot"' \ + --unknown-temperature-status='%\{status\} eq "unknown"' \ + --warning-temperature-status='%\{status\} eq "warn"' \ + --critical-temperature-status='%\{status\} eq "hot"' \ --warning-temperature='' \ --critical-temperature='' \ --warning-fans-failed='' \ --critical-fans-failed='' \ --warning-psu-status='' \ - --critical-psu-status='%{status} eq "bad"' \ + --critical-psu-status='%\{status\} eq "bad"' \ --verbose ``` @@ -439,7 +439,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -492,12 +492,12 @@ All available options for each service template are listed below: | Option | Description | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default : '%{status} eq "unknown"'). You can use the following variables: %{status}, %{class} | -| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default : '%{status} eq "warn"'). You can use the following variables: %{status}, %{class} | -| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "hot"'); You can use the following variables: %{status}, %{class} | -| --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-psu-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "bad"'); You can use the following variables: %{status}, %{name} | +| --unknown-temperature-status | Define the conditions to match for the status to be UNKNOWN (default : '%\{status\} eq "unknown"'). You can use the following variables: %\{status\}, %\{class\} | +| --warning-temperature-status | Define the conditions to match for the status to be WARNING (default : '%\{status\} eq "warn"'). You can use the following variables: %\{status\}, %\{class\} | +| --critical-temperature-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "hot"'); You can use the following variables: %\{status\}, %\{class\} | +| --unknown-psu-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-psu-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "bad"'); You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature', 'fans-failed'. | @@ -505,9 +505,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /MINOR/i'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /MAJOR\|CRITICAL/i'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /MINOR/i'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /MAJOR\|CRITICAL/i'). You can use the following variables: %\{status\} | @@ -516,12 +516,12 @@ All available options for each service template are listed below: |:--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter ports by name (can be a regexp). | | --filter-type | Filter ports by type (can be a regexp). You can use the following types: 'Network Port', 'Port Group' and 'Tool Port' | -| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-license-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /invalid\_software\_version/'). You can use the following variables: %{status}, %{name} | -| --critical-license-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminStatus} eq "enabled" and %{operationalStatus} ne "up"'). You can use the following variables: %{adminStatus}, %{operationalStatus}, %{name} | +| --unknown-license-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-license-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /invalid\_software\_version/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-license-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminStatus\} eq "enabled" and %\{operationalStatus\} ne "up"'). You can use the following variables: %\{adminStatus\}, %\{operationalStatus\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-out-prct', 'traffic-out', 'packets-out', 'packets-dropped', 'packets-pass', 'packets-insp'. | @@ -531,7 +531,7 @@ All available options for each service template are listed below: |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | --unknown-ntp-status | Define the conditions to match for the status to be UNKNOWN. | | --warning-ntp-status | Define the conditions to match for the status to be WARNING. | -| --critical-ntp-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /in\_reach\|in\_sync/i') You can use the following variables: %{status} | +| --critical-ntp-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /in\_reach\|in\_sync/i') You can use the following variables: %\{status\} | | --warning-offset | Define the time offset (in seconds) that will trigger a WARNING status. | | --critical-offset | Define the time offset (in seconds) that will trigger a CRITICAL status. | | --ntp-hostname | Set the NTP hostname (if not set, localtime is used). | diff --git a/pp/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md b/pp/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md index 67acabce07b2..f28987c6cdb5 100644 --- a/pp/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-lenovo-flexsystem-snmp.md @@ -345,7 +345,7 @@ yum install centreon-plugin-Network-Lenovo-Flexsystem-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -403,7 +403,7 @@ yum install centreon-plugin-Network-Lenovo-Flexsystem-Snmp | CRITICALINTRAFFIC | Thresholds | 90 | | | WARNINGOUTTRAFFIC | Thresholds | 80 | | | CRITICALOUTTRAFFIC | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -502,7 +502,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -603,9 +603,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -693,9 +693,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md b/pp/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md index aa4070c8a85c..fbe7e5941394 100644 --- a/pp/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-lenovo-rackswitch-snmp.md @@ -258,8 +258,8 @@ yum install centreon-plugin-Network-Lenovo-Rackswitch-Snmp | CRITICALFANSPEED | Thresholds | | | | WARNINGSENSORTEMPERATURE | Thresholds | | | | CRITICALSENSORTEMPERATURE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{status} eq "noncritical"'). You can use the following variables: %{status} | %{status} eq "noncritical" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "critical"'). You can use the following variables: %{status} | %{status} eq "critical" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "noncritical"'). You can use the following variables: %\{status\} | %\{status\} eq "noncritical" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "critical"'). You can use the following variables: %\{status\} | %\{status\} eq "critical" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -282,8 +282,8 @@ yum install centreon-plugin-Network-Lenovo-Rackswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -332,7 +332,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -405,7 +405,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -466,9 +466,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} eq "noncritical"'). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "critical"'). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} eq "noncritical"'). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "critical"'). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'sensor-temperature', 'fan-speed'. | @@ -496,9 +496,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-libraesva-snmp.md b/pp/integrations/plugin-packs/procedures/network-libraesva-snmp.md index fa2df2fbe8ba..87387b27503d 100644 --- a/pp/integrations/plugin-packs/procedures/network-libraesva-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-libraesva-snmp.md @@ -289,8 +289,8 @@ yum install centreon-plugin-Network-Libraesva-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -357,8 +357,8 @@ yum install centreon-plugin-Network-Libraesva-Snmp | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{cluster\_status} | | | -| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{cluster\_status} =~ /error/i'). You can use the following variables: %{cluster\_status} | | | +| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{cluster_status\} | | | +| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{cluster_status\} =~ /error/i'). You can use the following variables: %\{cluster_status\} | | | | WARNINGMAILSBOUNCED | Thresholds | | | | CRITICALMAILSBOUNCED | Thresholds | | | | WARNINGMAILSQUEUEIN | Thresholds | | | @@ -461,7 +461,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -535,9 +535,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -641,9 +641,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^mail-sent$' | -| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{cluster\_status} | -| --warning-cluster-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{cluster\_status} | -| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL (default: '%{cluster\_status} =~ /error/i'). You can use the following variables: %{cluster\_status} | +| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{cluster_status\} | +| --warning-cluster-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{cluster_status\} | +| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL (default: '%\{cluster_status\} =~ /error/i'). You can use the following variables: %\{cluster_status\} | | --warning-* --critical-* | Thresholds. Can be: 'mails-sent', 'mails-received', 'mails-rejected', 'mails-bounced', 'mails-queue-in', 'mails-queue-out', 'messages-spam', 'messages-virus', | diff --git a/pp/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md b/pp/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md index 85a32588c502..21a0985930c6 100644 --- a/pp/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-loadbalancers-a10-ax-snmp.md @@ -320,7 +320,7 @@ yum install centreon-plugin-Network-Loadbalancers-A10-AX-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -331,8 +331,8 @@ yum install centreon-plugin-Network-Loadbalancers-A10-AX-Snmp | FILTERNAME | Filter by virtual server name (can be a regexp) | | | | WARNINGCURRENTCON | Warning threshold | | | | CRITICALCURRENTCON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTOTALCON | Warning threshold | | | | CRITICALTOTALCON | Critical threshold | | | | WARNINGTRAFFICIN | Warning threshold | | | @@ -432,7 +432,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -564,9 +564,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -605,8 +605,8 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /down/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /down/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'current-con', 'total-con', 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: 'current-con', 'total-con', 'traffic-in', 'traffic-out'. | | --filter-name | Filter by virtual server name (can be a regexp). | diff --git a/pp/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md b/pp/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md index 649bc1c6776d..13fb5df89928 100644 --- a/pp/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-loadbalancers-f5-bigip-snmp.md @@ -336,10 +336,10 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------|:-----------:| -| CRITICALFAILOVERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{failoverstatus} =~ /unknown/'). You can use the following variables: %{failoverstatus} | %{failoverstatus} =~ /unknown/ | | -| WARNINGFAILOVERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{failoverstatus} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %{syncstatus} | %{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/ | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{syncstatus} | | | +| CRITICALFAILOVERSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{failoverstatus\} =~ /unknown/'). You can use the following variables: %\{failoverstatus\} | %\{failoverstatus\} =~ /unknown/ | | +| WARNINGFAILOVERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{failoverstatus\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %\{syncstatus\} | %\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/ | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{syncstatus\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -380,11 +380,11 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | | | WARNINGCURRENTSERVERCONNECTIONS | Thresholds | | | | CRITICALCURRENTSERVERCONNECTIONS | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -393,15 +393,15 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Default value | Mandatory | |:---------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | | | | WARNINGCURRENTACTIVEMEMBERS | Thresholds | | | | CRITICALCURRENTACTIVEMEMBERS | Thresholds | | | | WARNINGCURRENTSERVERCONNECTIONS | Thresholds | | | | CRITICALCURRENTSERVERCONNECTIONS | Thresholds | | | | WARNINGCURRENTTOTALMEMBERS | Thresholds | | | | CRITICALCURRENTTOTALMEMBERS | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -433,10 +433,10 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp |:------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | UNITS | Units of thresholds for the traffic (Default: '%') ('%', 'b/s') | % | | | FILTERNAME | Filter by trunks name (regexp can be used) | | | -| UNKNOWNINTERFACESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | -| WARNINGINTERFACESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | -| CRITICALINTERFACESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNINTERFACESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGINTERFACESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALINTERFACESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGINTERFACESTOTAL | Thresholds | | | | CRITICALINTERFACESTOTAL | Thresholds | | | | WARNINGPACKETSDROPIN | Thresholds | | | @@ -447,8 +447,8 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | CRITICALPACKETSERRORIN | Thresholds | | | | WARNINGPACKETSERROROUT | Thresholds | | | | CRITICALPACKETSERROROUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /uninitialized\|down/'). You can use the following variables: %{status}, %{display} | %{status} =~ /uninitialized\|down/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /uninitialized\|down/'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} =~ /uninitialized\|down/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -461,9 +461,9 @@ yum install centreon-plugin-Network-Loadbalancers-F5-Bigip-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------|:-----------:| | FILTER | Filter by name (regexp can be used) | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "yellow" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | %{state} eq "enabled" and %{status} eq "red" | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "yellow" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | %\{state\} eq "enabled" and %\{status\} eq "red" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -563,7 +563,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -660,10 +660,10 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). | -| --warning-sync-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{syncstatus} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%{syncstatus} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %{syncstatus} | -| --warning-failover-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{failoverstatus} | -| --critical-failover-status | Define the conditions to match for the status to be CRITICAL (Default: '%{failoverstatus} =~ /unknown/'). You can use the following variables: %{failoverstatus} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{syncstatus\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: '%\{syncstatus\} =~ /unknown\|syncFailed\|syncDisconnected\|incompatibleVersion/'). You can use the following variables: %\{syncstatus\} | +| --warning-failover-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{failoverstatus\} | +| --critical-failover-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{failoverstatus\} =~ /unknown/'). You can use the following variables: %\{failoverstatus\} | @@ -719,9 +719,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current-server-connections'. | @@ -730,12 +730,12 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{membersAllDisabled} eq "no" and %{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{membersAllDisabled}, %{display} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{status}, %{poolName}, %{nodeName} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{membersAllDisabled\} eq "no" and %\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{membersAllDisabled\}, %\{display\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{status\}, %\{poolName\}, %\{nodeName\} | | --warning-* --critical-* | Thresholds. Can be: 'current-server-connections', 'current-active-members', 'current-total-members'. | @@ -781,12 +781,12 @@ All available options for each service template are listed below: | --units-traffic | Units of thresholds for the traffic (Default: '%') ('%', 'b/s'). | | --speed | Set trunk speed in Mbps (Default: sysTrunkOperBw). If not setand sysTrunkOperBw OID value is 0, percentage thresholds will not be applied on traffic metrics. | | --add-interfaces | Monitor trunk interfaces. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /uninitialized\|down/'). You can use the following variables: %{status}, %{display} | -| --unknown-interface-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-interface-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-interface-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /uninitialized\|down/'). You can use the following variables: %\{status\}, %\{display\} | +| --unknown-interface-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-interface-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-interface-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'packets-error-in' (%), 'packets-error-out' (%), 'packets-drop-in' (%), 'packets-drop-out' (%), 'total-interfaces'. | @@ -795,9 +795,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by name (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{state}, %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{state} eq "enabled" and %{status} eq "yellow"'). You can use the following variables: %{state}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{state} eq "enabled" and %{status} eq "red"'). You can use the following variables: %{state}, %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{state\} eq "enabled" and %\{status\} eq "yellow"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{state\} eq "enabled" and %\{status\} eq "red"'). You can use the following variables: %\{state\}, %\{status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'current-client-connections'. | diff --git a/pp/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md b/pp/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md index 2d5297c270f7..5e414801e2f6 100644 --- a/pp/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-loadbalancers-kemp-snmp.md @@ -302,10 +302,10 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | | | -| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | | | -| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| WARNINGSYNCSTATUS | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSYNCSTATUS | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -338,8 +338,8 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALINTRAFFIC | Critical threshold | | | | WARNINGOUTRAFFIC | Warning threshold | | | | CRITICALOUTRAFFIC | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /inService\|disabled/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /inService\|disabled/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -376,7 +376,7 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -391,8 +391,8 @@ yum install centreon-plugin-Network-Loadbalancers-Kemp-Snmp | CRITICALINTRAFFIC | Critical threshold | | | | WARNINGOUTRAFFIC | Warning threshold | | | | CRITICALOUTRAFFIC | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /inService\|disabled\|redirect/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /inService\|disabled\|redirect/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -417,7 +417,7 @@ is able to monitor a resource using a command like this one (replace the sample --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='90' \ --warning-out-traffic='80' \ @@ -483,7 +483,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -558,10 +558,10 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^ha-status$' | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | -| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %{status}, %{display} | -| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %{status}, %{display} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --warning-sync-status | Define the conditions to match for the status to be WARNING (default: none). You can use the following variables: %\{status\}, %\{display\} | +| --critical-sync-status | Define the conditions to match for the status to be CRITICAL (default: none). You can use the following variables: %\{status\}, %\{display\} | @@ -602,8 +602,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter real server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | | --critical-* | Critical threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | @@ -632,9 +632,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -675,8 +675,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^status$' | | --filter-name | Filter virtual server name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /inService\|disabled\|redirect/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | | --critical-* | Critical threshold. Can be: 'active', 'in-traffic' (b/s), 'out-traffic' (b/s). | diff --git a/pp/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md b/pp/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md index 64e769991989..45d327993af1 100644 --- a/pp/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-loadbalancers-netscaler-snmp.md @@ -485,7 +485,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -564,12 +564,12 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%{ha\_status} =~ /unknown/i'). Can use special variables like: %{ha\_status} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %{ha\_status}, %{ha\_mode} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. (Default: '%{ha\_status} =~ /down\|partialFail\|monitorFail\|completeFail\|partialFailSsl\|routem onitorFail/i'). Can use special variables like: %{ha\_status}, %{ha\_mode} | -| --unknown-peer-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%{peer\_status} =~ /unknown/i'). Can use special variables like: %{peer\_status}, %{ha\_mode} | -| --warning-peer-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %{peer\_status} | -| --critical-peer-status | Define the conditions to match for the status to be CRITICAL. (Default: ''). Can use special variables like: %{peer\_status} | +| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%\{ha_status\} =~ /unknown/i'). Can use special variables like: %\{ha_status\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %\{ha_status\}, %\{ha_mode\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. (Default: '%\{ha_status\} =~ /down\|partialFail\|monitorFail\|completeFail\|partialFailSsl\|routem onitorFail/i'). Can use special variables like: %\{ha_status\}, %\{ha_mode\} | +| --unknown-peer-status | Define the conditions to match for the status to be UNKNOWN. (Default: '%\{peer_status\} =~ /unknown/i'). Can use special variables like: %\{peer_status\}, %\{ha_mode\} | +| --warning-peer-status | Define the conditions to match for the status to be WARNING. (Default: ''). Can use special variables like: %\{peer_status\} | +| --critical-peer-status | Define the conditions to match for the status to be CRITICAL. (Default: ''). Can use special variables like: %\{peer_status\} | @@ -629,9 +629,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-meru-snmp.md b/pp/integrations/plugin-packs/procedures/network-meru-snmp.md index 8bc20e31195a..ed90ba984dc9 100644 --- a/pp/integrations/plugin-packs/procedures/network-meru-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-meru-snmp.md @@ -275,8 +275,8 @@ yum install centreon-plugin-Network-Meru-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -382,7 +382,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -470,9 +470,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md b/pp/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md index 8043de3a1551..0f606db7a0bb 100644 --- a/pp/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-microsens-g6-snmp.md @@ -339,8 +339,8 @@ yum install centreon-plugin-Network-Microsens-G6-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -387,8 +387,8 @@ yum install centreon-plugin-Network-Microsens-G6-Snmp | CRITICALINPUTPOWER | Thresholds | | | | WARNINGOUTPUTPOWER | Thresholds | | | | CRITICALOUTPUTPOWER | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %{status}, %{port}, %{location} | %{status} =~ /txFailure\|lossOfSignal\|readError/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{location} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %\{status\}, %\{port\}, %\{location\} | %\{status\} =~ /txFailure\|lossOfSignal\|readError/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{location\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -422,7 +422,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --filter-port='' \ --warning-status='' \ - --critical-status='%{status} =~ /txFailure|lossOfSignal|readError/' \ + --critical-status='%\{status\} =~ /txFailure|lossOfSignal|readError/' \ --warning-temperature='' \ --critical-temperature='' \ --warning-input-power='' \ @@ -490,7 +490,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -596,9 +596,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -644,8 +644,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter ports by index (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{location} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %{status}, %{port}, %{location} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{location\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /txFailure\|lossOfSignal\|readError/'). You can use the following variables: %\{status\}, %\{port\}, %\{location\} | | --warning-* --critical-* | Thresholds. Can be: 'temperature', 'input-power', 'output-power'. | diff --git a/pp/integrations/plugin-packs/procedures/network-mikrotik-snmp.md b/pp/integrations/plugin-packs/procedures/network-mikrotik-snmp.md index 333c5a463daf..96e4a4499ffa 100644 --- a/pp/integrations/plugin-packs/procedures/network-mikrotik-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-mikrotik-snmp.md @@ -356,8 +356,8 @@ yum install centreon-plugin-Network-Mikrotik-Snmp | CRITICALOUTVOLUME | | | | | WARNINGSPEED | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | CRITICALSPEED | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | CRITICALTOTALADMINDOWN | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | | WARNINGTOTALADMINUP | Thresholds (will superseed --\[warning\|critical\]-errors). : 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%) | | | @@ -492,7 +492,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -589,9 +589,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will superseed --\[warning\|critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'in-tooshort' (%), 'in-toolong' (%), 'in-fcserror' (%), 'in-alignerror' (%), 'in-fragment' (%), 'in-overflow' (%), 'in-unknownop' (%), 'in-lengtherror' (%), 'in-codeerror' (%), 'in-carriererror' (%), 'in-jabber' (%), 'in-drop' (%), 'out-tooshort' (%), 'out-toolong' (%), 'out-underrun' (%), 'out-collision' (%), 'out-excessivecollision' (%), 'out-multiplecollision' (%), 'out-singlecollision' (%), 'out-excessivedeferred' (%),'out-deferred' (%), 'out-latecollision' (%), 'out-totalcollision' (%), 'out-drop' (%), 'out-jabber' (%), 'out-fcserror' (%), 'out-fragment' (%). | diff --git a/pp/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md b/pp/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md index 8388a7dc87be..b32bfcf1e359 100644 --- a/pp/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-mitel-3300icp-snmp.md @@ -285,7 +285,7 @@ yum install centreon-plugin-Network-Mitel-3300icp-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -396,7 +396,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,9 +478,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md b/pp/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md index 6431664db0e9..ceac7c3aabef 100644 --- a/pp/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-moxa-switch-snmp.md @@ -276,7 +276,7 @@ yum install centreon-plugin-Network-Switchs-Moxa-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | #NOM? | | @@ -371,7 +371,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -460,9 +460,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md index 6bbfb5197fa0..c8172fa0589d 100644 --- a/pp/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-netgear-mseries-snmp.md @@ -268,8 +268,8 @@ yum install centreon-plugin-Network-Netgear-Mseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -305,7 +305,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -377,7 +377,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -473,9 +473,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md index baa665ce4878..60df0258ce67 100644 --- a/pp/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-netgear-sseries-snmp.md @@ -269,8 +269,8 @@ yum install centreon-plugin-Network-Netgear-Sseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -310,7 +310,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -382,7 +382,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -477,9 +477,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md b/pp/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md index 5339e114e4cd..3ca5e0bd161f 100644 --- a/pp/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-nokia-isam-snmp.md @@ -267,14 +267,14 @@ yum install centreon-plugin-Network-Nokia-Isam-Snmp | Macro | Description | Default value | Mandatory | |:------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| DISPLAYNAME | Define the name to display. Available macros: %{SvcDescription}, %{IfName}, %{SapEncapName}, %{SapDescription}, %{SapPortId}. | %{SvcDescription}.%{IfName}.%{SapEncapName} | | +| DISPLAYNAME | Define the name to display. Available macros: %\{SvcDescription\}, %\{IfName\}, %\{SapEncapName\}, %\{SapDescription\}, %\{SapPortId\}. | %\{SvcDescription\}.%\{IfName\}.%\{SapEncapName\} | | | FILTERNAME | Filter by Service Access Point (SAP) name (can be a regexp) | | | | WARNINGINTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALINTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | WARNINGOUTTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALOUTTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default: '%{admin} =~ /up/i and %{status} !~ /up/i'. You can use the following variables: %{admin}, %{status}, %{display} | %{admin} =~ /up/i and %{status} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default: '%\{admin\} =~ /up/i and %\{status\} !~ /up/i'. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | %\{admin\} =~ /up/i and %\{status\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | | | WARNINGTOTALINTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | CRITICALTOTALINTRAFFIC | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | | WARNINGTOTALOUTTRAFFIC | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic' | | | @@ -291,8 +291,8 @@ yum install centreon-plugin-Network-Nokia-Isam-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -393,7 +393,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -479,15 +479,15 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --display-name | Define the name to display (default: '%{SvcDescription}.%{IfName}.%{SapEncapName}'). Other available macros: %{SapDescription}, %{SapPortId} | +| --display-name | Define the name to display (default: '%\{SvcDescription\}.%\{IfName\}.%\{SapEncapName\}'). Other available macros: %\{SapDescription\}, %\{SapPortId\} | | --filter-name | Filter by Service Access Point (SAP) name (can be a regexp). | | --speed-in | Define the actual maximum incoming traffic speed you can have on the interfaces in megabits per second. | | --speed-out | Define the actual maximum outgoing traffic speed you can have on the interfaces in megabits per second. | | --speed-total-in | Define the actual maximum total incoming traffic speed you can have on the interfaces in megabits per second. | | --speed-total-out | Define the actual maximum total outgoing traffic speed you can have on the interfaces in megabits per second. | | --units-traffic | Define the unit to use to apply to thresholds (default: '%') ('%', 'b/s'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin}, %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Default: '%{admin} =~ /up/i and %{status} !~ /up/i'. You can use the following variables: %{admin}, %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Default: '%\{admin\} =~ /up/i and %\{status\} !~ /up/i'. You can use the following variables: %\{admin\}, %\{status\}, %\{display\} | | --warning-* | Warning thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic'. | | --critical-* | Critical thresholds for: 'total-in-traffic', 'total-out-traffic', 'in-traffic', 'out-traffic'. | | --reload-cache-time | Time in seconds before reloading the cache file (default: 300). | @@ -517,9 +517,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md b/pp/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md index d65ae45671e9..3a1f9b44f797 100644 --- a/pp/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-nokia-timos-snmp.md @@ -336,8 +336,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | ACTIVEPREFIXES | Threshold | | | | SENTPREFIXES | Threshold | | | | RECEIVEDPREFIXES | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | %{state} =~ /outOfService/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | %\{state\} =~ /outOfService/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -376,8 +376,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters | | @@ -388,8 +388,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | FILTERNAME | Filter by instance name (can be a regexp) | | | | TOTALINTINSERVICE | Threshold | | | | TOTALINTOUTSERVICE | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state} | %{admin\_state} eq "inService" and %{oper\_state} !~ /inService\|transition/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\} | %\{admin_state\} eq "inService" and %\{oper_state\} !~ /inService\|transition/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -405,8 +405,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALPEERTUNNELTOTAL | Threshold | | | | WARNINGPEERTUNNELTOTALSESSIONS | Threshold | | | | CRITICALPEERTUNNELTOTALSESSIONS | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | | | | WARNINGVRTRTUNNELACTIVESESSIONS | Threshold | | | | CRITICALVRTRTUNNELACTIVESESSIONS | Threshold | | | | WARNINGVRTRTUNNELTOTAL | Threshold | | | @@ -429,8 +429,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | CRITICALIPV4ACTIVETARGETADJ | Threshold | | | | WARNINGIPV4OPERDOWNEVENTS | Threshold | | | | CRITICALIPV4OPERDOWNEVENTS | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | %{admin\_state} eq "inService" and %{ipv4\_oper\_state} !~ /inService\|transition/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | %\{admin_state\} eq "inService" and %\{ipv4_oper_state\} !~ /inService\|transition/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -452,8 +452,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | TRAFFICINABOVECIR | Threshold | | | | TRAFFICOUTBELOWCIR | Threshold | | | | TRAFFICOUTABOVECIR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{display} | %{admin\_state} eq "up" and %{oper\_state} !~ /up/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{display\} | %\{admin_state\} eq "up" and %\{oper_state\} !~ /up/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -462,8 +462,8 @@ yum install centreon-plugin-Network-Nokia-Timos-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------|:-----------:| | FILTERNAME | Filter alarm input (tmnxSasAlarmInputDescription) (can be a regexp) | | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{alarm\_input\_admin\_state}, %{alarm\_input\_status}, %{alarm\_output\_severity} | %{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /minor/ | | -| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | %{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /major\|critical/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{alarm_input_admin_state\}, %\{alarm_input_status\}, %\{alarm_output_severity\} | %\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /minor/ | | +| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | %\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /major\|critical/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -499,7 +499,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -609,7 +609,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -645,8 +645,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'active-prefixes', 'sent-prefixes', 'received-prefixes'. | | --critical-* | Critical threshold. Can be: 'active-prefixes', 'sent-prefixes', 'received-prefixes'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /outOfService/') You can use the following variables: %{display}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /outOfService/') You can use the following variables: %\{display\}, %\{state\} | | --filter-name | Filter by BGP name (can be a regexp). Syntax: VrtrName:peeraddr:peerAS:description | @@ -669,7 +669,7 @@ All available options for each service template are listed below: | --no-component | Define the expected status if no components are found (default: critical). | | --threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,\[instance,\]status,regexp). Example: --threshold-overload='entity,fan..*,CRITICAL,booting' | | --warning | Set warning threshold (syntax: type,regexp,threshold) Example: --warning='temperature,.*,20' | -| --critical | Set critical threshold (syntax: type,regexp,threshold) Example: --critical='temperature,.*,30' package network::nokia::timos::snmp::mode::components::entity; use strict; use warnings; my %map\_class = ( 1 =\> 'other', 2 =\> 'unknown', 3 =\> 'physChassis', 4 =\> 'container', 5 =\> 'powerSupply', 6 =\> 'fan', 7 =\> 'sensor', 8 =\> 'ioModule', 9 =\> 'cpmModule', 10 =\> 'fabricModule', 11 =\> 'mdaModule', 12 =\> 'flashDiskModule', 13 =\> 'port', 14 =\> 'mcm', 15 =\> 'ccm', 16 =\> 'oesCard', 17 =\> 'oesControlCard', 18 =\> 'oesUserPanel', 19 =\> 'alarmInputModule', ); my %map\_truth = (1 =\> 'true', 2 =\> 'false'); my %map\_oper\_state = ( 1 =\> 'unknown', 2 =\> 'inService', 3 =\> 'outOfService', 4 =\> 'diagnosing', 5 =\> 'failed', 6 =\> 'booting', 7 =\> 'empty', 8 =\> 'provisioned', 9 =\> 'unprovisioned', 10 =\> 'upgrade', 11 =\> 'downgrade', 12 =\> 'inServiceUpgrade', 13 =\> 'inServiceDowngrade', 14 =\> 'resetPending', 15 =\> 'softReset', 16 =\> 'preExtension', ); my $mapping = { tmnxHwClass =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.7', map =\> \%map\_class }, tmnxHwName =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.8' }, tmnxHwOperState =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.16', map =\> \%map\_oper\_state }, tmnxHwTempSensor =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.17', map =\> \%map\_truth }, tmnxHwTemperature =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.18' }, tmnxHwTempThreshold =\> { oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.19' }, }; sub load { my ($self) = @\_; push @{$self-\>{request}}, { oid =\> $mapping-\>{tmnxHwClass}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwName}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTempSensor}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwOperState}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTemperature}-\>{oid} }, { oid =\> $mapping-\>{tmnxHwTempThreshold}-\>{oid} }; } sub check { my ($self) = @\_; $self-\>{output}-\>output\_add(long\_msg =\> "Checking entities"); $self-\>{components}-\>{entity} = {name =\> 'entity', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'entity')); my ($exit, $warn, $crit, $checked); foreach my $oid ($self-\>{snmp}-\>oid\_lex\_sort(keys %{$self-\>{results}})) { next if ($oid !~ /^$mapping-\>{tmnxHwName}-\>{oid}\.(.*)$/); my $instance = $1; my $result = $self-\>{snmp}-\>map\_instance(mapping =\> $mapping, results =\> $self-\>{results}, instance =\> $instance); next if ($self-\>check\_filter(section =\> 'entity', instance =\> $result-\>{tmnxHwClass} . '.' . $instance)); $self-\>{components}-\>{entity}-\>{total}++; $self-\>{output}-\>output\_add( long\_msg =\> sprintf( "%s '%s' status is '%s' \[instance = %s, temperature = %s\]", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwOperState}, $result-\>{tmnxHwClass} . '.' . $instance, $result-\>{tmnxHwTempSensor} eq 'true' ? $result-\>{tmnxHwTemperature} : '-' ) ); $exit = $self-\>get\_severity(label =\> 'default', section =\> 'entity', instance =\> $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwOperState}); if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf("%s '%s' status is '%s'", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwOperState})); } next if ($result-\>{tmnxHwTempSensor} eq 'false'); ($exit, $warn, $crit, $checked) = $self-\>get\_severity\_numeric(section =\> 'temperature', instance =\> $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwTemperature}); if ($checked == 0 && $result-\>{tmnxHwTempThreshold} != -1 ) { $self-\>{perfdata}-\>threshold\_validate(label =\> 'critical-temperature-instance-' . $result-\>{tmnxHwClass} . '.' . $instance, value =\> $result-\>{tmnxHwTempThreshold}); $exit = $self-\>{perfdata}-\>threshold\_check(value =\> $result-\>{tmnxHwTemperature}, threshold =\> \[ { label =\> 'critical-temperature-instance-' . $instance, exit\_litteral =\> 'critical' }\]); $warn = undef; $crit = $self-\>{perfdata}-\>get\_perfdata\_for\_output(label =\> 'critical-temperature-instance-' . $result-\>{tmnxHwClass} . '.' . $instance); } if (!$self-\>{output}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) { $self-\>{output}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf( "%s '%s' temperature is '%s' C", $result-\>{tmnxHwClass}, $result-\>{tmnxHwName}, $result-\>{tmnxHwTemperature} ) ); } $self-\>{output}-\>perfdata\_add( label =\> 'temperature', unit =\> 'C', nlabel =\> 'hardware.entity.temperature.celsius', instances =\> $result-\>{tmnxHwName}, value =\> $result-\>{tmnxHwTemperature}, warning =\> $warn, critical =\> $crit ); } } 1; | +| --critical | Set critical threshold (syntax: type,regexp,threshold) Example: --critical='temperature,.*,30' package network::nokia::timos::snmp::mode::components::entity; use strict; use warnings; my %map\_class = ( 1 =\> 'other', 2 =\> 'unknown', 3 =\> 'physChassis', 4 =\> 'container', 5 =\> 'powerSupply', 6 =\> 'fan', 7 =\> 'sensor', 8 =\> 'ioModule', 9 =\> 'cpmModule', 10 =\> 'fabricModule', 11 =\> 'mdaModule', 12 =\> 'flashDiskModule', 13 =\> 'port', 14 =\> 'mcm', 15 =\> 'ccm', 16 =\> 'oesCard', 17 =\> 'oesControlCard', 18 =\> 'oesUserPanel', 19 =\> 'alarmInputModule', ); my %map\_truth = (1 =\> 'true', 2 =\> 'false'); my %map\_oper\_state = ( 1 =\> 'unknown', 2 =\> 'inService', 3 =\> 'outOfService', 4 =\> 'diagnosing', 5 =\> 'failed', 6 =\> 'booting', 7 =\> 'empty', 8 =\> 'provisioned', 9 =\> 'unprovisioned', 10 =\> 'upgrade', 11 =\> 'downgrade', 12 =\> 'inServiceUpgrade', 13 =\> 'inServiceDowngrade', 14 =\> 'resetPending', 15 =\> 'softReset', 16 =\> 'preExtension', ); my $mapping = \{ tmnxHwClass =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.7', map =\> \%map\_class \}, tmnxHwName =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.8' \}, tmnxHwOperState =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.16', map =\> \%map\_oper\_state \}, tmnxHwTempSensor =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.17', map =\> \%map\_truth \}, tmnxHwTemperature =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.18' \}, tmnxHwTempThreshold =\> \{ oid =\> '.1.3.6.1.4.1.6527.3.1.2.2.1.8.1.19' \}, \}; sub load \{ my ($self) = @\_; push @\{$self-\>\{request\}\}, \{ oid =\> $mapping-\>\{tmnxHwClass\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwName\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTempSensor\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwOperState\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTemperature\}-\>\{oid\} \}, \{ oid =\> $mapping-\>\{tmnxHwTempThreshold\}-\>\{oid\} \}; \} sub check \{ my ($self) = @\_; $self-\>\{output\}-\>output\_add(long\_msg =\> "Checking entities"); $self-\>\{components\}-\>\{entity\} = \{name =\> 'entity', total =\> 0, skip =\> 0}; return if ($self-\>check\_filter(section =\> 'entity')); my ($exit, $warn, $crit, $checked); foreach my $oid ($self-\>\{snmp\}-\>oid\_lex\_sort(keys %\{$self-\>\{results\}\})) \{ next if ($oid !~ /^$mapping-\>\{tmnxHwName\}-\>\{oid\}\.(.*)$/); my $instance = $1; my $result = $self-\>\{snmp\}-\>map\_instance(mapping =\> $mapping, results =\> $self-\>\{results\}, instance =\> $instance); next if ($self-\>check\_filter(section =\> 'entity', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance)); $self-\>\{components\}-\>\{entity\}-\>\{total\}++; $self-\>\{output\}-\>output\_add( long\_msg =\> sprintf( "%s '%s' status is '%s' \[instance = %s, temperature = %s\]", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwOperState\}, $result-\>\{tmnxHwClass\} . '.' . $instance, $result-\>\{tmnxHwTempSensor\} eq 'true' ? $result-\>\{tmnxHwTemperature\} : '-' ) ); $exit = $self-\>get\_severity(label =\> 'default', section =\> 'entity', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwOperState\}); if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf("%s '%s' status is '%s'", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwOperState\})); \} next if ($result-\>\{tmnxHwTempSensor\} eq 'false'); ($exit, $warn, $crit, $checked) = $self-\>get\_severity\_numeric(section =\> 'temperature', instance =\> $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwTemperature\}); if ($checked == 0 && $result-\>\{tmnxHwTempThreshold\} != -1 ) \{ $self-\>\{perfdata\}-\>threshold\_validate(label =\> 'critical-temperature-instance-' . $result-\>\{tmnxHwClass\} . '.' . $instance, value =\> $result-\>\{tmnxHwTempThreshold\}); $exit = $self-\>\{perfdata\}-\>threshold\_check(value =\> $result-\>\{tmnxHwTemperature\}, threshold =\> \[ \{ label =\> 'critical-temperature-instance-' . $instance, exit\_litteral =\> 'critical' \}\]); $warn = undef; $crit = $self-\>\{perfdata\}-\>get\_perfdata\_for\_output(label =\> 'critical-temperature-instance-' . $result-\>\{tmnxHwClass\} . '.' . $instance); \} if (!$self-\>\{output\}-\>is\_status(value =\> $exit, compare =\> 'ok', litteral =\> 1)) \{ $self-\>\{output\}-\>output\_add( severity =\> $exit, short\_msg =\> sprintf( "%s '%s' temperature is '%s' C", $result-\>\{tmnxHwClass\}, $result-\>\{tmnxHwName\}, $result-\>\{tmnxHwTemperature\} ) ); \} $self-\>\{output\}-\>perfdata\_add( label =\> 'temperature', unit =\> 'C', nlabel =\> 'hardware.entity.temperature.celsius', instances =\> $result-\>\{tmnxHwName\}, value =\> $result-\>\{tmnxHwTemperature\}, warning =\> $warn, critical =\> $crit ); \} \} 1; | | --warning-count-* | Define the warning threshold for the number of components of one type (replace '*' with the component type). | | --critical-count-* | Define the critical threshold for the number of components of one type (replace '*' with the component type). | @@ -699,9 +699,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -731,8 +731,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'total-int-inservice', 'total-int-outservice'. | | --critical-* | Critical threshold. Can be: 'total-int-inservice', 'total-int-outservice'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{oper\_state}, %{admin\_state}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "inService" and %{oper\_state} !~ /inService\|transition/'). You can use the following variables: %{display}, %{oper\_state}, %{admin\_state}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "inService" and %\{oper_state\} !~ /inService\|transition/'). You can use the following variables: %\{display\}, %\{oper_state\}, %\{admin_state\}. | | --filter-name | Filter by instance name (can be a regexp). | @@ -743,8 +743,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'vrtr-tunnel-total', 'vrtr-tunnel-active-sessions', 'vrtr-tunnel-total-sessions', 'peer-tunnel-total', 'peer-tunnel-active-sessions', 'peer-tunnel-total-sessions'. | | --critical-* | Critical threshold. Can be: 'vrtr-tunnel-total', 'vrtr-tunnel-active-sessions', 'vrtr-tunnel-total-sessions', 'peer-tunnel-total', 'peer-tunnel-active-sessions', 'peer-tunnel-total-sessions'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{display}, %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{display\}, %\{state\} | | --filter-vrtr-name | Filter by vrtr name (can be a regexp). | | --filter-peer-addr | Filter by peer addr (can be a regexp). | @@ -756,8 +756,8 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --warning-* | Warning threshold. Can be: 'ipv4-oper-down-events', 'ipv4-active-sessions', 'ipv4-active-link-adj', 'ipv4-active-target-adj'. | | --critical-* | Critical threshold. Can be: 'ipv4-oper-down-events', 'ipv4-active-sessions', 'ipv4-active-link-adj', 'ipv4-active-target-adj'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "inService" and %{ipv4\_oper\_state} !~ /inService\|transition/'). You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "inService" and %\{ipv4_oper_state\} !~ /inService\|transition/'). You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | --filter-name | Filter by LDP instance name (can be a regexp). | @@ -775,8 +775,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admin\_state} eq "up" and %{oper\_state} !~ /up/'). You can use the following variables: %{status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admin_state\} eq "up" and %\{oper_state\} !~ /up/'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'traffic-in-above-cir', 'traffic-in-below-cir', 'traffic-out-above-cir', 'traffic-out-below-cir'. | | --critical-* | Critical threshold. Can be: 'traffic-in-above-cir', 'traffic-in-below-cir', 'traffic-out-above-cir', 'traffic-out-below-cir'. | | --filter-name | Filter by virtual server name (can be a regexp). | @@ -787,8 +787,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Set warning threshold for status. (Default: '%{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /minor/') You can use the following variables: %{alarm\_input\_admin\_state}, %{alarm\_input\_status}, %{alarm\_output\_severity} | -| --critical-status | Set critical threshold for status (Default: '%{alarm\_input\_admin\_state} eq "up" and %{alarm\_input\_status} eq "alarm" and %{alarm\_output\_severity} =~ /major\|critical/'). You can use the following variables: %{ipv4\_oper\_state}, %{admin\_state}, %{display} | +| --warning-status | Set warning threshold for status. (Default: '%\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /minor/') You can use the following variables: %\{alarm_input_admin_state\}, %\{alarm_input_status\}, %\{alarm_output_severity\} | +| --critical-status | Set critical threshold for status (Default: '%\{alarm_input_admin_state\} eq "up" and %\{alarm_input_status\} eq "alarm" and %\{alarm_output_severity\} =~ /major\|critical/'). You can use the following variables: %\{ipv4_oper_state\}, %\{admin_state\}, %\{display\} | | --filter-name | Filter alarm input (tmnxSasAlarmInputDescription) (can be a regexp). | diff --git a/pp/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md index b12e625fdf93..d483436f96a1 100644 --- a/pp/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-nortel-standard-snmp.md @@ -343,7 +343,7 @@ yum install centreon-plugin-Network-Nortel-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -352,11 +352,11 @@ yum install centreon-plugin-Network-Nortel-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------|:-----------:| | UNIT | Select the time unit for the performance data and thresholds.May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds | s | | -| UNKNOWNUNITSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{operState}, %{adminState}, %{serial} | | | +| UNKNOWNUNITSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | | | | WARNINGUNITDETECTED | Thresholds | | | | CRITICALUNITDETECTED | Thresholds | | | -| WARNINGUNITSTATUS | Define the conditions to match for the status to be WARNING (default: '%{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | %{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i | | -| CRITICALUNITSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "enable" && %{operState} =~ /fatalErr/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | %{adminState} eq "enable" && %{operState} =~ /fatalErr/i | | +| WARNINGUNITSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | %\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i | | +| CRITICALUNITSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | %\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i | | | WARNINGUNITSTOTAL | Thresholds | | | | CRITICALUNITSTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -481,7 +481,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -582,9 +582,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -610,9 +610,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-unit-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{operState}, %{adminState}, %{serial} | -| --warning-unit-status | Define the conditions to match for the status to be WARNING (default: '%{adminState} eq "enable" && %{operState} =~ /nonFatalErr\|warning/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | -| --critical-unit-status | Define the conditions to match for the status to be CRITICAL (default: '%{adminState} eq "enable" && %{operState} =~ /fatalErr/i'). You can use the following variables: %{operState}, %{adminState}, %{serial} | +| --unknown-unit-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | +| --warning-unit-status | Define the conditions to match for the status to be WARNING (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /nonFatalErr\|warning/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | +| --critical-unit-status | Define the conditions to match for the status to be CRITICAL (default: '%\{adminState\} eq "enable" && %\{operState\} =~ /fatalErr/i'). You can use the following variables: %\{operState\}, %\{adminState\}, %\{serial\} | | --unit | Select the time unit for the performance data and thresholds.May be 's' for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds. | | --warning-* --critical-* | Thresholds. Can be: 'units-total', 'unit-detected'. | @@ -641,9 +641,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-oneaccess-snmp.md b/pp/integrations/plugin-packs/procedures/network-oneaccess-snmp.md index 7541b3449edb..b5ee2bd675bc 100644 --- a/pp/integrations/plugin-packs/procedures/network-oneaccess-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-oneaccess-snmp.md @@ -244,8 +244,8 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | CRITICALMODULECELLRADIOSNR | Thresholds | | | | WARNINGMODULESCELLRADIODETECTED | Thresholds | | | | CRITICALMODULESCELLRADIODETECTED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{signalQuality} =~ /poor/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | %{signalQuality} =~ /poor/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | %{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{signalQuality\} =~ /poor/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | %\{signalQuality\} =~ /poor/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | %\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -277,8 +277,8 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -298,7 +298,7 @@ yum install centreon-plugin-Network-Oneaccess-Snmp | FILTERTAG | Filter probes by name | | | | WARNINGPROBECOMPLETIONTIME | Thresholds | | | | CRITICALPROBECOMPLETIONTIME | Thresholds | | | -| CRITICALPROBESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{adminStatus} eq "active" and %{status} ne "ok"'). You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | %{adminStatus} eq "active" and %{status} ne "ok" | | +| CRITICALPROBESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{adminStatus\} eq "active" and %\{status\} ne "ok"'). You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | %\{adminStatus\} eq "active" and %\{status\} ne "ok" | | | WARNINGPROBESTATUS | | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -379,7 +379,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -435,9 +435,9 @@ All available options for each service template are listed below: |:----------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-cell-id | Filter cell modules by id (IMEI or MEID). | | --custom-perfdata-instances | Define perfdatas instance (default: '%(cellId) %(operator)') | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{signalQuality} =~ /poor/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} eq "notPresent" \|\| %{signalQuality} =~ /none/'). You can use the following variables: %{simStatus}, %{signalQuality}, %{cellId}, %{icci}, %{operator}, %{imsi} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{signalQuality\} =~ /poor/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} eq "notPresent" \|\| %\{signalQuality\} =~ /none/'). You can use the following variables: %\{simStatus\}, %\{signalQuality\}, %\{cellId\}, %\{icci\}, %\{operator\}, %\{imsi\} | | --warning-* --critical-* | Thresholds. Can be: 'modules-cellradio-detected', 'module-cellradio-rsrp', ''module-cellradio-rsrq', 'module-cellradio-rssi', 'module-cellradio-snr'. | @@ -473,9 +473,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -511,9 +511,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-tag | Filter probes by name. | -| --unknown-probe-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | -| --warning-probe-estatus | Define the conditions to match for the status to be WARNING. You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | -| --critical-probe-status | Define the conditions to match for the status to be CRITICAL (Default: '%{adminStatus} eq "active" and %{status} ne "ok"'). You can use the following variables: %{adminStatus}, %{status}, %{type}, %{tag} | +| --unknown-probe-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | +| --warning-probe-estatus | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | +| --critical-probe-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{adminStatus\} eq "active" and %\{status\} ne "ok"'). You can use the following variables: %\{adminStatus\}, %\{status\}, %\{type\}, %\{tag\} | | --warning-* --critical-* | Thresholds. Can be: 'probe-completion-time'. | diff --git a/pp/integrations/plugin-packs/procedures/network-opengear-snmp.md b/pp/integrations/plugin-packs/procedures/network-opengear-snmp.md index 677414ef2c0e..b6e962359376 100644 --- a/pp/integrations/plugin-packs/procedures/network-opengear-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-opengear-snmp.md @@ -316,8 +316,8 @@ yum install centreon-plugin-Network-Opengear-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -462,7 +462,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -556,9 +556,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md b/pp/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md index 3e2d4544e357..ff0ebf176b0a 100644 --- a/pp/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-oracle-infiniband-snmp.md @@ -326,7 +326,7 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -337,10 +337,10 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | FILTERCOUNTERS | Only display some counters (regexp can be used). | | | | IBNAME | Filter by infiniband name (can be a regexp) | | | | IBGWNAME | Filter by infiniband gateway name (can be a regexp) | | | -| CRITICALIBGWSTATUS | Critical threshold | %{status} !~ /up/i | | +| CRITICALIBGWSTATUS | Critical threshold | %\{status\} !~ /up/i | | | WARNINGIBGWSTATUS | Warning threshold | | | -| CRITICALIBSTATUS | Set critical threshold for ib status (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | %{status} !~ /active/i | | -| WARNINGIBSTATUS | Set warning threshold for ib status. You can use the following variables: %{status}, %{display} | | | +| CRITICALIBSTATUS | Set critical threshold for ib status (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} !~ /active/i | | +| WARNINGIBSTATUS | Set warning threshold for ib status. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGIN | Warning threshold | 80 | | | CRITICALIN | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | @@ -396,7 +396,7 @@ yum install centreon-plugin-Network-Oracle-Infiniband-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --oid-display=ifdesc --oid-filter=ifdesc | | @@ -489,7 +489,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -595,9 +595,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -641,8 +641,8 @@ All available options for each service template are listed below: | --speed-in | Set interface speed for incoming traffic (in Mb). | | --speed-out | Set interface speed for outgoing traffic (in Mb). | | --units-traffic | Units of thresholds for the traffic (default: '%') ('%', 'b/s'). | -| --warning-ib-status | Set warning threshold for ib status. You can use the following variables: %{status}, %{display} | -| --critical-ib-status | Set critical threshold for ib status (default: '%{status} !~ /up/i'). You can use the following variables: %{status}, %{display} | +| --warning-ib-status | Set warning threshold for ib status. You can use the following variables: %\{status\}, %\{display\} | +| --critical-ib-status | Set critical threshold for ib status (default: '%\{status\} !~ /up/i'). You can use the following variables: %\{status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'in', 'out'. | | --critical-* | Critical threshold. Can be: 'in', 'out'. | @@ -699,9 +699,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md b/pp/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md index 4c1f7813c7ab..1a998f68bf7d 100644 --- a/pp/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-patton-smartnode-snmp.md @@ -358,7 +358,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | diff --git a/pp/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md b/pp/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md index 84fe01be7ac5..0fbc70ed65e2 100644 --- a/pp/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-peplink-pepwave-snmp.md @@ -266,8 +266,8 @@ yum install centreon-plugin-Network-Peplink-Pepwave-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -295,8 +295,8 @@ yum install centreon-plugin-Network-Peplink-Pepwave-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERNAME | Filter wan name (can be a regexp) | | | -| WARNINGHEALTHSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health\_status}, %{display} | | | -| CRITICALHEALTHSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health\_status} =~ /fail/'). You can use the following variables: %{health\_status}, %{display} | | | +| WARNINGHEALTHSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health_status\}, %\{display\} | | | +| CRITICALHEALTHSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health_status\} =~ /fail/'). You can use the following variables: %\{health_status\}, %\{display\} | | | | WARNINGSIGNAL | Warning threshold | | | | CRITICALSIGNAL | Critical threshold | | | | WARNINGTRAFFICIN | Warning threshold | | | @@ -331,7 +331,7 @@ is able to monitor a resource using a command like this one (replace the sample --oid-filter='ifname' \ --oid-display='ifname' \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -430,7 +430,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -512,9 +512,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -563,8 +563,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='^traffic-in$' | | --filter-name | Filter wan name (can be a regexp). | -| --warning-health-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health\_status}, %{display} | -| --critical-health-status | Define the conditions to match for the status to be CRITICAL (default: '%{health\_status} =~ /fail/'). You can use the following variables: %{health\_status}, %{display} | +| --warning-health-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health_status\}, %\{display\} | +| --critical-health-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health_status\} =~ /fail/'). You can use the following variables: %\{health_status\}, %\{display\} | | --warning-* | Warning threshold. Can be: 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: Can be: 'traffic-in', 'traffic-out'. | diff --git a/pp/integrations/plugin-packs/procedures/network-perle-ids-snmp.md b/pp/integrations/plugin-packs/procedures/network-perle-ids-snmp.md index efead1a2f4d5..9bbe665d5e12 100644 --- a/pp/integrations/plugin-packs/procedures/network-perle-ids-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-perle-ids-snmp.md @@ -218,8 +218,8 @@ yum install centreon-plugin-Network-Perle-Ids-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -268,8 +268,8 @@ yum install centreon-plugin-Network-Perle-Ids-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -375,7 +375,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -442,8 +442,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -485,9 +485,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md b/pp/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md index e31717b9acef..c4e4331158e1 100644 --- a/pp/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-rad-airmux-snmp.md @@ -224,8 +224,8 @@ yum install centreon-plugin-Network-Rad-Airmux-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /minor\|warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | %{severity} =~ /critical\|major/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /minor\|warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | %\{severity\} =~ /critical\|major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -266,8 +266,8 @@ yum install centreon-plugin-Network-Rad-Airmux-Snmp | CRITICALOUTVOLUME | Thresholds | | | | WARNINGSPEED | Thresholds | | | | CRITICALSPEED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | WARNINGTOTALADMINDOWN | Thresholds | | | | CRITICALTOTALADMINDOWN | Thresholds | | | | WARNINGTOTALADMINUP | Thresholds | | | @@ -382,7 +382,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -449,8 +449,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -466,9 +466,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md b/pp/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md index aa60958c112d..adc43c301c19 100644 --- a/pp/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-radware-alteon-snmp.md @@ -283,8 +283,8 @@ yum install centreon-plugin-Network-Radware-Alteon-Snmp | FILTERNAME | Filter by virtual server name (can be a regexp) | | | | WARNINGCURRENTSESSIONS | Warning threshold | | | | CRITICALCURRENTSESSIONS | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | | | CRITICALTOTALSESSION | Critical threshold | | | | WARNINGTOTALSESSIONS | Warning threshold | | | | WARNINGTRAFFIC | Warning threshold | | | @@ -383,7 +383,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -478,8 +478,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --warning-* | Warning threshold. Can be: 'traffic', 'total-sessions', 'current-sessions'. | | --critical-* | Critical threshold. Can be: 'traffic', 'total-sessions', 'current-sessions'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{display\} | | --filter-name | Filter by virtual server name (can be a regexp). | diff --git a/pp/integrations/plugin-packs/procedures/network-raisecom-snmp.md b/pp/integrations/plugin-packs/procedures/network-raisecom-snmp.md index f6cf0dc6e01c..6d16551ba60c 100644 --- a/pp/integrations/plugin-packs/procedures/network-raisecom-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-raisecom-snmp.md @@ -281,8 +281,8 @@ yum install centreon-plugin-Network-Raisecom-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -403,7 +403,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -469,9 +469,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md b/pp/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md index 6104cb20af55..ac5ca341ecf0 100644 --- a/pp/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-riverbed-interceptor-snmp.md @@ -392,7 +392,7 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | CRITICALOUTDISCARD | Threshold | | | | WARNINGOUTERROR | Threshold | | | | CRITICALOUTERROR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -400,8 +400,8 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %{health}, %{status} | %{health} !~ /Healthy/ \|\| %{status} !~ /running/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL . You can use the following variables: %\{health\}, %\{status\} | %\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{status\} | | | | WARNINGUPTIME | Warning thresholds in seconds | | | | CRITICALUPTIME | Critical thresholds in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -416,7 +416,7 @@ yum install centreon-plugin-Network-Riverbed-Interceptor-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -543,7 +543,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -688,9 +688,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -718,8 +718,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /Healthy/ \|\| %{status} !~ /running/'). You can use the following variables: %{health}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/'). You can use the following variables: %\{health\}, %\{status\} | | --warning-uptime | Warning thresholds in seconds. | | --critical-uptime | Critical thresholds in seconds. | @@ -749,9 +749,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md b/pp/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md index 0b389e755558..5926207f440f 100644 --- a/pp/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-riverbed-steelhead-snmp.md @@ -499,7 +499,7 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | CRITICALOUTDISCARD | Threshold | | | | WARNINGOUTERROR | Threshold | | | | CRITICALOUTERROR | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -507,8 +507,8 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------|:-----------:| -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{health}, %{status} | %{health} !~ /Healthy/ \|\| %{status} !~ /running/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{health}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{health\}, %\{status\} | %\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{health\}, %\{status\} | | | | WARNINGUPTIME | Warning thresholds in seconds | | | | CRITICALUPTIME | Critical thresholds in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -532,7 +532,7 @@ yum install centreon-plugin-Network-Riverbed-Steelhead-Snmp | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -663,7 +663,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -826,9 +826,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -855,8 +855,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{health}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} !~ /Healthy/ \|\| %{status} !~ /running/'). You can use the following variables: %{health}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{health\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} !~ /Healthy/ \|\| %\{status\} !~ /running/'). You can use the following variables: %\{health\}, %\{status\} | | --warning-uptime | Warning thresholds in seconds. | | --critical-uptime | Critical thresholds in seconds. | @@ -893,9 +893,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md b/pp/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md index 5fefacf8990a..0d7c7dabd3f3 100644 --- a/pp/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-routers-atrica-snmp.md @@ -265,7 +265,7 @@ yum install centreon-plugin-Network-Routers-Atrica-Snmp | WARNINGOUTEIR | Thresholds | | | | CRITICALOUTEIRDISCARD | Thresholds | | | | WARNINGOUTEIRDISCARD | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%{admstatus} eq "on" and %{opstatus} ne "inService"' '%{admstatus} eq "up" and %{opstatus} ne "up"' You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%\{admstatus\} eq "on" and %\{opstatus\} ne "inService"' '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -358,9 +358,9 @@ All available options for each service template are listed below: | --add-status | Check interface status (by default if no --add-* option is set). | | --add-traffic | Check interface traffic. | | --add-errors | Check interface errors. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up" or %{opstatus} eq "inService"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%{admstatus} eq "on" and %{opstatus} ne "inService"' '%{admstatus} eq "up" and %{opstatus} ne "up"' You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up" or %\{opstatus\} eq "inService"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. Default (depends of the atrica release): '%\{admstatus\} eq "on" and %\{opstatus\} ne "inService"' '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'in-cir', 'in-eir', 'out-cir', 'out-eir', 'in-eir-discard', 'out-eir-discard'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md index 76ff4630fcff..4530d11fde2e 100644 --- a/pp/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-routers-juniper-mseries-snmp.md @@ -328,8 +328,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTER | Filter by peer identifier (can be regexp) | | | | FILTERREMOTEIP | Filter by remote IP address (can be regexp) | | | | FILTERLOCALAS | Filter by local AS (can be regexp) | | | -| CRITICALSTATUS | Specify critical threshold (default: '%{peer\_status} =~ /running/ && %{peer\_state} !~ /established/'). Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | %{peer\_status} =~ /running/ && %{peer\_state} !~ /established/ | | -| WARNINGSTATUS | Specify warning threshold. Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | | | +| CRITICALSTATUS | Specify critical threshold (default: '%\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/'). Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | %\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/ | | +| WARNINGSTATUS | Specify warning threshold. Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -401,8 +401,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERPEER | Filter entities and/or peer | | | | WARNINGLASTCHANGE | Warning threshold in seconds | | | | CRITICALLASTCHANGE | Critical threshold in seconds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /operational/i'). You can use the following variables: %{state} | %{state} !~ /operational/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /operational/i'). You can use the following variables: %\{state\} | %\{state\} !~ /operational/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -415,8 +415,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERTO | Filter LSPs | | | | WARNINGLASTTRANSITION | Warning threshold | | | | CRITICALLASTTRANSITION | Critical threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | %{state} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | %\{state\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | WARNINGTRANSITIONCOUNT | Warning threshold | | | | CRITICALTRANSITIONCOUNT | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -443,8 +443,8 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | FILTERNAME | Filter sessions | | | | FILTERFROM | Filter sessions | | | | FILTERTO | Filter sessions | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | %{state} !~ /up/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | %\{state\} !~ /up/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -481,7 +481,7 @@ yum install centreon-plugin-Network-Routers-Juniper-Mseries-Snmp | CRITICALIN | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 90 | | | WARNINGOUT | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 80 | | | CRITICALOUT | Thresholds (will superseed --\[warning-critical\]-errors). : 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C) | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -576,7 +576,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -642,8 +642,8 @@ All available options for each service template are listed below: | --filter-peer | Filter by peer identifier (can be regexp) | | --filter-remote-ip | Filter by remote ip address (can be regexp) | | --filter-local-as | Filter by local AS (can be regexp) | -| --warning-status | Specify warning threshold. Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | -| --critical-status | Specify critical threshold (default: '%{peer\_status} =~ /running/ && %{peer\_state} !~ /established/'). Can use special variables like %{peer\_identifier}, %{peer\_state}, %{peer\_status}, %{local\_type}, %{local\_ip}, %{local\_port}, %{local\_as}, %{remote\_type}, %{remote\_ip}, %{remote\_port}, %{remote\_as} | +| --warning-status | Specify warning threshold. Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | +| --critical-status | Specify critical threshold (default: '%\{peer_status\} =~ /running/ && %\{peer_state\} !~ /established/'). Can use special variables like %\{peer_identifier\}, %\{peer_state\}, %\{peer_status\}, %\{local_type\}, %\{local_ip\}, %\{local_port\}, %\{local_as\}, %\{remote_type\}, %\{remote_ip\}, %\{remote_port\}, %\{remote_as\} | @@ -724,8 +724,8 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter entities and/or peer. Can be: 'entity', 'peer' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /operational/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /operational/i'). You can use the following variables: %\{state\} | | --warning-last-change | Warning threshold in seconds. | | --critical-last-change | Critical threshold in seconds. | @@ -735,8 +735,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter LSPs. Can be: 'name', 'from', 'to' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | | --warning-* | Warning threshold. Can be: 'transition-count', 'last-transition' (seconds). | | --critical-* | Critical threshold. Can be: 'transition-count', 'last-transition' (seconds). | @@ -754,8 +754,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------| | --filter-* | Filter sessions. Can be: 'name', 'from', 'to' (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} !~ /up/i'). You can use the following variables: %{state} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} !~ /up/i'). You can use the following variables: %\{state\} | @@ -783,9 +783,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical metrics. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-errors | Set warning threshold for all error counters. | | --critical-errors | Set critical threshold for all error counters. | | --warning-* --critical-* | Thresholds (will superseed --\[warning-critical\]-errors). Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'fcs-errors (%)', 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'module-temperature' (C). | diff --git a/pp/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md b/pp/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md index 0577331f7970..7c2fd123e5b7 100644 --- a/pp/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-routers-peplink-balance-snmp.md @@ -282,7 +282,7 @@ yum install centreon-plugin-Network-Routers-Peplink-Balance-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | #NOM? | | @@ -319,7 +319,7 @@ yum install centreon-plugin-Network-Routers-Peplink-Balance-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | #NOM? | | @@ -404,7 +404,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -494,9 +494,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -543,9 +543,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-routers-redback-snmp.md b/pp/integrations/plugin-packs/procedures/network-routers-redback-snmp.md index 9d4d68abb7f7..494d68479e5c 100644 --- a/pp/integrations/plugin-packs/procedures/network-routers-redback-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-routers-redback-snmp.md @@ -340,7 +340,7 @@ yum install centreon-plugin-Network-Routers-Redback-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -377,7 +377,7 @@ yum install centreon-plugin-Network-Routers-Redback-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -465,7 +465,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -578,9 +578,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -626,9 +626,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md b/pp/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md index 66c01dd8faa3..f3f07900db0e 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ruckus-icx-snmp.md @@ -289,8 +289,8 @@ yum install centreon-plugin-Network-Ruckus-Icx-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --use-new-perfdata | | @@ -317,7 +317,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -415,7 +415,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -500,9 +500,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md b/pp/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md index 2e89b43ba5db..04588f6039b6 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ruckus-scg-snmp.md @@ -345,8 +345,8 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| | FILTERNAME | Filter by AP name (can be a regexp) | .* | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{configuration\_status} !~ /^Up-to-date$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | %{configuration\_status} !~ /^Up-to-date$/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /^Disconnect$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | %{connection\_status} =~ /^Disconnect$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{configuration_status\} !~ /^Up-to-date$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | %\{configuration_status\} !~ /^Up-to-date$/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /^Disconnect$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | %\{connection_status\} =~ /^Disconnect$/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -445,7 +445,7 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | CRITICALOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -523,7 +523,7 @@ yum install centreon-plugin-Network-Ruckus-Scg-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -627,7 +627,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -682,8 +682,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by AP name (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{configuration\_status} !~ /^Up-to-date$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connection\_status} =~ /^Disconnect$/i'). You can use the following variables: %{connection\_status}, %{registration\_status}, %{configuration\_status}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{configuration_status\} !~ /^Up-to-date$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connection_status\} =~ /^Disconnect$/i'). You can use the following variables: %\{connection_status\}, %\{registration_status\}, %\{configuration_status\}, %\{display\} | @@ -783,9 +783,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -873,9 +873,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md b/pp/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md index 242bb5028d79..13e6a7cbcf78 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ruckus-smartzone-snmp.md @@ -284,8 +284,8 @@ yum install centreon-plugin-Network-Ruckus-Smartzone-Snmp | FILTERNAME | Filter by access point name (can be a regexp) | .* | | | WARNINGCONNECTIONCLIENTDEVICESAUTHORIZED | Thresholds | | | | CRITICALCONNECTIONCLIENTDEVICESAUTHORIZED | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | | | WARNINGTRAFFICIN | Thresholds | | | | CRITICALTRAFFICIN | Thresholds | | | | WARNINGTRAFFICOUT | Thresholds | | | @@ -323,8 +323,8 @@ yum install centreon-plugin-Network-Ruckus-Smartzone-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --use-new-perfdata | | @@ -462,7 +462,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -529,9 +529,9 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-name | Filter by access point name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status}, %{connection\_status}, %{registration\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\}, %\{connection_status\}, %\{registration_status\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'connection-client-devices-authorized'. | @@ -570,9 +570,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ruckus-snmp.md b/pp/integrations/plugin-packs/procedures/network-ruckus-snmp.md index 41d68805eb63..dd9826a98e37 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruckus-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ruckus-snmp.md @@ -252,7 +252,7 @@ yum install centreon-plugin-Network-Ruckus-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -351,7 +351,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -441,9 +441,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md b/pp/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md index ae2127b3dbc7..1b7a3051f1e6 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ruckus-zonedirector-snmp.md @@ -232,8 +232,8 @@ yum install centreon-plugin-Network-Ruckus-Zonedirector-Snmp | CRITICALCPUUTILIZATION | Thresholds | | | | WARNINGMEMORYUSAGE | Thresholds | | | | CRITICALMEMORYUSAGE | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{zd\_connection\_status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{zd\_connection\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{zd_connection_status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{zd_connection_status\} | | | | WARNINGTRAFFICOUT | Thresholds | | | | CRITICALTRAFFICOUT | Thresholds | | | | WARNINGUSAGEFREE | Thresholds | | | @@ -338,7 +338,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -405,9 +405,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by access point name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{zd\_connection\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{zd\_connection\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{zd\_connection\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{zd_connection_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{zd_connection_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{zd_connection_status\} | | --warning-* --critical-* | Thresholds. Can be: 'memory-usage', 'memory-usage-free', 'memory-usage-prct', 'traffic-in', 'traffic-out', 'cpu-utilization', 'connection-accesspoints', 'connection-client-devices-authorized', 'connection-rogue-devices'. | @@ -415,9 +415,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{system\_status}, %{peer\_connected\_status} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{system\_status}, %{peer\_connected\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{system\_status}, %{peer\_connected\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{system_status\}, %\{peer_connected_status\} | | --warning-* --critical-* | Thresholds. Can be: 'memory-usage', 'usage-free', 'usage-prct', 'traffic-in', 'traffic-out', 'cpu-utilization', 'connection-accesspoints', 'connection-client-devices-authorized', 'connection-rogue-devices'. | diff --git a/pp/integrations/plugin-packs/procedures/network-ruggedcom.md b/pp/integrations/plugin-packs/procedures/network-ruggedcom.md index 6d3775320122..cff045616427 100644 --- a/pp/integrations/plugin-packs/procedures/network-ruggedcom.md +++ b/pp/integrations/plugin-packs/procedures/network-ruggedcom.md @@ -286,7 +286,7 @@ yum install centreon-plugin-Network-Ruggedcom | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -373,7 +373,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -482,9 +482,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-securactive-snmp.md b/pp/integrations/plugin-packs/procedures/network-securactive-snmp.md index 162834d7dc81..0cbbc917bd50 100644 --- a/pp/integrations/plugin-packs/procedures/network-securactive-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-securactive-snmp.md @@ -292,7 +292,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-silverpeak-snmp.md b/pp/integrations/plugin-packs/procedures/network-silverpeak-snmp.md index bd62f2031fee..762ba0bbd01a 100644 --- a/pp/integrations/plugin-packs/procedures/network-silverpeak-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-silverpeak-snmp.md @@ -220,8 +220,8 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERMSG | Filter by message (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -229,8 +229,8 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGSTATUS | Trigger warning on %{operStatus} values | | | -| CRITICALSTATUS | Trigger critical on %{operStatus} values (default: '%{operStatus} !~ /(Normal)/') | | | +| WARNINGSTATUS | Trigger warning on %\{operStatus\} values | | | +| CRITICALSTATUS | Trigger critical on %\{operStatus\} values (default: '%\{operStatus\} !~ /(Normal)/') | | | @@ -266,7 +266,7 @@ yum install centreon-plugin-Network-Silverpeak-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -362,7 +362,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -429,8 +429,8 @@ All available options for each service template are listed below: | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --filter-msg | Filter by message (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{severity} =~ /minor\|warning/i') You can use the following variables: %{severity}, %{text}, %{source}, %{since} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{severity} =~ /critical\|major/i'). You can use the following variables: %{severity}, %{text}, %{source}, %{since} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{severity\} =~ /minor\|warning/i') You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{severity\} =~ /critical\|major/i'). You can use the following variables: %\{severity\}, %\{text\}, %\{source\}, %\{since\} | | --memory | Only check new alarms. | @@ -438,8 +438,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------| -| --warning-status | Trigger warning on %{operStatus} values | -| --critical-status | Trigger critical on %{operStatus} values (default: '%{operStatus} !~ /(Normal)/') | +| --warning-status | Trigger warning on %\{operStatus\} values | +| --critical-status | Trigger critical on %\{operStatus\} values (default: '%\{operStatus\} !~ /(Normal)/') | @@ -466,9 +466,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md b/pp/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md index 6054197161e7..805c46c5da58 100644 --- a/pp/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-sonus-sbc-snmp.md @@ -398,8 +398,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALCHANNELSWAITINGFORDIGITS | Thresholds | | | | WARNINGCHANNELSWAITINGFORROUTE | Thresholds | | | | CRITICALCHANNELSWAITINGFORROUTE | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | %{admstatus} eq "enable" and %{opstatus} !~ /up\|idle\|connected/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | %\{admstatus\} eq "enable" and %\{opstatus\} !~ /up\|idle\|connected/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -441,8 +441,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALCHANNELSACTIVE | Thresholds | | | | WARNINGCPUUTILIZATION | Thresholds | | | | CRITICALCPUUTILIZATION | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{display} | %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{display\} | %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -465,8 +465,8 @@ yum install centreon-plugin-Network-Sonus-SBC-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -619,7 +619,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -697,8 +697,8 @@ All available options for each service template are listed below: | --filter-slot-id | Filter channels by slot ID (can be a regexp). | | --filter-port-id | Filter channels by port ID (can be a regexp). | | --filter-channel-id | Filter channels by channel ID (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'channels-total', 'channels-outofservice', 'channels-idle', 'channels-pending', 'channels-waitingforroute', 'channels-actionlist', 'channels-waitingfordigits', 'channels-remotesetup', 'channels-peersetup', 'channels-alerting', 'channels-inbandinfo', 'channels-connected', 'channels-tonegeneration', 'channels-releasing', 'channels-aborting', 'channels-resetting', 'channels-up', 'channels-down', 'channel-lifetime'. | @@ -776,8 +776,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------| | --warning-* --critical-* | Thresholds. Can be: 'cpu-utilization', 'channels-active'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} eq "down"'). You can use the following variables: %{state}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} eq "down"'). You can use the following variables: %\{state\}, %\{display\} | @@ -804,9 +804,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-sophos-es-snmp.md b/pp/integrations/plugin-packs/procedures/network-sophos-es-snmp.md index 3d3508a6f783..351153e48135 100644 --- a/pp/integrations/plugin-packs/procedures/network-sophos-es-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-sophos-es-snmp.md @@ -295,7 +295,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | diff --git a/pp/integrations/plugin-packs/procedures/network-stormshield-api.md b/pp/integrations/plugin-packs/procedures/network-stormshield-api.md index e26a82237ca5..40c3e783be58 100644 --- a/pp/integrations/plugin-packs/procedures/network-stormshield-api.md +++ b/pp/integrations/plugin-packs/procedures/network-stormshield-api.md @@ -269,11 +269,11 @@ yum install centreon-plugin-Network-Stormshield-Api | Macro | Description | Default value | Mandatory | |:----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------|:-----------:| -| UNKNOWNMEMBERLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%{linkStatus} =~ /unknown/i'). You can use the following variables: %{linkStatus}, %{name} | %{linkStatus} =~ /unknown/i | | -| WARNINGMEMBERCONFIG | Define the conditions to match for the status to be WARNING (default: '%{isConfigSync} eq "no"'). You can use the following variables: %{isConfigSync}, %{name} | %{isConfigSync} eq "no" | | -| CRITICALMEMBERCONFIG | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{isConfigSync}, %{name} | | | -| CRITICALMEMBERLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{linkStatus} =~ /failed\|failing/i'). You can use the following variables: %{linkStatus}, %{name} | %{linkStatus} =~ /failed\|failing/i | | -| WARNINGMEMBERLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkStatus}, %{name} | | | +| UNKNOWNMEMBERLINKSTATUS | Define the conditions to match for the status to be UNKNOWN (default: '%\{linkStatus\} =~ /unknown/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | %\{linkStatus\} =~ /unknown/i | | +| WARNINGMEMBERCONFIG | Define the conditions to match for the status to be WARNING (default: '%\{isConfigSync\} eq "no"'). You can use the following variables: %\{isConfigSync\}, %\{name\} | %\{isConfigSync\} eq "no" | | +| CRITICALMEMBERCONFIG | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{isConfigSync\}, %\{name\} | | | +| CRITICALMEMBERLINKSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{linkStatus\} =~ /failed\|failing/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | %\{linkStatus\} =~ /failed\|failing/i | | +| WARNINGMEMBERLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkStatus\}, %\{name\} | | | | WARNINGMEMBERQUALITY | Thresholds | | | | CRITICALMEMBERQUALITY | Thresholds | | | | WARNINGMEMBERSDETECTED | Thresholds | | | @@ -292,8 +292,8 @@ yum install centreon-plugin-Network-Stormshield-Api | CRITICALMEMBERSRUNNING | Thresholds | | | | WARNINGMEMBERSSTARTING | Thresholds | | | | CRITICALMEMBERSSTARTING | Thresholds | | | -| WARNINGMEMBERSTATE | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{name}. | | | -| CRITICALMEMBERSTATE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{name}. | | | +| WARNINGMEMBERSTATE | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{name\}. | | | +| CRITICALMEMBERSTATE | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{name\}. | | | | WARNINGMEMBERSWAITINGPEER | Thresholds | | | | CRITICALMEMBERSWAITINGPEER | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options). | --verbose | | @@ -312,8 +312,8 @@ yum install centreon-plugin-Network-Stormshield-Api | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| | FILTERSERIAL | Filter by firewalls by serial (can be a regexp) | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /minor/i | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /major/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /minor/i | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options). | --verbose | | @@ -331,8 +331,8 @@ yum install centreon-plugin-Network-Stormshield-Api | CRITICALPACKETSACCEPTED | Thresholds | | | | WARNINGPACKETSBLOCKED | Thresholds | | | | CRITICALPACKETSBLOCKED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: "%{state} eq 'enabled' and %{plugged} eq 'unplugged'") You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | %{state} eq "enabled" and %{plugged} eq "unplugged" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name}. | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: "%\{state\} eq 'enabled' and %\{plugged\} eq 'unplugged'") You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | %\{state\} eq "enabled" and %\{plugged\} eq "unplugged" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\}. | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options). | --verbose | | @@ -462,7 +462,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -524,15 +524,15 @@ All available options for each service template are listed below: | Option | Description | |:------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-member-state | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{name} | -| --warning-member-state | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{name} | -| --critical-member-state | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{name} | -| --unknown-member-link-status | Define the conditions to match for the status to be UNKNOWN (default: '%{linkStatus} =~ /unknown/i'). You can use the following variables: %{linkStatus}, %{name} | -| --warning-member-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkStatus}, %{name} | -| --critical-member-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{linkStatus} =~ /failed\|failing/i'). You can use the following variables: %{linkStatus}, %{name} | -| --unknown-member-config | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{isConfigSync}, %{name} | -| --warning-member-config | Define the conditions to match for the status to be WARNING (default: '%{isConfigSync} eq "no"'). You can use the following variables: %{isConfigSync}, %{name} | -| --critical-member-config | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{isConfigSync}, %{name} | +| --unknown-member-state | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{name\} | +| --warning-member-state | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{name\} | +| --critical-member-state | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{name\} | +| --unknown-member-link-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{linkStatus\} =~ /unknown/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | +| --warning-member-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkStatus\}, %\{name\} | +| --critical-member-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{linkStatus\} =~ /failed\|failing/i'). You can use the following variables: %\{linkStatus\}, %\{name\} | +| --unknown-member-config | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{isConfigSync\}, %\{name\} | +| --warning-member-config | Define the conditions to match for the status to be WARNING (default: '%\{isConfigSync\} eq "no"'). You can use the following variables: %\{isConfigSync\}, %\{name\} | +| --critical-member-config | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{isConfigSync\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'member-quality', 'members-detected', 'members-none', 'members-starting', 'members-waiting-peer', 'members-running', 'members-ready', 'members-reboot', 'members-down', 'members-initializing'. | @@ -553,9 +553,9 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-serial | Filter by firewalls by serial (can be a regexp). | -| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | +| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | @@ -568,9 +568,9 @@ All available options for each service template are listed below: | --add-traffic | Check interface traffic. | | --add-errors | Check interface errors. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: "%{state} eq 'enabled' and %{plugged} eq 'unplugged'") You can use the following variables: %{state}, %{plugged}, %{user\_name}, %{real\_name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: "%\{state\} eq 'enabled' and %\{plugged\} eq 'unplugged'") You can use the following variables: %\{state\}, %\{plugged\}, %\{user_name\}, %\{real_name\} | | --warning-* --critical-* | Thresholds. Can be: 'in-traffic', 'out-traffic', 'packets-accepted', 'packets-blocked', | | --speed | Set interface speed (in Mb). | diff --git a/pp/integrations/plugin-packs/procedures/network-stormshield-snmp.md b/pp/integrations/plugin-packs/procedures/network-stormshield-snmp.md index 06ab2e36944f..77caaf6ec3f7 100644 --- a/pp/integrations/plugin-packs/procedures/network-stormshield-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-stormshield-snmp.md @@ -407,8 +407,8 @@ yum install centreon-plugin-Network-Stormshield-Snmp | CRITICALDEADNODES | Critical threshold for dead nodes (absolute unless --percent is used) | | | | WARNINGHEALTH | Warning threshold for health level (example: --warning 90:) | | | | CRITICALHEALTH | Critical threshold for health level (example --critical 80:) | | | -| WARNINGSTATE | Set warning threshold for state. You can use the following variables: %{state}, %{role} | | | -| CRITICALSTATE | Set critical threshold for state. (default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{role} | | | +| WARNINGSTATE | Set warning threshold for state. You can use the following variables: %\{state\}, %\{role\} | | | +| CRITICALSTATE | Set critical threshold for state. (default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{role\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -424,9 +424,9 @@ yum install centreon-plugin-Network-Stormshield-Snmp | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:-----------:| -| UNKNOWNSERVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /minor/i | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | %{health} =~ /major/i | | +| UNKNOWNSERVICESTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /minor/i | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | %\{health\} =~ /major/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -535,7 +535,7 @@ yum install centreon-plugin-Network-Stormshield-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -546,8 +546,8 @@ yum install centreon-plugin-Network-Stormshield-Snmp | FILTERID | Filter by ID (regexp can be used) | | | | FILTERSRCIP | Filter by source IP address (regexp can be used) | | | | FILTERDSTIP | Filter by destination IP address (regexp can be used) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%{state} eq "dead"'). You can use the following variables: %{state}, %{srcIp}, %{dstIp} | %{state} eq "dead" | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: '%\{state\} eq "dead"'). You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | %\{state\} eq "dead" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | | | | WARNINGTRAFFIC | Thresholds | | | | CRITICALTRAFFIC | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -579,7 +579,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-id='' \ --filter-src-ip='' \ --filter-dst-ip='' \ - --warning-status='%{state} eq "dead"' \ + --warning-status='%\{state\} eq "dead"' \ --critical-status='' \ --warning-traffic='' \ --critical-traffic='' \ @@ -656,7 +656,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -804,8 +804,8 @@ All available options for each service template are listed below: | --critical-health | Critical threshold on health level (example --critical 80:). | | --warning-dead-nodes | Warning threshold on dead nodes (absolute unless --percent is used). | | --critical-dead-nodes | Critical threshold on dead nodes (absolute unless --percent is used). | -| --warning-state | Set warning threshold for state. You can use the following variables: %{state}, %{role}. | -| --critical-state | Set critical threshold for state. (default: '%{state} =~ /offline/i'). You can use the following variables: %{state}, %{role}. | +| --warning-state | Set warning threshold for state. You can use the following variables: %\{state\}, %\{role\}. | +| --critical-state | Set critical threshold for state. (default: '%\{state\} =~ /offline/i'). You can use the following variables: %\{state\}, %\{role\}. | | --percent | Set this option if you want to warn on percent . | @@ -826,9 +826,9 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-serial | Filter by firewall serial (can be a regexp). | -| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{health}, %{service} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /minor/i'). You can use the following variables: %{health}, %{service} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /major/i'). You can use the following variables: %{health}, %{service} | +| --unknown-service-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{health\}, %\{service\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /minor/i'). You can use the following variables: %\{health\}, %\{service\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /major/i'). You can use the following variables: %\{health\}, %\{service\} | @@ -913,9 +913,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -956,9 +956,9 @@ All available options for each service template are listed below: | --filter-id | Filter by ID (regexp can be used). | | --filter-src-ip | Filter by source IP address (regexp can be used). | | --filter-dst-ip | Filter by destination IP address (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{state} eq "dead"'). You can use the following variables: %{state}, %{srcIp}, %{dstIp} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{srcIp}, %{dstIp} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{state\} eq "dead"'). You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{srcIp\}, %\{dstIp\} | | --warning-* --critical-* | Thresholds. Can be: 'vpn-detected', 'traffic', 'traffic-in', 'traffic-out'. | diff --git a/pp/integrations/plugin-packs/procedures/network-stormshield-ssh.md b/pp/integrations/plugin-packs/procedures/network-stormshield-ssh.md index ac36e0fbfc9b..f36bc66cd499 100644 --- a/pp/integrations/plugin-packs/procedures/network-stormshield-ssh.md +++ b/pp/integrations/plugin-packs/procedures/network-stormshield-ssh.md @@ -295,7 +295,7 @@ All available options for each service template are listed below: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[newuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard\|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traffic\_(in\|out)\_$1)' =back | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md index b89e4e0300c5..29aa075ddc72 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-alcatel-omniswitch-snmp.md @@ -291,8 +291,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -310,8 +310,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -321,8 +321,8 @@ yum install centreon-plugin-Network-Switchs-Alcatel-Omniswitch-Snmp |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | WARNINGCHASSISDETECTED | Thresholds | | | | CRITICALCHASSISDETECTED | Thresholds | | | -| CRITICALCHASSISSTATUS | Define the conditions to match for the status to be CRITICAL (default: %{status} !~ /init\|running/) You can use the following variables: %{role}, %{status}, %{mac} | %{status} !~ /init\|running/ | | -| WARNINGCHASSISSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{status}, %{mac} | | | +| CRITICALCHASSISSTATUS | Define the conditions to match for the status to be CRITICAL (default: %\{status\} !~ /init\|running/) You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | %\{status\} !~ /init\|running/ | | +| WARNINGCHASSISSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -349,7 +349,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} !~ /up|dormant/' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} !~ /up|dormant/' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -425,7 +425,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -525,9 +525,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -562,17 +562,17 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | | Option | Description | |:--------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-chassis-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{status}, %{mac} | -| --warning-chassis-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{status}, %{mac} | -| --critical-chassis-status | Define the conditions to match for the status to be CRITICAL (default: %{status} !~ /init\|running/) You can use the following variables: %{role}, %{status}, %{mac} | +| --unknown-chassis-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | +| --warning-chassis-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | +| --critical-chassis-status | Define the conditions to match for the status to be CRITICAL (default: %\{status\} !~ /init\|running/) You can use the following variables: %\{role\}, %\{status\}, %\{mac\} | | --warning-* --critical-* | Thresholds. Can be: 'chassis-detected'. | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md index 9cc67f470e67..98d0d3e5c1f0 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-arista-snmp.md @@ -327,7 +327,7 @@ yum install centreon-plugin-Network-Switchs-Arista-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -380,7 +380,7 @@ yum install centreon-plugin-Network-Switchs-Arista-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -478,7 +478,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -582,9 +582,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -654,9 +654,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md index 58e3f7442bfe..6d5eb53cdca0 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-aruba-standard-snmp.md @@ -358,16 +358,16 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Default value | Mandatory | |:----------------------------|:--------------------------------------------------------------------------------------------|:-------------------|:-----------:| -| WARNINGCONNECTEDCURRENT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALCONNECTEDCURRENT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGCONTROLLERBOOTSTRAP | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALCONTROLLERBOOTSTRAP | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGREBOOT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALREBOOT | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALSTATUS | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | %{status} !~ /up/i | | -| WARNINGSTATUS | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| WARNINGUPTIME | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | -| CRITICALUPTIME | Thresholds. : %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | | | +| WARNINGCONNECTEDCURRENT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALCONNECTEDCURRENT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGCONTROLLERBOOTSTRAP | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALCONTROLLERBOOTSTRAP | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGREBOOT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALREBOOT | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALSTATUS | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | %\{status\} !~ /up/i | | +| WARNINGSTATUS | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| WARNINGUPTIME | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | +| CRITICALUPTIME | Thresholds. : %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -375,10 +375,10 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Default value | Mandatory | |:-------------------------|:----------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| -| WARNINGCONNECTEDCURRENT | Warning threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | | | -| CRITICALCONNECTEDCURRENT | Critical threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | | | -| CRITICALSTATUS | Critical threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | %{status} !~ /active/i | | -| WARNINGSTATUS | Warning threshold. : %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | | | +| WARNINGCONNECTEDCURRENT | Warning threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | | | +| CRITICALCONNECTEDCURRENT | Critical threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | | | +| CRITICALSTATUS | Critical threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Warning threshold. : %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -427,8 +427,8 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------|:-----------:| -| CRITICALSTATUS | Critical threshold. Can use special variables like: %{key}, %{service}, %{flag}, %{expires} (default: '%{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400)') | %{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400) | | -| WARNINGSTATUS | Warning threshold. Can use special variables like:%{key}, %{service}, %{flag}, %{expires} (default: '') | | | +| CRITICALSTATUS | Critical threshold. Can use special variables like: %\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '%\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400)') | %\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400) | | +| WARNINGSTATUS | Warning threshold. Can use special variables like:%\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '') | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -486,7 +486,7 @@ yum install centreon-plugin-Network-Switchs-Aruba-Standard-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -625,7 +625,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -688,7 +688,7 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* --critical-* | Thresholds. Can be: 'connected-current' (global), 'uptime', 'controller-bootstrap', 'reboot', 'status' (per AP). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{group}, %{location} (default: '') | +| --warning-* --critical-* | Thresholds. Can be: 'connected-current' (global), 'uptime', 'controller-bootstrap', 'reboot', 'status' (per AP). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{group\}, %\{location\} (default: '') | | --filter-* | Filter by 'ip', 'name', 'group' (regexp can be used). | @@ -696,8 +696,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-* | Warning threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{role}, %{location} (default: '') | -| --critical-* | Critical threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %{name}, %{status}, %{ip}, %{role}, %{location} (default: '%{status} !~ /active/i') | +| --warning-* | Warning threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '') | +| --critical-* | Critical threshold. Can be: 'connected-current' (global), 'status' (per controller). 'status' can use special variables like: %\{name\}, %\{status\}, %\{ip\}, %\{role\}, %\{location\} (default: '%\{status\} !~ /active/i') | | --filter-* | Filter by 'ip', 'name', 'location' (regexp can be used). | @@ -753,8 +753,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --warning-status | Warning threshold. Can use special variables like:%{key}, %{service}, %{flag}, %{expires} (default: '') | -| --critical-status | Critical threshold. Can use special variables like: %{key}, %{service}, %{flag}, %{expires} (default: '%{flag} !~ /enabled/i \|\| (%{expires} ne "Never" && %{expires} \< 86400)') | +| --warning-status | Warning threshold. Can use special variables like:%\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '') | +| --critical-status | Critical threshold. Can use special variables like: %\{key\}, %\{service\}, %\{flag\}, %\{expires\} (default: '%\{flag\} !~ /enabled/i \|\| (%\{expires\} ne "Never" && %\{expires\} \< 86400)') | @@ -789,9 +789,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -847,9 +847,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md index d0d9287791d5..a1a6498b008e 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-brocade-snmp.md @@ -308,7 +308,7 @@ yum install centreon-plugin-Network-Switchs-Brocade-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -345,7 +345,7 @@ yum install centreon-plugin-Network-Switchs-Brocade-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -432,7 +432,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -536,9 +536,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -583,9 +583,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -630,9 +630,9 @@ All available options for each service template are listed below: | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | | --add-optical | Check interface optical. | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s), 'laser-temp', 'input-power', 'output-power'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md index 916911bd756f..617dd757008c 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-cisco-smallbusiness-standard-snmp.md @@ -307,7 +307,7 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | WARNINGOUTDISCARD | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -316,8 +316,8 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | Macro | Description | Default value | Mandatory | |:---------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:-----------:| | FILTERPORT | Filter on port description (can be a regexp) | .* | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | %{state} =~ /blocking\|broken/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | %\{state\} =~ /blocking\|broken/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -354,7 +354,7 @@ yum install centreon-plugin-Network-Switchs-Cisco-Smallbusiness-Standard-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -443,7 +443,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -538,9 +538,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -567,8 +567,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-port | Filter on port description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{op\_status} =~ /up/ && %{state} =~ /blocking\|broken/'). You can use the following variables: %{state}, %{op\_status}, %{admin\_status}, %{port}, %{index}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{op_status\} =~ /up/ && %\{state\} =~ /blocking\|broken/'). You can use the following variables: %\{state\}, %\{op_status\}, %\{admin_status\}, %\{port\}, %\{index\}. | @@ -595,9 +595,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md index 5749f78b103b..b78cecf5da11 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-dell-xseries-snmp.md @@ -255,8 +255,8 @@ yum install centreon-plugin-Network-Dell-Xseries-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -292,7 +292,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-traffic \ --add-errors \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -363,7 +363,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -457,9 +457,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md index 0c425f3b3c51..802feb0bf8e4 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-hirschmann-snmp.md @@ -233,8 +233,8 @@ yum install centreon-plugin-Network-Switchs-Hirschmann | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{config\_status} | %{config\_status} =~ /notInSync\|outOfSync/ | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{config_status\} | %\{config_status\} =~ /notInSync\|outOfSync/ | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -314,7 +314,7 @@ yum install centreon-plugin-Network-Switchs-Hirschmann | CRITICALIN | Threshold | 90 | | | WARNINGOUT | Threshold | 80 | | | CRITICALOUT | Threshold | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -428,7 +428,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -462,8 +462,8 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | -| --warning-status | Define the conditions to match for the status to be WARNING (default : '%{config\_status} =~ /notInSync\|outOfSync/'). You can use the following variables: %{config\_status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{config\_status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default : '%\{config_status\} =~ /notInSync\|outOfSync/'). You can use the following variables: %\{config_status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{config_status\} | @@ -530,9 +530,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md index e851cbfe2d59..5242a278b33a 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-hp-procurve-snmp.md @@ -282,10 +282,10 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------|:-----------:| -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | %{role} ne %{roleLast} | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | | | -| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | %{admin\_status} eq "up" and %{oper\_status} ne "up" | | -| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | %\{role\} ne %\{roleLast\} | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | | | +| CRITICALPORTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | %\{admin_status\} eq "up" and %\{oper_status\} ne "up" | | +| WARNINGPORTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -322,7 +322,7 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | WARNINGIN | Threshold on warning-in-traffic | 80 | | | CRITICALOUT | Threshold on critical-in-traffic | 90 | | | WARNINGOUT | Threshold on warning-out-traffic | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -333,10 +333,10 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | FILTERMEMBERSERIAL | Filter members by serial (can be a regexp) | | | | WARNINGCPUUTILIZATION | Threshold | | | | CRITICALCPUUTILIZATION | Threshold | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{link\_status}, %{display} | %{link\_status} eq "down" | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{stateLast} | %{state} ne %{stateLast} \|\| %{state} =~ /communicationFailure\|incompatibleOS/i | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{stateLast} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} eq "down" | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{stateLast\} | %\{state\} ne %\{stateLast\} \|\| %\{state\} =~ /communicationFailure\|incompatibleOS/i | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{stateLast\} | | | | WARNINGMEMBERSTOTAL | Threshold | | | | CRITICALMEMBERSTOTAL | Threshold | | | | WARNINGMEMORYUSAGE | Threshold | | | @@ -345,8 +345,8 @@ yum install centreon-plugin-Network-Switchs-Hp-Procurve-Snmp | CRITICALMEMORYUSAGEFREE | Threshold | | | | WARNINGMEMORYUSAGEPRCT | Threshold | | | | CRITICALMEMORYUSAGEPRCT | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | %{status} !~ /active/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | %\{status\} !~ /active/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -369,7 +369,7 @@ is able to monitor a resource using a command like this one (replace the sample --snmp-community='my-snmp-community' \ --filter-member-serial='' \ --warning-member-status='' \ - --critical-member-status='%{state} ne %{stateLast} || %{state} =~ /communicationFailure|incompatibleOS/i' \ + --critical-member-status='%\{state\} ne %\{stateLast\} || %\{state\} =~ /communicationFailure|incompatibleOS/i' \ --warning-cpu-utilization='' \ --critical-cpu-utilization='' \ --warning-memory-usage='' \ @@ -379,11 +379,11 @@ is able to monitor a resource using a command like this one (replace the sample --warning-memory-usage-prct='' \ --critical-memory-usage-prct='' \ --warning-status='' \ - --critical-status='%{status} !~ /active/i' \ + --critical-status='%\{status\} !~ /active/i' \ --warning-members-total='' \ --critical-members-total='' \ --warning-link-status='' \ - --critical-link-status='%{link\_status} eq "down"' \ + --critical-link-status='%\{link_status\} eq "down"' \ --verbose ``` @@ -468,7 +468,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -533,12 +533,12 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\ |yyyy$' | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%{role} ne %{roleLast}'). You can use the following variables: %{role}, %{roleLast}, %{state}, %{stateLast} | -| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | -| --warning-port-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | -| --critical-port-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admin\_status} eq "up" and %{oper\_status} ne "up"'). You can use the following variables: %{admin\_status}, %{oper\_status}, %{display} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{role\} ne %\{roleLast\}'). You can use the following variables: %\{role\}, %\{roleLast\}, %\{state\}, %\{stateLast\} | +| --unknown-port-status | Define the conditions to match for the status to be UNKNOWN (Default: ''). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | +| --warning-port-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | +| --critical-port-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admin_status\} eq "up" and %\{oper_status\} ne "up"'). You can use the following variables: %\{admin_status\}, %\{oper_status\}, %\{display\} | @@ -554,9 +554,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). And also: 'input-power' (dBm), 'bias-current' (mA), 'output-power' (dBm), 'voltage' (mV), 'module-temperature' (C), 'poe-power-actual'. | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -591,8 +591,8 @@ All available options for each service template are listed below: | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | | --add-poe | Check power over thernet. | | --add-optical | Check interface optical metrics. | -| --warning-poe-status | Set warning threshold for poe status. You can use the following variables: %{admstatus}, %{opstatus}, %{poestatus}, %{display} | -| --critical-poe-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{poestatus}, %{display} | +| --warning-poe-status | Set warning threshold for poe status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{poestatus\}, %\{display\} | +| --critical-poe-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{poestatus\}, %\{display\} | @@ -601,15 +601,15 @@ All available options for each service template are listed below: |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-member-serial | Filter members by serial (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /active/i'). You can use the following variables: %{status} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{stateLast} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{stateLast} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} ne %{stateLast} \|\| %{state} =~ /communicationFailure\|incompatibleOS/i'). You can use the following variables: %{state}, %{stateLast} | -| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%{link\_status} eq "down"'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /active/i'). You can use the following variables: %\{status\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{stateLast\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{stateLast\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} ne %\{stateLast\} \|\| %\{state\} =~ /communicationFailure\|incompatibleOS/i'). You can use the following variables: %\{state\}, %\{stateLast\} | +| --unknown-link-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (default: '%\{link_status\} eq "down"'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'members-total', 'memory-usage-prct', 'memory-usage', 'memory-usage-free', 'cpu-utilization'. | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md index ee47b75506e2..0e34b505a65f 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-juniper-ex-snmp.md @@ -352,7 +352,7 @@ yum install centreon-plugin-Network-Switchs-Juniper-Ex-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -441,7 +441,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -596,9 +596,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md b/pp/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md index 62755e94a22e..5e28a01e8773 100644 --- a/pp/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-switchs-mrv-optiswitch-snmp.md @@ -212,8 +212,8 @@ yum install centreon-plugin-Network-Switchs-Mrv-Optiswitch-Snmp | CRITICALIN | Thresholds | | | | WARNINGOUT | Thresholds | | | | CRITICALOUT | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "enabled" and %{linkstatus} ne "true"'). You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "enabled" and %\{linkstatus\} ne "true"'). You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -248,7 +248,7 @@ is able to monitor a resource using a command like this one (replace the sample --add-status \ --add-traffic \ --warning-status='' \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='' \ --critical-in-traffic='' \ --warning-out-traffic='' \ @@ -311,7 +311,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -396,9 +396,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "enabled" and %{linkstatus} eq "true"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "enable" and %{opstatus} eq "enabled" and %{linkstatus} ne "true"'). You can use the following variables: %{linkstatus}, %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "enabled" and %\{linkstatus\} eq "true"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "enable" and %\{opstatus\} eq "enabled" and %\{linkstatus\} ne "true"'). You can use the following variables: %\{linkstatus\}, %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'total-link-up', 'total-link-down', 'in-traffic', 'out-traffic', 'in-crc', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md b/pp/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md index 01d41ea6844f..445ac30885d8 100644 --- a/pp/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-symbol-wing-snmp.md @@ -238,7 +238,7 @@ yum install centreon-plugin-Network-Symbol-Wing-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -297,7 +297,7 @@ yum install centreon-plugin-Network-Symbol-Wing-Snmp | CRITICALIN | Thresholds | 80 | | | WARNINGOUT | Thresholds | 90 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} ne "up" | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} ne "up" | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -322,7 +322,7 @@ is able to monitor a resource using a command like this one (replace the sample --name \ --add-status \ --add-traffic \ - --critical-status='%{admstatus} eq "up" and %{opstatus} ne "up"' \ + --critical-status='%\{admstatus\} eq "up" and %\{opstatus\} ne "up"' \ --warning-in-traffic='80' \ --critical-in-traffic='80' \ --warning-out-traffic='90' \ @@ -382,7 +382,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -456,9 +456,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -513,9 +513,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-teldat-snmp.md b/pp/integrations/plugin-packs/procedures/network-teldat-snmp.md index 1e96d85b9881..2961debaeebe 100644 --- a/pp/integrations/plugin-packs/procedures/network-teldat-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-teldat-snmp.md @@ -264,8 +264,8 @@ yum install centreon-plugin-Network-Teldat-Snmp | CRITICALMODULECELLRADIOSNR | Thresholds on cellular mobile signal versus noise ratio (SINR). | | | | WARNINGMODULESCELLRADIODETECTED | Thresholds on detected cellular mobile(s) | | | | CRITICALMODULESCELLRADIODETECTED | Thresholds on detected cellular mobile(s) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | '%{interfaceState} =~ /disconnect/' | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | '%{simStatus} =~ /LOCKED/ or %{simStatus} =~ /DETECTING/' | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | '%\{interfaceState\} =~ /disconnect/' | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | '%\{simStatus\} =~ /LOCKED/ or %\{simStatus\} =~ /DETECTING/' | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -300,8 +300,8 @@ yum install centreon-plugin-Network-Teldat-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\dormant/ | | -| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Set critical threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\dormant/ | | +| WARNINGSTATUS | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -408,7 +408,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -465,10 +465,10 @@ All available options for each service template are listed below: | --filter-module | Filter cellular radio interfaces by module. | | --filter-imei | Filter cellular radio interfaces by IMEI. | | --filter-interface-type | Filter cellular radio interfaces by type. | -| --custom-perfdata-instances | Define perfdata instances (default: '%(cellId) %(operator)'). You can use the following variables: %{cellId}, %{simIcc}, %{operator} | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{interfaceState} =~ /disconnect/'). You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{simStatus} =~ /LOCKED/ \|\| %{simStatus} =~ /DETECTING/'). You can use the following variables: %{simStatus}, %{interfaceState}, %{cellId}, %{simIcc}, %{operator}, %{imsi} | +| --custom-perfdata-instances | Define perfdata instances (default: '%(cellId) %(operator)'). You can use the following variables: %\{cellId\}, %\{simIcc\}, %\{operator\} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{interfaceState\} =~ /disconnect/'). You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{simStatus\} =~ /LOCKED/ \|\| %\{simStatus\} =~ /DETECTING/'). You can use the following variables: %\{simStatus\}, %\{interfaceState\}, %\{cellId\}, %\{simIcc\}, %\{operator\}, %\{imsi\} | | --warning-* --critical-* | Thresholds. Can be: 'modules-cellradio-detected', 'module-cellradio-rsrp', ''module-cellradio-rsrq', 'module-cellradio-rscp', 'module-cellradio-csq' 'module-cellradio-snr'. | @@ -503,9 +503,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Set warning threshold for status. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Set critical threshold for status. (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Set warning threshold for status. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Set critical threshold for status. (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-teltonika-snmp.md b/pp/integrations/plugin-packs/procedures/network-teltonika-snmp.md index def4e4fc8356..45a5c9371942 100644 --- a/pp/integrations/plugin-packs/procedures/network-teltonika-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-teltonika-snmp.md @@ -221,8 +221,8 @@ yum install centreon-plugin-Network-Teltonika-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -236,8 +236,8 @@ yum install centreon-plugin-Network-Teltonika-Snmp | CRITICALSIGNALRECEIVEQUALITY | Thresholds | | | | WARNINGSIGNALSTRENGTH | Thresholds | | | | CRITICALSIGNALSTRENGTH | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | %{connectionState} !~ /connected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | %\{connectionState\} !~ /connected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | | | | WARNINGTEMPERATURE | Thresholds | | | | CRITICALTEMPERATURE | Thresholds | | | | WARNINGTRAFFICIN | Thresholds | | | @@ -264,7 +264,7 @@ is able to monitor a resource using a command like this one (replace the sample --hostname='10.0.0.1' \ --snmp-version='2c' \ --snmp-community='my-snmp-community' \ - --critical-status='%{connectionState} !~ /connected/i' \ + --critical-status='%\{connectionState\} !~ /connected/i' \ --verbose ``` @@ -320,7 +320,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -394,9 +394,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (Default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (Default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (Default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (Default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -423,8 +423,8 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connectionState} !~ /connected/i'). You can use the following variables: %{simState}, %{pinState}, %{netState}, %{connectionState} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connectionState\} !~ /connected/i'). You can use the following variables: %\{simState\}, %\{pinState\}, %\{netState\}, %\{connectionState\} | | --warning-* --critical-* | Thresholds. Can be: 'signal-strength', 'temperature', 'traffic-in', 'traffic-out' 'signal-receive-power', 'signal-receive-quality'. | diff --git a/pp/integrations/plugin-packs/procedures/network-tplink-snmp.md b/pp/integrations/plugin-packs/procedures/network-tplink-snmp.md index b8bc68d7027a..61b110bc546c 100644 --- a/pp/integrations/plugin-packs/procedures/network-tplink-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-tplink-snmp.md @@ -265,8 +265,8 @@ yum install centreon-plugin-Network-Tplink-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --use-new-perfdata | | @@ -363,7 +363,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -444,9 +444,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md b/pp/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md index d4ca3f56fc9a..71b205785ca8 100644 --- a/pp/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ubiquiti-airfiber-snmp.md @@ -255,8 +255,8 @@ yum install centreon-plugin-Network-Ubiquiti-Airfiber-Snmp | CRITICALOUTERROR | Threshold | | | | WARNINGOUTTRAFFIC | Threshold | | | | CRITICALOUTTRAFFIC | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --no-skipped-counters --use-new-perfdata | | @@ -295,8 +295,8 @@ yum install centreon-plugin-Network-Ubiquiti-Airfiber-Snmp | CRITICALCHAIN0SIGNALRECEIVEPOWER | Threshold | | | | WARNINGCHAIN1SIGNALRECEIVEPOWER | Threshold | | | | CRITICALCHAIN1SIGNALRECEIVEPOWER | Threshold | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{enabled}, %{state}, %{name} | %{enabled} eq "yes" and %{state} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{enabled}, %{state}, %{name} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | %\{enabled\} eq "yes" and %\{state\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | | | | WARNINGTRAFFICIN | Threshold | | | | CRITICALTRAFFICIN | Threshold | | | | WARNINGTRAFFICOUT | Threshold | | | @@ -409,7 +409,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -463,9 +463,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -507,9 +507,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter interface by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{enabled}, %{state}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{enabled}, %{state}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{enabled} eq "yes" and %{state} eq "down"'). You can use the following variables: %{enabled}, %{state}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{enabled\} eq "yes" and %\{state\} eq "down"'). You can use the following variables: %\{enabled\}, %\{state\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'traffic-in', 'traffic-out', 'chain0-signal-receive-power', 'chain1-signal-receive-power'. | diff --git a/pp/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md b/pp/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md index a1f5c833c71d..f002157246df 100644 --- a/pp/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ubiquiti-unifi-snmp.md @@ -355,8 +355,8 @@ yum install centreon-plugin-Network-Ubiquiti-Unifi-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose --use-new-perfdata | | @@ -402,11 +402,11 @@ yum install centreon-plugin-Network-Ubiquiti-Unifi-Snmp |:------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|:-----------:| | FILTERAPNAME | Filter virtual access points by name (can be a regexp) | | | | FILTERAPSSID | Filter virtual access points by SSID (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{ssid}, %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | | | WARNINGCLIENTSCONNECTED | Thresholds | | | | CRITICALCLIENTSCONNECTED | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{name}, %{ssid}, %{status} | %{status} eq "down" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{ssid}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | %\{status\} eq "down" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | WARNINGTOTALCLIENTSCONNECTED | Thresholds | | | @@ -439,7 +439,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-ssid='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} eq "down"' \ + --critical-status='%\{status\} eq "down"' \ --warning-total='' \ --critical-total='' \ --warning-total-clients-connected='' \ @@ -512,7 +512,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -635,9 +635,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -731,9 +731,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='status' | | --filter-name | Filter virtual access points by name (can be a regexp). | | --filter-ssid | Filter virtual access points by SSID (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{name}, %{ssid}, %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{name}, %{ssid}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "down"'). You can use the following variables: %{name}, %{ssid}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "down"'). You can use the following variables: %\{name\}, %\{ssid\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total', 'total-clients-connected', 'clients-connected', 'traffic-in', 'traffic-out'. | diff --git a/pp/integrations/plugin-packs/procedures/network-ucopia-snmp.md b/pp/integrations/plugin-packs/procedures/network-ucopia-snmp.md index cc2eadddec8c..c3667202a89a 100644 --- a/pp/integrations/plugin-packs/procedures/network-ucopia-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-ucopia-snmp.md @@ -235,10 +235,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -256,10 +256,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | %{status} eq "stopped" | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} eq "stopped" | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -277,10 +277,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -298,10 +298,10 @@ yum install centreon-plugin-Network-Ucopia-Snmp | CRITICALCPUTEMPERATURE | Thresholds | | | | WARNINGDISKTEMPERATURE | Thresholds | | | | CRITICALDISKTEMPERATURE | Thresholds | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGUSERSCONNECTED | Thresholds | | | | CRITICALUSERSCONNECTED | Thresholds | | | | WARNINGUSERSCONNECTEDPRCT | Thresholds | | | @@ -392,7 +392,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -447,10 +447,10 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -459,10 +459,10 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -471,10 +471,10 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | @@ -483,10 +483,10 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-counters | Only display some counters (regexp can be used). Example: --filter-counters='service-status' | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} eq "stopped"'). You can use the following variables: %{status}, %{display} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{ha\_status} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%{ha\_status} eq "fault"'). You can use the following variables: %{ha\_status} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} eq "stopped"'). You can use the following variables: %\{status\}, %\{display\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{ha_status\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ha_status\} eq "fault"'). You can use the following variables: %\{ha_status\} | | --warning-* --critical-* | Thresholds. Can be: 'users-connected', 'users-connected-prct', 'disk-temperature', 'cpu-temperature'. | diff --git a/pp/integrations/plugin-packs/procedures/network-versa-director-restapi.md b/pp/integrations/plugin-packs/procedures/network-versa-director-restapi.md index c415fb765fdb..67003681a141 100644 --- a/pp/integrations/plugin-packs/procedures/network-versa-director-restapi.md +++ b/pp/integrations/plugin-packs/procedures/network-versa-director-restapi.md @@ -157,7 +157,7 @@ and test the Plugin by running the following command: --organization='.*' \ --filter-device-name='^CENFRGW101$' \ --warning-status='' \ - --critical-status='%{ping_status} ne "reachable" or %{services_status} ne "good"' \ + --critical-status='%\{ping_status\} ne "reachable" or %\{services_status\} ne "good"' \ --verbose ``` diff --git a/pp/integrations/plugin-packs/procedures/network-watchguard-snmp.md b/pp/integrations/plugin-packs/procedures/network-watchguard-snmp.md index d95539fcf187..eda953264c75 100644 --- a/pp/integrations/plugin-packs/procedures/network-watchguard-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-watchguard-snmp.md @@ -276,16 +276,16 @@ yum install centreon-plugin-Network-Watchguard-Snmp | Macro | Description | Default value | Mandatory | |:-----------------------------|:----------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state} | | | -| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state} | | | +| WARNINGCLUSTERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\} | | | +| CRITICALCLUSTERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\} | | | | WARNINGMEMBERHEALTHHARDWARE | Thresholds | | | | CRITICALMEMBERHEALTHHARDWARE | Thresholds | | | | WARNINGMEMBERHEALTHSYSTEM | Thresholds | | | | CRITICALMEMBERHEALTHSYSTEM | Thresholds | | | | WARNINGMEMBERSDETECTED | Thresholds | | | | CRITICALMEMBERSDETECTED | Thresholds | | | -| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{serial} | | | -| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{serial} | | | +| WARNINGMEMBERSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{serial\} | | | +| CRITICALMEMBERSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{serial\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -374,7 +374,7 @@ yum install centreon-plugin-Network-Watchguard-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -471,7 +471,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -525,12 +525,12 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:------------------------------------------------------------------------------------------------------------------------| -| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state} | -| --warning-cluster-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state} | -| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state} | -| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{role}, %{serial} | -| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{role}, %{serial} | -| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{role}, %{serial} | +| --unknown-cluster-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\} | +| --warning-cluster-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\} | +| --critical-cluster-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\} | +| --unknown-member-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{role\}, %\{serial\} | +| --warning-member-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{role\}, %\{serial\} | +| --critical-member-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{role\}, %\{serial\} | | --warning-* --critical-* | Thresholds. Can be: 'members-detected', 'member-health-hardware', 'member-health-system'. | @@ -677,9 +677,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/network-zyxel-snmp.md b/pp/integrations/plugin-packs/procedures/network-zyxel-snmp.md index 099d2a76e734..12b46ae22e02 100644 --- a/pp/integrations/plugin-packs/procedures/network-zyxel-snmp.md +++ b/pp/integrations/plugin-packs/procedures/network-zyxel-snmp.md @@ -294,7 +294,7 @@ yum install centreon-plugin-Network-Zyxel-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -303,8 +303,8 @@ yum install centreon-plugin-Network-Zyxel-Snmp | Macro | Description | Default value | Mandatory | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------|:-----------:| | FILTERNAME | Filter vpn name with regexp | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{connectstatus} eq "disconnected"'). You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | %{connectstatus} eq "disconnected" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{connectstatus\} eq "disconnected"'). You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | %\{connectstatus\} eq "disconnected" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | | | | WARNINGTRAFFICIN | Warning threshold | | | | CRITICALTRAFFICIN | Critical threshold | | | | WARNINGTRAFFICOUT | Warning threshold | | | @@ -397,7 +397,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on an "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -496,9 +496,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -539,8 +539,8 @@ All available options for each service template are listed below: | --filter-name | Filter vpn name with regexp. | | --warning-* | Warning threshold. Can be: 'traffic-in', 'traffic-out'. | | --critical-* | Critical threshold. Can be: 'traffic-in', 'traffic-out'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{connectstatus} eq "disconnected"'). You can use the following variables: %{activestatus}, %{connectstatus}, %{display} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{connectstatus\} eq "disconnected"'). You can use the following variables: %\{activestatus\}, %\{connectstatus\}, %\{display\} | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md b/pp/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md index f068e8ee621a..1a7a4edb3aeb 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-aix-snmp.md @@ -378,7 +378,7 @@ yum install centreon-plugin-Operatingsystems-Aix-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -470,7 +470,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -658,9 +658,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md b/pp/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md index ebba90413a69..6fff1b654612 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-aix-ssh.md @@ -276,9 +276,9 @@ yum install centreon-plugin-Operatingsystems-Aix-Local | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | FILTERTYPE | Filter filesystem type (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | %{state} =~ /stale/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{lv}, %{mount}, %{type} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | %\{state\} =~ /stale/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -288,8 +288,8 @@ yum install centreon-plugin-Operatingsystems-Aix-Local |:---------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERCOMMAND | Filter process commands (regexp can be used) | | | | FILTERPPID | Filter process ppid (regexp can be used) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | | | WARNINGTOTAL | Threshold | | | | CRITICALTOTAL | Threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -332,13 +332,13 @@ is able to monitor a resource using a command like this one (replace the sample --warning-usage='' \ --critical-usage='' \ --warning-usage-prct='' \ - --critical-usage-prct='' + --critical-usage-prct='' ``` The expected command output is shown below: ```bash -OK: All storages are ok | 'disk_name1#storage.space.usage.bytes'=90102B;;;0;total_space 'disk_name2#storage.space.usage.bytes'=18580B;;;0;total_space 'disk_name1#storage.space.free.bytes'=53768B;;;0;total_space 'disk_name2#storage.space.free.bytes'=16004B;;;0;total_space 'disk_name1#storageresource.space.usage.percentage'=63%;;;0;100 'disk_name2#storageresource.space.usage.percentage'=54%;;;0;100 +OK: All storages are ok | 'disk_name1#storage.space.usage.bytes'=90102B;;;0;total_space 'disk_name2#storage.space.usage.bytes'=18580B;;;0;total_space 'disk_name1#storage.space.free.bytes'=53768B;;;0;total_space 'disk_name2#storage.space.free.bytes'=16004B;;;0;total_space 'disk_name1#storageresource.space.usage.percentage'=63%;;;0;100 'disk_name2#storageresource.space.usage.percentage'=54%;;;0;100 ``` ### Troubleshooting @@ -394,7 +394,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | | --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back | @@ -479,9 +479,9 @@ All available options for each service template are listed below: | --filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx\|yyyy$' | | --filter-type | Filter filesystem type (regexp can be used). | | --filter-mount | Filter storage mount point (regexp can be used). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /stale/i'). You can use the following variables: %{state}, %{lv}, %{mount}, %{type}. | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{state\} =~ /stale/i'). You can use the following variables: %\{state\}, %\{lv\}, %\{mount\}, %\{type\}. | @@ -493,8 +493,8 @@ All available options for each service template are listed below: | --filter-arg | Filter process arguments (regexp can be used). | | --filter-ppid | Filter process ppid (regexp can be used). | | --filter-state | Filter process states (regexp can be used). You can use: 'Canceled', 'Nonexistent', 'Active', 'Swapped', 'Idle', 'Stopped', 'Running', 'Sleeping'. | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{ppid}, %{state}, %{elapsed}, %{cmd}, %{args} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '') You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{ppid\}, %\{state\}, %\{elapsed\}, %\{cmd\}, %\{args\} | | --warning-* --critical-* | Thresholds. Can be: 'total'. | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md b/pp/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md index 7a7c8654dbb1..93c1a95f6227 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-as400-connector.md @@ -276,9 +276,9 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | COMMANDNAME | Specify the command to execute (required) | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /failed/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /failed/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | | | @@ -286,10 +286,10 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Default value | Mandatory | |:------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/i | | | DISKNAME | Filter disks by name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitControl)$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitControl)$/i | | | WARNINGUSAGEPRCT | Thresholds | | | | CRITICALUSAGEPRCT | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -300,7 +300,7 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | Macro | Description | Default value | Mandatory | |:----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:---------------------|:-----------:| | JOBQUEUES | | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGJOBSACTIVE | Thresholds | | | | CRITICALJOBSACTIVE | Thresholds | | | | WARNINGJOBSHELD | Thresholds | | | @@ -309,8 +309,8 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | CRITICALJOBSSCHEDULED | Thresholds | | | | WARNINGJOBSTOTAL | Thresholds | | | | CRITICALJOBSTOTAL | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | %{status} =~ /HELD/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | %\{status\} =~ /HELD/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -356,7 +356,7 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| | FILTERNAME | Filter subsystems by name (can be a regexp) | | | | FILTERLIBRARY | Filter subsystems by library (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGACTIVE | Thresholds | | | | CRITICALACTIVE | Thresholds | | | | WARNINGENDING | Thresholds | | | @@ -369,8 +369,8 @@ yum install centreon-plugin-Operatingsystems-AS400-Connector | CRITICALRESTRICTED | Thresholds | | | | WARNINGSTARTING | Thresholds | | | | CRITICALSTARTING | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | %{status} =~ /ending\|restricted\|starting/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | %\{status\} =~ /ending\|restricted\|starting/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | | | WARNINGTOTAL | Thresholds | | | | CRITICALTOTAL | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -478,7 +478,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -524,9 +524,9 @@ All available options for each service template are listed below: | Option | Description | |:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------| | --command-name | Specify the command to execute (required). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /failed/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /failed/i'). You can use the following variables: %\{status\}, %\{name\} | @@ -535,9 +535,9 @@ All available options for each service template are listed below: |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --disk-name | Check exact disk. | | --filter-disk-name | Filter disks by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/i'). You can use the following variables: %{status}, %{name} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i') . You can use the following variables: %{status}, %{name} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitContr ol)$/i'). You can use the following variables: %{status}, %{name} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/i'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /noReady\|busy\|hwFailureOk\|hwFailurePerf\|Protected\|rebuilding/i') . You can use the following variables: %\{status\}, %\{name\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /^(noAccess\|otherDiskSubFailed\|failed\|notOperational\|noUnitContr ol)$/i'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct', 'reserved', 'disks-total', 'disks-active', 'disks-errors', 'disks-gap-repartition'. | @@ -545,9 +545,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{library} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /HELD/i'). You can use the following variables: %{status}, %{name}, %{library} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /HELD/i'). You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | --warning-* --critical-* | Thresholds. Can be: 'jobqueues-total', 'jobqueue-jobs-active', 'jobqueue-jobs-scheduled', 'jobqueue-jobs-held'. | @@ -588,9 +588,9 @@ All available options for each service template are listed below: |:---------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-subsystem-name | Filter subsystems by name (can be a regexp). | | --filter-subsystem-library | Filter subsystems by library (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name}, %{library} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /ending\|restricted\|starting/i'). You can use the following variables: %{status}, %{name}, %{library} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{library} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /ending\|restricted\|starting/i'). You can use the following variables: %\{status\}, %\{name\}, %\{library\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{library\} | | --warning-* --critical-* | Thresholds. Can be: 'subsystems-total', 'subsystems-active', 'subsystems-ending', 'subsystems-inactive', 'subsystems-restricted', 'subsystems-starting', 'jobs-active'. | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md b/pp/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md index c2887c5ebf4f..d370b1569b5c 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-freebsd-snmp.md @@ -452,7 +452,7 @@ yum install centreon-plugin-Operatingsystems-Freebsd-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | Warning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -561,7 +561,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -792,9 +792,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md index fd1b077f1209..9685c363013b 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-centreon-monitoring-agent.md @@ -709,8 +709,8 @@ This monitoring connector relies on an integration supported by Centreon Engine | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --use-new-perfdata --verbose | | @@ -799,8 +799,8 @@ This monitoring connector relies on an integration supported by Centreon Engine |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -940,7 +940,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1181,9 +1181,9 @@ All available options for each service template are listed below: | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1212,9 +1212,9 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1304,8 +1304,8 @@ All available options for each service template are listed below: | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1328,9 +1328,9 @@ All available options for each service template are listed below: | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md index 8bc7b337b094..3d761182c73c 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-nrpe4.md @@ -843,8 +843,8 @@ yum install nagios-plugins-nrpe | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --use-new-perfdata --verbose | | @@ -933,8 +933,8 @@ yum install nagios-plugins-nrpe |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -1075,7 +1075,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1316,9 +1316,9 @@ All available options for each service template are listed below: | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1347,9 +1347,9 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1439,8 +1439,8 @@ All available options for each service template are listed below: | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1463,9 +1463,9 @@ All available options for each service template are listed below: | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md index 9b071556b02f..a9dcb7246a06 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp.md @@ -552,7 +552,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | CRITICALOUTDISCARD | Thresholds | | | | WARNINGOUTERROR | Thresholds | | | | CRITICALOUTERROR | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -619,7 +619,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | WARNINGIN | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -731,7 +731,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -946,9 +946,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | @@ -1053,9 +1053,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md index b3294015784a..aa23bd22b7a8 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmpv3.md @@ -470,8 +470,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Snmp | CRITICALOUTERROR | Thresholds | | | | WARNINGOUTTRAFFIC | Thresholds | | | | CRITICALOUTTRAFFIC | Thresholds | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | %{admstatus} eq "up" and %{opstatus} !~ /up\|dormant/ | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | %\{admstatus\} eq "up" and %\{opstatus\} !~ /up\|dormant/ | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -639,7 +639,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -821,9 +821,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md index ed2fdd63bc97..95d88676dfdb 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-ssh.md @@ -604,7 +604,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | FILTERDEVICE | Filter device name (can use regexp) | | | | FILTERMOUNTPOINT | Filter mount point name (can use regexp) | | | | FILTERTYPE | Filter mount point type (can use regexp) | | | -| CRITICALSTATUS | Critical threshold (default: '%{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i') | %{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i | | +| CRITICALSTATUS | Critical threshold (default: '%\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i') | %\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i | | | WARNINGSTATUS | Warning threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -616,13 +616,13 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | NTPMODE | Default mode for parsing and command: 'ntpq' (default), 'chronyc' or 'all' | ntpq | | | FILTERNAME | Filter peer name (can be a regexp) | | | | FILTERSTATE | Filter peer state (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGOFFSET | Warning threshold offset deviation value in milliseconds | | | | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -646,7 +646,7 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERSTATE | Filter filesystem type (regexp can be used) | | | | FILTERINTERFACE | Filter interface name (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGINDISCARD | Thresholds. | | | | CRITICALINDISCARD | Thresholds. | | | | WARNINGINERROR | Thresholds. | | | @@ -655,8 +655,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | CRITICALOUTDISCARD | Thresholds. | | | | WARNINGOUTERROR | Thresholds. | | | | CRITICALOUTERROR | Thresholds. | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | %{status} ne "RU" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | %\{status\} ne "RU" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -762,8 +762,8 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | Macro | Description | Default value | Mandatory | |:---------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | %{active} =~ /failed/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | %\{active\} =~ /failed/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -780,13 +780,13 @@ yum install centreon-plugin-Operatingsystems-Linux-Ssh | Macro | Description | Default value | Mandatory | |:----------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERINTERFACE | Filter interface name (regexp can be used) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | WARNINGIN | Warning threshold in percent for 'in' traffic | | | | CRITICALIN | Critical threshold in percent for 'in' traffic | | | | WARNINGOUT | Warning threshold in percent for 'out' traffic | | | | CRITICALOUT | Critical threshold in percent for 'out' traffic | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | %{status} ne "RU" | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | %\{status\} ne "RU" | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -821,7 +821,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-interface='' \ --unknown-status='' \ --warning-status='' \ - --critical-status='%{status} ne "RU"' \ + --critical-status='%\{status\} ne "RU"' \ --warning-in='' \ --critical-in='' \ --warning-out='' \ @@ -913,7 +913,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1124,7 +1124,7 @@ All available options for each service template are listed below: | --exclude-device | Exclude device name (can use regexp). | | --filter-type | Filter mount point type (can use regexp). | | --warning-status | Warning threshold. | -| --critical-status | Critical threshold (default: '%{options} !~ /^rw/i && %{type} !~ /tmpfs\|squashfs/i'). | +| --critical-status | Critical threshold (default: '%\{options\} !~ /^rw/i && %\{type\} !~ /tmpfs\|squashfs/i'). | @@ -1140,9 +1140,9 @@ All available options for each service template are listed below: | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1171,9 +1171,9 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1308,8 +1308,8 @@ All available options for each service template are listed below: | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Examples of status for some of this variables : %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Examples of status for some of this variables : %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1332,9 +1332,9 @@ All available options for each service template are listed below: | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md index bf0b017f13d6..a3bedd0b8cf9 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-linux-telegraf-agent.md @@ -873,8 +873,8 @@ This monitoring connector relies on an integration supported by Centreon Engine | CRITICALOFFSET | Critical threshold offset deviation value in milliseconds | | | | WARNINGPEERS | Warning threshold minimum amount of NTP-Server | | | | CRITICALPEERS | Critical threshold minimum amount of NTP-Server | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | | | | WARNINGSTRATUM | Warning threshold | | | | CRITICALSTRATUM | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --use-new-perfdata --verbose | | @@ -963,8 +963,8 @@ This monitoring connector relies on an integration supported by Centreon Engine |:---------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------|:-----------:| | FILTERNAME | Filter service name (can be a regexp) | .* | | | EXCLUDENAME | Exclude service name (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | | | | WARNINGTOTALDEAD | Thresholds | | | | CRITICALTOTALDEAD | Thresholds | | | | WARNINGTOTALEXITED | Thresholds | | | @@ -1104,7 +1104,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1345,9 +1345,9 @@ All available options for each service template are listed below: | --critical-offset | Critical threshold offset deviation value in milliseconds | | --warning-stratum | Warning threshold. | | --critical-stratum | Critical threshold. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{state}, %{rawstate}, %{type}, %{rawtype}, %{reach}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{state\}, %\{rawstate\}, %\{type\}, %\{rawtype\}, %\{reach\}, %\{display\} | @@ -1376,9 +1376,9 @@ All available options for each service template are listed below: | --statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). | | --statefile-key | Define the key to encrypt/decrypt the cache. | | --statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %%{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %%\{status\}, %\{display\} | | --warning-* | Warning threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --critical-* | Critical threshold in percent of total packets. Can be: in-error, out-error, in-discard, out-discard | | --filter-interface | Filter interface name (regexp can be used). | @@ -1468,8 +1468,8 @@ All available options for each service template are listed below: | --filter-name | Filter service name (can be a regexp). | | --exclude-name | Exclude service name (can be a regexp). | | --warning-* --critical-* | Thresholds. Can be: 'total-running', 'total-dead', 'total-exited', 'total-failed'. | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{active} =~ /failed/i'). You can use the following variables: %{display}, %{active}, %{sub}, %{load}, %{boot} Example of statuses for the majority of these variables: %{active}: active, inactive %{sub}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %{load}: loaded, not-found %{boot}: enabled, disabled, static, indirect | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{active\} =~ /failed/i'). You can use the following variables: %\{display\}, %\{active\}, %\{sub\}, %\{load\}, %\{boot\} Example of statuses for the majority of these variables: %\{active\}: active, inactive %\{sub\}: waiting, plugged, mounted, dead, failed, running, exited, listening, active %\{load\}: loaded, not-found %\{boot\}: enabled, disabled, static, indirect | @@ -1492,9 +1492,9 @@ All available options for each service template are listed below: | --critical-in | Critical threshold in percent for 'in' traffic. | | --warning-out | Warning threshold in percent for 'out' traffic. | | --critical-out | Critical threshold in percent for 'out' traffic. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %{status}, %{display} | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{status}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} ne "RU"'). You can use the following variables: %{status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{status\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} ne "RU"'). You can use the following variables: %\{status\}, %\{display\} | | --units | Units of thresholds (default: 'b/s') ('%', 'b/s'). Percent canbe used only if --speed is set. | | --filter-interface | Filter interface name (regexp can be used). | | --exclude-interface | Exclude interface name (regexp can be used). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md b/pp/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md index 8304b1dc6f37..a5eec91e364f 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-mac-snmp.md @@ -451,7 +451,7 @@ yum install centreon-plugin-Operatingsystems-Mac-Snmp | WARNINGIN | Warning threshold | 80 | | | CRITICALOUT | Critical threshold | 90 | | | WARNINGOUT | TWarning threshold | 80 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -560,7 +560,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -791,9 +791,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md index 1a2314dc5389..564b846a9091 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-centreon-monitoring-agent.md @@ -335,8 +335,8 @@ This connector relies on an integration supported by Centreon Engine and does no | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:---------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | `%{RebootPending} =~ /true/i` | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | `%{RebootPending} =~ /true/i` | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | TIMEOUT | Set timeout time for command execution | 10 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -457,7 +457,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -596,8 +596,8 @@ All available options for each service template are listed below: | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md index 82e0fc5f020f..f9ce59dcd7e8 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-restapi.md @@ -386,8 +386,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Restapi | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | %{RebootPending} =~ /true/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | %\{RebootPending\} =~ /true/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -590,7 +590,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -636,7 +636,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentification system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -662,7 +662,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentification system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -688,7 +688,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -714,7 +714,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -740,7 +740,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -766,7 +766,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -792,7 +792,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -818,7 +818,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -845,8 +845,8 @@ All available options for each service template are listed below: | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | @@ -870,7 +870,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -896,7 +896,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -922,7 +922,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -974,7 +974,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -1000,7 +1000,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | @@ -1043,7 +1043,7 @@ All available options for each service template are listed below: | --legacy-password | Specify password for old authentication system. | | --timeout | Threshold for HTTP timeout (Default: 5) | | --command | Set command. | -| --unknown-status | Warning threshold for http response code. (Default: '%{http\_code} \< 200 or %{http\_code} \>= 300') | +| --unknown-status | Warning threshold for http response code. (Default: '%\{http_code\} \< 200 or %\{http_code\} \>= 300') | | --warning-status | Warning threshold for http response code. | | --critical-status | Critical threshold for http response code. | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md index 6a5cbe72114c..86e7154475f4 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp.md @@ -389,8 +389,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Snmp | CRITICALPAUSED | Thresholds on services count | | | | WARNINGPAUSEPENDING | Thresholds on services count | | | | CRITICALPAUSEPENDING | Thresholds on services count | | | -| WARNINGSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state} | | | -| CRITICALSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state} | | | +| WARNINGSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\} | | | +| CRITICALSTATUS | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (example: a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -436,7 +436,7 @@ yum install centreon-plugin-Operatingsystems-Windows-Snmp | CRITICALIN | Thresholds | 90 | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (example: a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -532,7 +532,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -698,7 +698,7 @@ All available options for each service template are listed below: | Option | Description | |:-----------------------------------|:-------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter by service name (can be a regexp). | -| --warning-status --critical-status | Set WARNING or CRITICAL threshold for status. You can use the following variables: %{operating\_state}, %{installed\_state}. | +| --warning-status --critical-status | Set WARNING or CRITICAL threshold for status. You can use the following variables: %\{operating_state\}, %\{installed_state\}. | | --warning-* --critical-* | Thresholds on services count. Can be: 'total', 'active', 'continue-pending', 'pause-pending', 'paused'. | | --warning | DEPRECATED. Use --warning-active instead. | | --critical | DEPRECATED. Use --critical-active instead. | @@ -740,9 +740,9 @@ All available options for each service template are listed below: | --add-cast | Check interface cast. | | --add-speed | Check interface speed. | | --add-volume | Check interface data volume between two checks (not supposed to be graphed, useful for BI reporting). | -| --check-metrics | If the expression is true, metrics are checked (default: '%{opstatus} eq "up"'). | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{admstatus} eq "up" and %{opstatus} ne "up"'). You can use the following variables: %{admstatus}, %{opstatus}, %{duplexstatus}, %{display} | +| --check-metrics | If the expression is true, metrics are checked (default: '%\{opstatus\} eq "up"'). | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{admstatus\} eq "up" and %\{opstatus\} ne "up"'). You can use the following variables: %\{admstatus\}, %\{opstatus\}, %\{duplexstatus\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'total-port', 'total-admin-up', 'total-admin-down', 'total-oper-up', 'total-oper-down', 'in-traffic', 'out-traffic', 'in-error', 'in-discard', 'out-error', 'out-discard', 'in-ucast', 'in-bcast', 'in-mcast', 'out-ucast', 'out-bcast', 'out-mcast', 'speed' (b/s). | | --units-traffic | Units of thresholds for the traffic (default: 'percent\_delta') ('percent\_delta', 'bps', 'counter'). | | --units-errors | Units of thresholds for errors/discards (default: 'percent\_delta') ('percent\_delta', 'percent', 'delta', 'deltaps', 'counter'). | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md index d04cb5f7b69a..0f0279b437ad 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-telegraf-agent.md @@ -316,8 +316,8 @@ This connector relies on an integration supported by Centreon Engine and does no | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | `%{RebootPending} =~ /true/i` | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | `%{RebootPending} =~ /true/i` | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | TIMEOUT | Set timeout time for command execution (default: 50 sec). | 10 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -404,7 +404,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -471,8 +471,8 @@ All available options for each service template are listed below: | --command-options | Command options (Default: '-InputFormat none -NoLogo -EncodedCommand'). | | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md index 6349b3323ad4..1006da278b70 100644 --- a/pp/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md +++ b/pp/integrations/plugin-packs/procedures/operatingsystems-windows-wsman.md @@ -382,8 +382,8 @@ yum install centreon-plugin-Operatingsystems-Windows-Wsman | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | %{RebootPending} =~ /true/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | %\{RebootPending\} =~ /true/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (E.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -569,7 +569,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -684,8 +684,8 @@ All available options for each service template are listed below: |:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{RebootPending} =~ /true/i'). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{RebootPending}, %{WindowsUpdate}, %{CBServicing}, %{CCMClientSDK}, %{PendFileRename}, %{PendComputerRename}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{RebootPending\} =~ /true/i'). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{RebootPending\}, %\{WindowsUpdate\}, %\{CBServicing\}, %\{CCMClientSDK\}, %\{PendFileRename\}, %\{PendComputerRename\}. | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md b/pp/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md index c07ea28ee8e1..ae8aaaae9587 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-hpe-simplivity-restapi.md @@ -221,10 +221,10 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | Macro | Description | Default value | Mandatory | |:------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| -| UNKNOWNRAIDSTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNPHYSICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNLOGICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | -| UNKNOWNHOSTSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status}, %{name} | %{status} =~ /unknown/ | | +| UNKNOWNRAIDSTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNPHYSICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNLOGICALDRIVESTATUS | Set unknown threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | +| UNKNOWNHOSTSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /unknown/ | | | FILTERNAME | Filter hosts by name | | | | WARNINGHOSTCOMPONENTSGREEN | Thresholds | | | | CRITICALHOSTCOMPONENTSGREEN | Thresholds | | | @@ -244,16 +244,16 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | CRITICALHOSTSREMOVED | Thresholds | | | | WARNINGHOSTSSUSPECTED | Thresholds | | | | CRITICALHOSTSSUSPECTED | Thresholds | | | -| WARNINGHOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name} | %{status} =~ /suspected/ | | -| CRITICALHOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name} | %{status} =~ /faulty/ | | +| WARNINGHOSTSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /suspected/ | | +| CRITICALHOSTSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /faulty/ | | | WARNINGHOSTSUNKNOWN | Thresholds | | | | CRITICALHOSTSUNKNOWN | Thresholds | | | -| WARNINGLOGICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALLOGICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | -| WARNINGPHYSICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALPHYSICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | -| WARNINGRAIDSTATUS | Set warning threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /yellow/ | | -| CRITICALRAIDSTATUS | Set critical threshold for component status. You can use the following variables: %{status}, %{name} | %{status} =~ /red/ | | +| WARNINGLOGICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALLOGICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | +| WARNINGPHYSICALDRIVESTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALPHYSICALDRIVESTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | +| WARNINGRAIDSTATUS | Set warning threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /yellow/ | | +| CRITICALRAIDSTATUS | Set critical threshold for component status. You can use the following variables: %\{status\}, %\{name\} | %\{status\} =~ /red/ | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -281,10 +281,10 @@ yum install centreon-plugin-Virtualization-Hpe-Simplivity-Restapi | Macro | Description | Default value | Mandatory | |:-----------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNHASTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{ha\_status}, %{vm\_name} | %{ha\_status} =~ /unknown/ | | +| UNKNOWNHASTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ha_status\}, %\{vm_name\} | %\{ha_status\} =~ /unknown/ | | | FILTERVMNAME | Filter virtual machines by virtual machine name | | | -| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{ha\_status}, %{vm\_name} | %{ha\_status} =~ /degraded/ | | -| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status}, %{vm\_name} | | | +| WARNINGHASTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ha_status\}, %\{vm_name\} | %\{ha_status\} =~ /degraded/ | | +| CRITICALHASTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\}, %\{vm_name\} | | | | WARNINGSPACEUSAGE | Thresholds | | | | CRITICALSPACEUSAGE | Thresholds | | | | WARNINGSPACEUSAGEFREE | Thresholds | | | @@ -334,18 +334,18 @@ is able to monitor a resource using a command like this one (replace the sample --critical-hosts-suspected='' \ --warning-hosts-unknown='' \ --critical-hosts-unknown='' \ - --unknown-raid-status='%{status} =~ /unknown/' \ - --warning-raid-status='%{status} =~ /yellow/' \ - --critical-raid-status='%{status} =~ /red/' \ - --unknown-physical-drive-status='%{status} =~ /unknown/' \ - --warning-physical-drive-status='%{status} =~ /yellow/' \ - --critical-physical-drive-status='%{status} =~ /red/' \ - --unknown-logical-drive-status='%{status} =~ /unknown/' \ - --warning-logical-drive-status='%{status} =~ /yellow/' \ - --critical-logical-drive-status='%{status} =~ /red/' \ - --unknown-host-status='%{status} =~ /unknown/' \ - --warning-host-status='%{status} =~ /suspected/' \ - --critical-host-status='%{status} =~ /faulty/' \ + --unknown-raid-status='%\{status\} =~ /unknown/' \ + --warning-raid-status='%\{status\} =~ /yellow/' \ + --critical-raid-status='%\{status\} =~ /red/' \ + --unknown-physical-drive-status='%\{status\} =~ /unknown/' \ + --warning-physical-drive-status='%\{status\} =~ /yellow/' \ + --critical-physical-drive-status='%\{status\} =~ /red/' \ + --unknown-logical-drive-status='%\{status\} =~ /unknown/' \ + --warning-logical-drive-status='%\{status\} =~ /yellow/' \ + --critical-logical-drive-status='%\{status\} =~ /red/' \ + --unknown-host-status='%\{status\} =~ /unknown/' \ + --warning-host-status='%\{status\} =~ /suspected/' \ + --critical-host-status='%\{status\} =~ /faulty/' \ --verbose ``` @@ -470,7 +470,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -525,18 +525,18 @@ All available options for each service template are listed below: | Option | Description | |:---------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-name | Filter hosts by name. | -| --unknown-host-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-host-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /suspected/'). You can use the following variables: %{status}, %{name} | -| --critical-host-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} =~ /faulty/'). You can use the following variables: %{status}, %{name} | -| --unknown-raid-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-raid-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-raid-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | -| --unknown-logical-drive-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-logical-drive-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-logical-drive-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | -| --unknown-physical-drive-status | Set unknown threshold for component status (default: '%{status} =~ /unknown/'). You can use the following variables: %{status}, %{name} | -| --warning-physical-drive-status | Set warning threshold for component status (default: '%{status} =~ /yellow/'). You can use the following variables: %{status}, %{name} | -| --critical-physical-drive-status | Set critical threshold for component status (default: '%{status} =~ /red/'). You can use the following variables: %{status}, %{name} | +| --unknown-host-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-host-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /suspected/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-host-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} =~ /faulty/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-raid-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-raid-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-raid-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-logical-drive-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-logical-drive-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-logical-drive-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | +| --unknown-physical-drive-status | Set unknown threshold for component status (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{status\}, %\{name\} | +| --warning-physical-drive-status | Set warning threshold for component status (default: '%\{status\} =~ /yellow/'). You can use the following variables: %\{status\}, %\{name\} | +| --critical-physical-drive-status | Set critical threshold for component status (default: '%\{status\} =~ /red/'). You can use the following variables: %\{status\}, %\{name\} | | --warning-* --critical-* | Thresholds. Can be: 'hosts-alive', 'hosts-faulty', 'hosts-managed', 'hosts-removed', 'hosts-suspected', 'hosts-unknown', 'host-components-green', 'host-components-yellow', 'host-components-red', 'host-components-unknown'. | @@ -553,9 +553,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --filter-vm-name | Filter virtual machines by virtual machine name. | -| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN (default: '%{status} =~ /unknown/'). You can use the following variables: %{ha\_status}, %{vm\_name} | -| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: '%{status} =~ /degraded/'). You can use the following variables: %{ha\_status}, %{vm\_name} | -| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{ha\_status}, %{vm\_name} | +| --unknown-ha-status | Define the conditions to match for the status to be UNKNOWN (default: '%\{status\} =~ /unknown/'). You can use the following variables: %\{ha_status\}, %\{vm_name\} | +| --warning-ha-status | Define the conditions to match for the status to be WARNING (default: '%\{status\} =~ /degraded/'). You can use the following variables: %\{ha_status\}, %\{vm_name\} | +| --critical-ha-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{ha_status\}, %\{vm_name\} | | --warning-* --critical-* | Thresholds. Can be: 'space-usage', 'space-usage-free', 'space-usage-prct'. | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md b/pp/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md index c6e2c8f5d95d..d0d6aa83ef4e 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-hyperv-2012-nrpe.md @@ -261,10 +261,10 @@ yum install centreon-nrpe3-plugin | FILTERSTATUS | Filter virtual machine status (can be a regexp) | Running | | | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | %{integration\_service\_state} =~ /Update required/i | | -| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | not %{primary\_status} =~ /Ok/i | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | | | +| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | %\{integration_service_state\} =~ /Update required/i | | +| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | not %\{primary_status\} =~ /Ok/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -273,8 +273,8 @@ yum install centreon-nrpe3-plugin | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -298,8 +298,8 @@ yum install centreon-nrpe3-plugin |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | not %{status} =~ /Operating normally/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | not %\{status\} =~ /Operating normally/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -311,8 +311,8 @@ yum install centreon-nrpe3-plugin | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{vmaddition}, %{status} | %{vmaddition} =~ /not detected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %{vm}, %{vmaddition}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | %\{vmaddition\} =~ /not detected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -336,8 +336,8 @@ yum install centreon-nrpe3-plugin | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{status}, %{hostgroup} | not %{status} =~ /Running\|Stopped/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %{vm}, %{status}, %{hostgroup} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | not %\{status\} =~ /Running\|Stopped/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING . You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -361,7 +361,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-description="" \ --filter-hostgroup="" \ --warning-status="" \ - --critical-status="not %{status} =~ /Running|Stopped/i" \ + --critical-status="not %\{status\} =~ /Running|Stopped/i" \ --verbose' ``` @@ -426,7 +426,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -465,10 +465,10 @@ All available options for each service template are listed below: | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | | --filter-status | Filter virtual machine status (can be a regexp) (default: 'running'). | -| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%{integration\_service\_state} =~ /Update required/i'). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{primary\_status} !~ /Ok/i'). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | +| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%\{integration_service_state\} =~ /Update required/i'). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{primary_status\} !~ /Ok/i'). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | @@ -483,8 +483,8 @@ All available options for each service template are listed below: | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /Warning/i'). You can use the following variables: %{vm}, %{state}, %{health} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /Critical/i'). You can use the following variables: %{vm}, %{state}, %{health} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /Warning/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /Critical/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | @@ -518,8 +518,8 @@ All available options for each service template are listed below: | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Operating normally/i'). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Operating normally/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | @@ -541,8 +541,8 @@ All available options for each service template are listed below: | --filter-description | Filter by description (can be a regexp). | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{vmaddition}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{vmaddition} =~ /not detected/i'). You can use the following variables: %{vm}, %{vmaddition}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vmaddition\} =~ /not detected/i'). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | @@ -586,8 +586,8 @@ All available options for each service template are listed below: | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | | --filter-description | Filter by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{status}, %{hostgroup} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Running\|Stopped/i'). You can use the following variables: %{vm}, %{status}, %{hostgroup} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Running\|Stopped/i'). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md b/pp/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md index 3e348954679f..b5933a76147e 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-hyperv-nscp-restapi.md @@ -291,10 +291,10 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | | FILTERSTATUS | Filter virtual machine status (can be a regexp) | Running | | -| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | %{integration\_service\_state} =~ /Update required/i | | -| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | not %{primary\_status} =~ /Ok/i | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | | | +| WARNINGGLOBALSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | %\{integration_service_state\} =~ /Update required/i | | +| CRITICALGLOBALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | not %\{primary_status\} =~ /Ok/i | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -303,8 +303,8 @@ yum install | Macro | Description | Default value | Mandatory | |:---------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Warning/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{health} | %{health} =~ /Critical/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Warning/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | %\{health\} =~ /Critical/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -328,8 +328,8 @@ yum install |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERNOTE | Filter by VM notes (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | not %{status} =~ /Operating normally/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | not %\{status\} =~ /Operating normally/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -341,8 +341,8 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{vmaddition}, %{status} | %{vmaddition} =~ /not detected/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{vmaddition}, %{status} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | %\{vmaddition\} =~ /not detected/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -366,8 +366,8 @@ yum install | FILTERVM | Filter virtual machines (can be a regexp) | | | | FILTERDESCRIPTION | Filter by description (can be a regexp) | | | | FILTERHOSTGROUP | Filter hostgroup (can be a regexp) | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{vm}, %{status}, %{hostgroup} | not %{status} =~ /Running\|Stopped/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{vm}, %{status}, %{hostgroup} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | not %\{status\} =~ /Running\|Stopped/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed [here](#available-options). | --verbose | | @@ -404,7 +404,7 @@ is able to monitor a resource using a command like this one (replace the sample --filter-description="" \ --filter-hostgroup="" \ --warning-status="" \ - --critical-status="not %{status} =~ /Running|Stopped/i" \ + --critical-status="not %\{status\} =~ /Running|Stopped/i" \ --verbose' ``` @@ -469,7 +469,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -508,10 +508,10 @@ All available options for each service template are listed below: | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | | --filter-status | Filter virtual machine status (can be a regexp) (default: 'running'). | -| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%{integration\_service\_state} =~ /Update required/i'). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %{vm}, %{integration\_service\_state}, %{integration\_service\_version}, %{state} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%{primary\_status} !~ /Ok/i'). You can use the following variables: %{vm}, %{service}, %{primary\_status}, %{secondary\_status}, %{enabled} | +| --warning-global-status | Define the conditions to match for the status to be WARNING (default: '%\{integration_service_state\} =~ /Update required/i'). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --critical-global-status | Define the conditions to match for the status to be CRITICAL (default: ''). You can use the following variables: %\{vm\}, %\{integration_service_state\}, %\{integration_service_version\}, %\{state\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (default: '%\{primary_status\} !~ /Ok/i'). You can use the following variables: %\{vm\}, %\{service\}, %\{primary_status\}, %\{secondary_status\}, %\{enabled\} | @@ -526,8 +526,8 @@ All available options for each service template are listed below: | --ps-display | Display powershell script. | | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: '%{health} =~ /Warning/i'). You can use the following variables: %{vm}, %{state}, %{health} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{health} =~ /Critical/i'). You can use the following variables: %{vm}, %{state}, %{health} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: '%\{health\} =~ /Warning/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{health\} =~ /Critical/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{health\} | @@ -561,8 +561,8 @@ All available options for each service template are listed below: | --ps-exec-only | Print powershell output. | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-note | Filter by VM notes (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Operating normally/i'). You can use the following variables: %{vm}, %{state}, %{status}, %{is\_clustered} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Operating normally/i'). You can use the following variables: %\{vm\}, %\{state\}, %\{status\}, %\{is_clustered\} | @@ -584,8 +584,8 @@ All available options for each service template are listed below: | --filter-description | Filter by description (can be a regexp). | | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{vmaddition}, %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{vmaddition} =~ /not detected/i'). You can use the following variables: %{vm}, %{vmaddition}, %{status} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{vmaddition\} =~ /not detected/i'). You can use the following variables: %\{vm\}, %\{vmaddition\}, %\{status\} | @@ -629,8 +629,8 @@ All available options for each service template are listed below: | --filter-vm | Filter virtual machines (can be a regexp). | | --filter-hostgroup | Filter hostgroup (can be a regexp). | | --filter-description | Filter by description (can be a regexp). | -| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %{vm}, %{status}, %{hostgroup} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{status} !~ /Running\|Stopped/i'). You can use the following variables: %{vm}, %{status}, %{hostgroup} | +| --warning-status | Define the conditions to match for the status to be WARNING (default: ''). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{status\} !~ /Running\|Stopped/i'). You can use the following variables: %\{vm\}, %\{status\}, %\{hostgroup\} | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md index b3ab7f4dabff..fb62323c818d 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md @@ -555,12 +555,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGREAD | Warning threshold | | | | CRITICALREAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGTOTALREAD | Warning threshold | | | | CRITICALTOTALREAD | Critical threshold | | | | WARNINGTOTALWRITE | Warning threshold | | | @@ -574,7 +574,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | @@ -582,8 +582,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALREADTOTAL | Thresholds | | | | WARNINGREADVM | Thresholds | | | | CRITICALREADVM | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | WARNINGWRITETOTAL | Thresholds | | | @@ -597,12 +597,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGSNAPSHOT | Warning threshold | | | | CRITICALSNAPSHOT | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -612,13 +612,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | UNIT | | % | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | | CRITICALPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 80 | | | CRITICALUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 90 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -628,14 +628,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | %{accessible} !~ /^true\|1$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | %\{accessible\} !~ /^true\|1$/i | | | DATASTORENAME | The connector will only take into account alerts coming from the datastores listed here | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -652,8 +652,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERTIME | The connector will ignore any alert older than the time period specified here (in seconds). | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -665,13 +665,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTOTALCPUMHZ | Warning threshold | | | | CRITICALTOTALCPUMHZ | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -682,11 +682,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGWRITELATENCY | Warning threshold | | | | CRITICALWRITELATENCY | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -696,15 +696,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGPROBLEMS | Thresholds | | | | CRITICALPROBLEMS | Thresholds | | | | WARNINGPROBLEMSRED | Thresholds | | | | CRITICALPROBLEMSRED | Thresholds | | | | WARNINGPROBLEMSYELLOW | Thresholds | | | | CRITICALPROBLEMSYELLOW | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTOTALPROBLEMS | Thresholds | | | | CRITICALTOTALPROBLEMS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -714,15 +714,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNING | Warning threshold (can use unit option) | | | | CRITICAL | Critical threshold (can use unit option) | | | | WARNINGOVERHEADMEMORY | Threshold overhead | | | | CRITICALOVERHEADMEMORY | Critical threshold | | | | WARNINGSTATEMEMORY | Warning threshold. For state != 'high': --warning-state=0 | | | | CRITICALSTATEMEMORY | Critical threshold. For state != 'high': --warning-state=0 | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -730,12 +730,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i && %{maintenance} =~ /false/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i | | | FILTERSERVICES | Filter services you want to check (can be a regexp) | ^(?!(snmpd\|xorg)$) | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | %{policy} =~ /^on\|automatic/i && !%{running} | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | %\{policy\} =~ /^on\|automatic/i && !%\{running\} | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -743,12 +743,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -756,7 +756,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | %{status} !~ /^connected$/i && %{maintenance} =~ /false/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | %\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i | | | FILTERADAPTERNAME | Filter adapters by name (can be a regexp) | | | | FILTERLUNNAME | Filter luns by name (can be a regexp) | | | | FILTERPATHNAME | Filter paths by name (can be a regexp) | | | @@ -766,8 +766,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALADAPTERSOFFLINE | Thresholds | | | | WARNINGADAPTERSONLINE | Thresholds | | | | CRITICALADAPTERSONLINE | Thresholds | | | -| CRITICALADAPTERSTATUS | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /fault/ | | -| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALADAPTERSTATUS | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /fault/ | | +| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGADAPTERSTOTAL | Thresholds | | | | CRITICALADAPTERSTOTAL | Thresholds | | | | WARNINGADAPTERSUNKNOWN | Thresholds | | | @@ -782,8 +782,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALLUNSOK | Threshold | | | | WARNINGLUNSQUIESCED | Threshold | | | | CRITICALLUNSQUIESCED | Threshold | | | -| WARNINGLUNSTATUS | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /degraded\|quiesced/ | | -| CRITICALLUNSTATUS | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /lostcommunication\|error/ | | +| WARNINGLUNSTATUS | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /degraded\|quiesced/ | | +| CRITICALLUNSTATUS | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /lostcommunication\|error/ | | | WARNINGLUNSTOTAL | Threshold | | | | CRITICALLUNSTOTAL | Threshold | | | | WARNINGLUNSUNKNOWN | Threshold | | | @@ -796,14 +796,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALPATHSDISABLED | Threshold | | | | WARNINGPATHSSTANDBY | Threshold | | | | CRITICALPATHSSTANDBY | Threshold | | | -| CRITICALPATHSTATUS | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /dead/ | | -| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALPATHSTATUS | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /dead/ | | +| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGPATHSTOTAL | Threshold | | | | CRITICALPATHSTOTAL | Threshold | | | | WARNINGPATHSUNKNOWN | Threshold | | | | CRITICALPATHSUNKNOWN | Threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -811,9 +811,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -825,9 +825,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | -2:2 | | | CRITICALTIME | Critical threshold in seconds | -5:5 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -838,8 +838,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERNICNAME | ESX nic to check. If not set, we check all nics | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGDROPPEDIN | Thresholds | | | | CRITICALDROPPEDIN | Thresholds | | | | WARNINGDROPPEDOUT | Thresholds | | | @@ -850,12 +850,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALHOSTTRAFFICOUT | Thresholds | | | | WARNINGIN | Thresholds | 80 | | | CRITICALIN | Thresholds | 90 | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | %{link\_status} !~ /up/ | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | %\{link_status\} !~ /up/ | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -863,9 +863,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | | | | CRITICALTIME | Critical threshold in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -875,13 +875,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -897,11 +897,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:--------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | %{status} !~ /^connected$/i | | -| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | %{maintenance} !~ /false/ | | -| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | +| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | %\{maintenance\} !~ /false/ | | +| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -924,7 +924,7 @@ is able to monitor a resource using a command like this one (replace the sample --connector-port='5700' \ --container='default' \ --esx-hostname='' \ - --unknown-status='%{status} !~ /^connected$/i' \ + --unknown-status='%\{status\} !~ /^connected$/i' \ --warning-status='' \ --critical-status='' \ --warning-total-on='' \ @@ -1036,7 +1036,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1065,9 +1065,9 @@ All generic options are listed here: | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different than 300 or 20. | | --time-shift | Can shift the time. We the following option you can average X counters values (default: 0). | | --case-insensitive | Searchs are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Modes options @@ -1081,9 +1081,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | | --critical-* | Critical threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | @@ -1096,9 +1096,9 @@ All available options for each service template are listed below: | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --detail-iops-min | Only display VMs with iops higher value (default: 50). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: 'read-total', 'write-total', 'read', 'write', 'read-vm', 'write-vm'. | @@ -1109,9 +1109,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total', 'snapshot'. | | --critical-* | Critical threshold. Can be: 'total', 'snapshot'. | @@ -1125,9 +1125,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --filter-host | Filter datastores attached to hosts (can be a regexp). | | --refresh | Explicitly ask vmware to refreshes free-space and capacity values (slower). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned'. | @@ -1138,9 +1138,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1167,8 +1167,8 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-time | The connector will ignore any alert older than the time period specified here (in seconds). | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1181,9 +1181,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | @@ -1198,9 +1198,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'read-latency', 'write-latency'. | | --critical-* | Critical threshold. Can be: 'read-latency', 'write-latency'. | @@ -1214,9 +1214,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --storage-status | Check storage(s) status. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-problems', 'problems', 'problems-yellow', 'problems-red', 'sensor-temperature', 'sensor-fan', 'sensor-voltage', 'sensor-power'. | @@ -1230,9 +1230,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-consumed-memory | Warning threshold (can use unit option). | | --critical-consumed-memory | Critical threshold (can use unit option). | | --warning-overhead-memory | Overhead threshold. | @@ -1251,11 +1251,11 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-services | Filter services you want to check (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | @@ -1266,12 +1266,12 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -1285,15 +1285,15 @@ All available options for each service template are listed below: | --filter-adapter-name | Filter adapters by name (can be a regexp). | | --filter-lun-name | Filter luns by name (can be a regexp). | | --filter-path-name | Filter paths by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | -| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-adapter-status | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-lun-status | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | -| --critical-lun-status | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-path-status | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-path-status | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-adapter-status | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-lun-status | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-lun-status | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-path-status | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-path-status | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'adapters-total', 'adapters-online', 'adapters-offline', 'adapters-fault', 'adapters-unknown', | @@ -1305,9 +1305,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | @@ -1320,9 +1320,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1337,12 +1337,12 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --nic-name | ESX nic to check. If not set, we check all nics. | | --filter-vswitch-name | Filter vswitch by name. It monitors only ESX nic that belongs to the filtered vswitches. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'host-traffic-in' (b/s), 'host-traffic-out' (b/s), 'vswitch-traffic-in' (b/s), 'vswitch-traffic-out' (b/s), 'link-traffic-in' (%), 'link-traffic-out' (%), 'link-dropped-in', 'link-dropped-out'. | | --no-proxyswitch | Use the following option if you are checking an ESX 3.x version (it's mandatory). | @@ -1355,9 +1355,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1370,9 +1370,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1385,11 +1385,11 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | -| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | +| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md index 9938156bf47d..7e112691d426 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic.md @@ -795,9 +795,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -806,9 +806,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------|:-----------:| | FILTERNAME | cluster to check. If not set, we check all clusters | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | %{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | %\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -817,8 +817,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTERTIME | Do not check alarms older than specified time (value in seconds) | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -832,8 +832,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------------|:------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Datacenter to check. If not set, we check all datacenters | .* | | | FILTERTIME | Do not check alarms older than specified time (value in seconds) | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -846,11 +846,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGREAD | Warning threshold | | | | CRITICALREAD | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGTOTALREAD | Warning threshold | | | | CRITICALTOTALREAD | Critical threshold | | | | WARNINGTOTALWRITE | Warning threshold | | | @@ -865,15 +865,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------------|:-------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\| 1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\| 1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | | WARNINGREADTOTAL | Thresholds | | | | CRITICALREADTOTAL | Thresholds | | | | WARNINGREADVM | Thresholds | | | | CRITICALREADVM | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | WARNINGWRITETOTAL | Thresholds | | | @@ -888,11 +888,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------|:-------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGSNAPSHOT | Warning threshold | | | | CRITICALSNAPSHOT | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{accessible\} | | | | WARNINGTOTAL | Warning threshold | | | | CRITICALTOTAL | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -904,11 +904,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:--------------------|:-------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | | UNIT | Set this option to '%' if you want the thresholds to be interpreted as a percentage of the maximum possible value instead of as an absolute threshold. | % | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | | CRITICALPROVISIONED | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 80 | | | CRITICALUSAGE | Thresholds. : 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned' | 90 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -919,13 +919,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | The connector will only take into account alerts coming from the datastores listed here | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\ |1$/i'). You can use the following variables: %{accessible} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\ |1$/i'). You can use the following variables: %\{accessible\} | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -943,8 +943,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERTIME | The connector will ignore any alert older than the time period specified here (in seconds). | 3600 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /yellow/i | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{name}, %{entity}, %{type} | %{status} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /yellow/i | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\} | %\{status\} =~ /red/i | | | WARNINGTOTALALARMWARNING | Warning threshold | | | | CRITICALTOTALALARMWARNING | Critical threshold | | | | WARNINGTOTALALARMCRITICAL | Warning threshold | | | @@ -957,13 +957,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTOTALCPUMHZ | Warning threshold | | | | CRITICALTOTALCPUMHZ | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -975,11 +975,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERESXNAME | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGREADLATENCY | Warning threshold | | | | CRITICALREADLATENCY | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGWRITELATENCY | Warning threshold | | | | CRITICALWRITELATENCY | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -990,15 +990,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-------------------------------------------------------------------------------------------------------------------------------|:----------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{status} | %{status} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{status\} | %\{status\} !~ /^connected$/i | | | WARNINGPROBLEMS | Thresholds | | | | CRITICALPROBLEMS | Thresholds | | | | WARNINGPROBLEMSRED | Thresholds | | | | CRITICALPROBLEMSRED | Thresholds | | | | WARNINGPROBLEMSYELLOW | Thresholds | | | | CRITICALPROBLEMSYELLOW | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTOTALPROBLEMS | Thresholds | | | | CRITICALTOTALPROBLEMS | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1009,15 +1009,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNING | Warning threshold (can use unit option) | | | | CRITICAL | Critical threshold (can use unit option) | | | | WARNINGOVERHEADMEMORY | Overhead threshold | | | | CRITICALOVERHEADMEMORY | Critical threshold | | | | WARNINGSTATEMEMORY | Warning threshold. For state != 'high': --warning-state=0 | | | | CRITICALSTATEMEMORY | Critical threshold. For state != 'high': --warning-state=0 | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1027,11 +1027,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERSERVICES | Filter services you want to check (can be a regexp) | ^(?!(snmpd\|xorg)$) | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | | | -| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{running}, %{label}, %{policy} | %{policy} =~ /^on\|automatic/i && !%{running} | | -| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{running}, %{label}, %{policy} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | | | +| CRITICALSERVICESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | %\{policy\} =~ /^on\|automatic/i && !%\{running\} | | +| WARNINGSERVICESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1040,12 +1040,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1057,15 +1057,15 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTERADAPTERNAME | Filter adapters by name (can be a regexp) | | | | FILTERLUNNAME | Filter luns by name (can be a regexp) | | | | FILTERPATHNAME | Filter paths by name (can be a regexp) | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | | | | WARNINGADAPTERSFAULT | Thresholds | | | | CRITICALADAPTERSFAULT | Thresholds | | | | WARNINGADAPTERSOFFLINE | Thresholds | | | | CRITICALADAPTERSOFFLINE | Thresholds | | | | WARNINGADAPTERSONLINE | Thresholds | | | | CRITICALADAPTERSONLINE | Thresholds | | | -| CRITICALADAPTERSTATUS | Set critical threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /fault/ | | -| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALADAPTERSTATUS | Set critical threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /fault/ | | +| WARNINGADAPTERSTATUS | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGADAPTERSTOTAL | Thresholds | | | | CRITICALADAPTERSTOTAL | Thresholds | | | | WARNINGADAPTERSUNKNOWN | Thresholds | | | @@ -1080,8 +1080,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALLUNSOK | Set critical threshold for the count of LUNs that are operational. | | | | WARNINGLUNSQUIESCED | Set warning threshold for the count of LUNs that are in a quiesced state. | | | | CRITICALLUNSQUIESCED | Set critical threshold for the count of LUNs that are in a quiesced state. | | | -| WARNINGLUNSTATUS | Set warning threshold for lun status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /degraded\|quiesced/ | | -| CRITICALLUNSTATUS | Set critical threshold for lun status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /lostcommunication\|error/ | | +| WARNINGLUNSTATUS | Set warning threshold for lun status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /degraded\|quiesced/ | | +| CRITICALLUNSTATUS | Set critical threshold for lun status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /lostcommunication\|error/ | | | WARNINGLUNSTOTAL | Set warning threshold for the total count of LUNs. | | | | CRITICALLUNSTOTAL | Set critical threshold for the total count of LUNs. | | | | WARNINGLUNSUNKNOWN | Set warning threshold for the count of LUNs with an unknown status. | | | @@ -1094,14 +1094,14 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALPATHSDISABLED | Set critical threshold for the count of disabled storage paths. | | | | WARNINGPATHSSTANDBY | Set warning threshold for the count of storage paths in standby mode. | | | | CRITICALPATHSSTANDBY | Set critical threshold for the count of storage paths in standby mode. | | | -| CRITICALPATHSTATUS | Set critical threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | %{status} =~ /dead/ | | -| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | | | +| CRITICALPATHSTATUS | Set critical threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | %\{status\} =~ /dead/ | | +| WARNINGPATHSTATUS | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | | | WARNINGPATHSTOTAL | Set warning threshold for the total count of storage paths. | | | | CRITICALPATHSTOTAL | Set critical threshold for the total count of storage paths. | | | | WARNINGPATHSUNKNOWN | Set warning threshold for the count of storage paths with an unknown status. | | | | CRITICALPATHSUNKNOWN | Set critical threshold for the count of storage paths with an unknown status. | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1110,9 +1110,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -1125,9 +1125,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | -2:2 | | | CRITICALTIME | Critical threshold in seconds | -5:5 | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1139,8 +1139,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTERESXNAME | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | | FILTERNICNAME | ESX nic to check. If not set, we check all nics | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| UNKNOWNLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGDROPPEDIN | Thresholds | | | | CRITICALDROPPEDIN | Thresholds | | | | WARNINGDROPPEDOUT | Thresholds | | | @@ -1151,12 +1151,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALHOSTTRAFFICOUT | Thresholds | | | | WARNINGIN | Thresholds | 80 | | | CRITICALIN | Thresholds | 90 | | -| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | | | -| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | | | +| WARNINGLINKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | | | +| CRITICALLINKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | | | WARNINGOUT | Thresholds | 80 | | | CRITICALOUT | Thresholds | 90 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1165,9 +1165,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGTIME | Warning threshold in seconds | | | | CRITICALTIME | Critical threshold in seconds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1178,13 +1178,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | | WARNINGOFF | Warning threshold | | | | CRITICALOFF | Critical threshold | | | | WARNINGON | Warning threshold | | | | CRITICALON | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | WARNINGSUSPENDED | Warning threshold | | | | CRITICALSUSPENDED | Critical threshold | | | | WARNINGTOTALOFF | Warning threshold | | | @@ -1201,11 +1201,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:--------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------|:-----------:| | FILTER | Hostnames of the ESX to monitor. If not set, we check all ESX | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | | | -| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{maintenance} | %{maintenance} !~ /false/ | | -| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{maintenance} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | | | +| CRITICALMAINTENANCESTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{maintenance\} | %\{maintenance\} !~ /false/ | | +| WARNINGMAINTENANCESTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{maintenance\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1235,13 +1235,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGREADY | Warning threshold | 5 | | | CRITICALREADY | Critical threshold | 10 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGUSAGE | Warning threshold | 80 | | | CRITICALUSAGE | Critical threshold | 90 | | | WARNINGUSAGEMHZ | Warning threshold | | | @@ -1256,13 +1256,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGMAXTOTALLATENCY | Thresholds | | | | CRITICALMAXTOTALLATENCY | Thresholds | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1275,9 +1275,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | | FILTERDEVICE | Device to check (Required) (Example: --device='VirtualCdrom') | | X | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | | CRITICALTOTALDEVICECONNECTED | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1289,12 +1289,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{limit} != -1 | | -| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | +| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{limit\} != -1 | | +| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1304,7 +1304,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGACTIVE | Warning threshold | | | @@ -1315,8 +1315,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALOVERHEAD | Critical threshold | | | | WARNINGSHARED | Warning threshold | | | | CRITICALSHARED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1336,13 +1336,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -1352,9 +1352,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | FILTER | Hostnames of the VMs to monitor. If not set, we check all VMs | .* | | | VMUUID | Filter by UUID | | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -1592,7 +1592,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Filter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -1621,9 +1621,9 @@ All generic options are listed here: | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different than 300 or 20. | | --time-shift | Can shift the time. We the following option you can average X counters values (default: 0). | | --case-insensitive | Searchs are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status. You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status. You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status. You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status. You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Modes options @@ -1657,9 +1657,9 @@ All available options for each service template are listed below: | --cluster-name | cluster to check. If not set, we check all clusters. | | --filter | Cluster name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | @@ -1669,9 +1669,9 @@ All available options for each service template are listed below: | --cluster-name | cluster to check. If not set, we check all clusters. | | --filter | Cluster name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i \|\| %{vsan\_status} =~ /gray/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i \|\| %{vsan\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i \|\| %{vsan\_status} =~ /red/i'). You can use the following variables: %{overall\_status}, %{vsan\_status}, %{drs\_enabled}, %{ha\_enabled} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i \|\| %\{vsan_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i \|\| %\{vsan_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i \|\| %\{vsan_status\} =~ /red/i'). You can use the following variables: %\{overall_status\}, %\{vsan_status\}, %\{drs_enabled\}, %\{ha_enabled\} | @@ -1696,8 +1696,8 @@ All available options for each service template are listed below: | --filter-time | Do not check alarms older than specified time (value in seconds). | | --filter-type | Check only alarms for specified type(s). Can be a regex. Can be for example: --filter-type='VirtualMachine' will only show alarms for VirtualMachines. | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1724,8 +1724,8 @@ All available options for each service template are listed below: | --filter-time | Do not check alarms older than specified time (value in seconds). | | --filter-type | Check only alarms for specified type(s). Can be a regex. Can be for example: --filter-type='VirtualMachine' will only show alarms for VirtualMachines. | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1737,9 +1737,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here. | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | | --critical-* | Critical threshold. Can be: 'total-read', 'total-write', 'read', 'write'. | @@ -1752,9 +1752,9 @@ All available options for each service template are listed below: | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --detail-iops-min | Only display VMs with iops higher value (default: 50). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: 'read-total', 'write-total', 'read', 'write', 'read-vm', 'write-vm'. | @@ -1765,9 +1765,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here. | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total', 'snapshot'. | | --critical-* | Critical threshold. Can be: 'total', 'snapshot'. | @@ -1781,9 +1781,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --filter-host | Filter datastores attached to hosts (can be a regexp). | | --refresh | Explicitly ask vmware to refreshes free-space and capacity values (slower). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* --critical-* | Thresholds. Can be: Can be: 'usage' (B), 'usage-free' (B), 'usage-prct' (%), 'provisioned'. | @@ -1794,9 +1794,9 @@ All available options for each service template are listed below: | --datastore-name | The connector will only take into account alerts coming from the datastores listed here. | | --filter | Datastore name is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{accessible} !~ /^true\|1$/i'). You can use the following variables: %{accessible} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{accessible} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{accessible} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{accessible\} !~ /^true\|1$/i'). You can use the following variables: %\{accessible\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{accessible\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{accessible\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -1823,8 +1823,8 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-time | The connector will ignore any alert older than the time period specified here (in seconds). | | --memory | Check new alarms only. | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%{status} =~ /yellow/i). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%{status} =~ /red/i'). You can use the following variables: %{status}, %{name}, %{entity}, %{type}. | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: '%\{status\} =~ /yellow/i). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{status\} =~ /red/i'). You can use the following variables: %\{status\}, %\{name\}, %\{entity\}, %\{type\}. | | --warning-* | Warning threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | | --critical-* | Critical threshold. Can be: 'total-alarm-warning', 'total-alarm-critical'. | @@ -1837,9 +1837,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu'. | @@ -1854,9 +1854,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'read-latency', 'write-latency'. | | --critical-* | Critical threshold. Can be: 'read-latency', 'write-latency'. | @@ -1870,9 +1870,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --storage-status | Check storage(s) status. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'total-problems', 'problems', 'problems-yellow', 'problems-red', 'sensor-temperature', 'sensor-fan', 'sensor-voltage', 'sensor-power'. | @@ -1886,9 +1886,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-consumed-memory | Warning threshold (can use unit option). | | --critical-consumed-memory | Critical threshold (can use unit option). | | --warning-overhead-memory | Overhead threshold. | @@ -1907,11 +1907,11 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --filter-services | Filter services you want to check (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{running}, %{label}, %{policy} | -| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%{policy} =~ /^on\|automatic/i && !%{running}'). You can use the following variables: %{running}, %{label}, %{policy} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-service-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | +| --critical-service-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{policy\} =~ /^on\|automatic/i && !%\{running\}'). You can use the following variables: %\{running\}, %\{label\}, %\{policy\} | @@ -1922,12 +1922,12 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -1941,15 +1941,15 @@ All available options for each service template are listed below: | --filter-adapter-name | Filter adapters by name (can be a regexp). | | --filter-lun-name | Filter luns by name (can be a regexp). | | --filter-path-name | Filter paths by name (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i && %{maintenance} =~ /false/i'). You can use the following variables: %{status}, %{maintenance} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{status}, %{maintenance} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{status}, %{maintenance} | -| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-adapter-status | Set critical threshold for adapter status (Default: '%{status} =~ /fault/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-lun-status | Set warning threshold for lun status (Default: '%{status} =~ /degraded\|quiesced/'). You can use the following variables: %{name}, %{host}, %{status} | -| --critical-lun-status | Set critical threshold for lun status (Default: '%{status} =~ /lostcommunication\|error/'). You can use the following variables: %{name}, %{host}, %{status} | -| --warning-path-status | Set warning threshold for path status. You can use the following variables: %{name}, %{host}, %{status} | -| --critical-path-status | Set critical threshold for path status (Default: '%{status} =~ /dead/'). You can use the following variables: %{name}, %{host}, %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i && %\{maintenance\} =~ /false/i'). You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{status\}, %\{maintenance\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{status\}, %\{maintenance\} | +| --warning-adapter-status | Set warning threshold for adapter status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-adapter-status | Set critical threshold for adapter status (Default: '%\{status\} =~ /fault/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-lun-status | Set warning threshold for lun status (Default: '%\{status\} =~ /degraded\|quiesced/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-lun-status | Set critical threshold for lun status (Default: '%\{status\} =~ /lostcommunication\|error/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --warning-path-status | Set warning threshold for path status. You can use the following variables: %\{name\}, %\{host\}, %\{status\} | +| --critical-path-status | Set critical threshold for path status (Default: '%\{status\} =~ /dead/'). You can use the following variables: %\{name\}, %\{host\}, %\{status\} | | --warning-* --critical-* | Thresholds. Can be: 'adapters-total', 'adapters-online', 'adapters-offline', 'adapters-fault', 'adapters-unknown', | @@ -1961,9 +1961,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | @@ -1976,9 +1976,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -1993,12 +1993,12 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --nic-name | ESX nic to check. If not set, we check all nics. | | --filter-vswitch-name | Filter vswitch by name. It monitors only ESX nic that belongs to the filtered vswitches. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{link\_status}, %{display} | -| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%{link\_status} !~ /up/'). You can use the following variables: %{link\_status}, %{display} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --unknown-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --warning-link-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{link_status\}, %\{display\} | +| --critical-link-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{link_status\} !~ /up/'). You can use the following variables: %\{link_status\}, %\{display\} | | --warning-* --critical-* | Thresholds. Can be: 'host-traffic-in' (b/s), 'host-traffic-out' (b/s), 'vswitch-traffic-in' (b/s), 'vswitch-traffic-out' (b/s), 'link-traffic-in' (%), 'link-traffic-out' (%), 'link-dropped-in', 'link-dropped-out'. | | --no-proxyswitch | Use the following option if you are checking an ESX 3.x version (it's mandatory). | @@ -2011,9 +2011,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-time | Warning threshold in seconds. | | --critical-time | Critical threshold in seconds. | @@ -2026,9 +2026,9 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | | --warning-* | Warning threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | | --critical-* | Critical threshold. Can be: 'total-on', 'total-off', 'total-suspended', 'on', 'off', 'suspended'. | @@ -2041,11 +2041,11 @@ All available options for each service template are listed below: | --filter | ESX hostname is a regexp. | | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{status} !~ /^connected$/i'). You can use the following variables: %{status} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{status} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{status} | -| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{maintenance} | -| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%{maintenance} !~ /false/'). You can use the following variables: %{maintenance} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{status\} !~ /^connected$/i'). You can use the following variables: %\{status\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{status\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{status\} | +| --warning-maintenance-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{maintenance\} | +| --critical-maintenance-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{maintenance\} !~ /false/'). You can use the following variables: %\{maintenance\} | @@ -2071,9 +2071,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | @@ -2092,9 +2092,9 @@ All available options for each service template are listed below: | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Datastore name is a regexp. | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | @@ -2111,9 +2111,9 @@ All available options for each service template are listed below: | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | | --device | Device to check (Required) (Example: --device='VirtualCdrom'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | | --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | @@ -2128,12 +2128,12 @@ All available options for each service template are listed below: | --filter-os | Filter also virtual machines OS name (can be a regexp). | | --display-description | Display virtual machine description. | | --check-disk-limit | Check disk limits (since vsphere 5.0). | -| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | @@ -2148,9 +2148,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are on free space left. | | --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | @@ -2189,12 +2189,12 @@ All available options for each service template are listed below: | --scope-datacenter | Search in following datacenter(s) (can be a regexp). | | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | -| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -2209,9 +2209,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in following cluster(s) (can be a regexp). | | --scope-host | Search in following host(s) (can be a regexp). | | --display-description | Display virtual machine description. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 05dc0d04386a..8f43dee2368f 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -398,13 +398,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNINGCPU | Warning threshold | | | | CRITICALCPU | Critical threshold | | | | WARNINGREADY | Warning threshold | 5 | | | CRITICALREADY | Critical threshold | 10 | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGUSAGE | Warning threshold | 80 | | | CRITICALUSAGE | Critical threshold | 90 | | | WARNINGUSAGEMHZ | Warning threshold | | | @@ -417,13 +417,13 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| | FILTERDATASTORENAME | Datastore to check. If not set, we check all datastores | .* | | -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNINGMAXTOTALLATENCY | Thresholds | | | | CRITICALMAXTOTALLATENCY | Thresholds | | | | WARNINGREAD | Thresholds | | | | CRITICALREAD | Thresholds | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGWRITE | Thresholds | | | | CRITICALWRITE | Thresholds | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -433,10 +433,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | %{connection\_state} !~ /^connected$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | %\{connection_state\} !~ /^connected$/i | | | FILTERDEVICE | Device to check (required). (Example: --device='VirtualCdrom') | | X | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | | CRITICALTOTALDEVICECONNECTED | Critical threshold | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -446,12 +446,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------|:-----------:| -| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | -| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | %{connection\_state} !~ /^connected$/i \|\| %{limit} != -1 | | -| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | | | +| CRITICALCPUSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGCPUSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALDISKSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGDISKSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | +| CRITICALMEMORYSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | %\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1 | | +| WARNINGMEMORYSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -459,7 +459,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | | WARNING | Warning threshold | | | | CRITICAL | Critical threshold | | | | WARNINGACTIVE | Warning threshold | | | @@ -470,8 +470,8 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | CRITICALOVERHEAD | Critical threshold | | | | WARNINGSHARED | Warning threshold | | | | CRITICALSHARED | Critical threshold | | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -488,12 +488,12 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i | | -| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /gray/i | | -| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /yellow/i | | -| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | %{overall\_status} =~ /red/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i | | +| UNKNOWNOVERALLSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /gray/i | | +| WARNINGOVERALLSTATUS | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /yellow/i | | +| CRITICALOVERALLSTATUS | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | %\{overall_status\} =~ /red/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | --verbose | | @@ -501,9 +501,9 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|:-----------:| -| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | %{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i | | -| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | -| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | | | +| UNKNOWNSTATUS | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | %\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i | | +| WARNINGSTATUS | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | +| CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | | | WARNINGSWAPIN | Warning threshold | | | | CRITICALSWAPIN | Critical threshold | | | | WARNINGSWAPOUT | Warning threshold | | | @@ -549,7 +549,7 @@ is able to monitor a resource using a command like this one (replace the sample --container='default' \ --vm-hostname='' \ --filter-uuid='' \ - --unknown-status='%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i' \ + --unknown-status='%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i' \ --warning-status='' \ --critical-status='' \ --warning-swap-in='' \ @@ -653,7 +653,7 @@ All generic options are listed here: | --verbose | Display extended status information (long output). | | --debug | Display debug messages. | | --filter-perfdata | Keep only perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | -| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Eg: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; | | --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[m ax\]\] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic\_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic\_in,,percent() | | --extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation\[,\[ne wuom\],\[min\],\[max\]\] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets\_wrong,sum(packets\_(discard \|error)\_(in\|out))' Sum traffic by interface: --extend-perfdata-group='traffic\_in\_(.*),traffic\_$1,sum(traf fic\_(in\|out)\_$1)' | @@ -682,9 +682,9 @@ All generic options are listed here: | --sampling-period | Choose the sampling period (can change the default sampling for counters). Should be not different from 300 or 20. | | --time-shift | Can shift the time. With the following option you can average X counters values (default: 0). | | --case-insensitive | Searches are case insensitive. | -| --unknown-connector-status | Set unknown threshold for connector status (Default: '%{code} \< 0 \|\| (%{code} \> 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | -| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short\_message}, %{extra\_message}. | +| --unknown-connector-status | Set unknown threshold for connector status (Default: '%\{code\} \< 0 \|\| (%\{code\} \> 0 && %\{code\} \< 200)'). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --warning-connector-status | Set warning threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | +| --critical-connector-status | Set critical threshold for connector status (Default: ''). You can use the following variables: %\{code\}, %\{short_message\}, %\{extra_message\}. | #### Modes options @@ -702,9 +702,9 @@ All available options for each service template are listed below: | --scope-datacenter | Search in the following datacenter(s) (can be a regexp). | | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | | --critical-* | Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'. | @@ -723,9 +723,9 @@ All available options for each service template are listed below: | --datastore-name | Datastore to check. If not set, we check all datastores. | | --filter-datastore | Define which devices should be monitored based on the datastores names. This option will be treated as a regular expression. | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | @@ -742,9 +742,9 @@ All available options for each service template are listed below: | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | | --device | Device to check (required). (Example: --device='VirtualCdrom'). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\} | | --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | | --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | @@ -759,12 +759,12 @@ All available options for each service template are listed below: | --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --display-description | Display the description of the virtual machine. | | --check-disk-limit | Check disk limits (since vsphere 5.0). | -| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | -| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%{connection\_state} !~ /^connected$/i \|\| %{limit} != -1'). You can use the following variables: %{connection\_state}, %{power\_state}, %{limit} | +| --warning-disk-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-disk-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-cpu-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-cpu-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --warning-memory-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | +| --critical-memory-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{connection_state\} !~ /^connected$/i \|\| %\{limit\} != -1'). You can use the following variables: %\{connection_state\}, %\{power_state\}, %\{limit\} | @@ -779,9 +779,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | | --free | Thresholds are applied on free space left. | | --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | @@ -820,12 +820,12 @@ All available options for each service template are listed below: | --scope-datacenter | Search in the following datacenter(s) (can be a regexp). | | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{connection\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{connection\_state}, %{power\_state} | -| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{overall\_status} =~ /gray/i'). You can use the following variables: %{overall\_status} | -| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%{overall\_status} =~ /yellow/i'). You can use the following variables: %{overall\_status} | -| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%{overall\_status} =~ /red/i'). You can use the following variables: %{overall\_status} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{connection_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --unknown-overall-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{overall_status\} =~ /gray/i'). You can use the following variables: %\{overall_status\} | +| --warning-overall-status | Define the conditions to match for the status to be WARNING (Default: '%\{overall_status\} =~ /yellow/i'). You can use the following variables: %\{overall_status\} | +| --critical-overall-status | Define the conditions to match for the status to be CRITICAL (Default: '%\{overall_status\} =~ /red/i'). You can use the following variables: %\{overall_status\} | @@ -840,9 +840,9 @@ All available options for each service template are listed below: | --scope-cluster | Search in the following cluster(s) (can be a regexp). | | --scope-host | Search in the following host(s) (can be a regexp). | | --display-description | Display the description of the virtual machine. | -| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%{connection\_state} !~ /^connected$/i or %{power\_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection\_state}, %{power\_state} | -| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | -| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection\_state}, %{power\_state} | +| --unknown-status | Define the conditions to match for the status to be UNKNOWN (Default: '%\{connection_state\} !~ /^connected$/i or %\{power_state\} !~ /^poweredOn$/i'). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --warning-status | Define the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | +| --critical-status | Define the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %\{connection_state\}, %\{power_state\} | | --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | | --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | diff --git a/src/pages/index.js b/src/pages/index.js index 641cbf517f75..5dc617a454a7 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -1,5 +1,5 @@ import React from 'react'; -import { Redirect } from 'react-router-dom'; +import { Redirect } from '@docusaurus/router'; import clsx from 'clsx'; import Layout from '@theme/Layout'; import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; diff --git a/src/theme/DocBreadcrumbs/index.js b/src/theme/DocBreadcrumbs/index.js index 9b1f0efd33ab..bf9a204f2a54 100644 --- a/src/theme/DocBreadcrumbs/index.js +++ b/src/theme/DocBreadcrumbs/index.js @@ -1,10 +1,8 @@ import React from 'react'; import clsx from 'clsx'; -import {ThemeClassNames} from '@docusaurus/theme-common'; -import { - useSidebarBreadcrumbs, - useHomePageRoute, -} from '@docusaurus/theme-common/internal'; +import { ThemeClassNames } from '@docusaurus/theme-common'; +import { useSidebarBreadcrumbs } from '@docusaurus/plugin-content-docs/client'; +import { useHomePageRoute } from '@docusaurus/theme-common/internal'; import Link from '@docusaurus/Link'; import useBaseUrl from '@docusaurus/useBaseUrl'; import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; diff --git a/src/theme/DocBreadcrumbs/styles.module.css b/src/theme/DocBreadcrumbs/styles.module.css index f1af9cba8d4f..72da4671a455 100644 --- a/src/theme/DocBreadcrumbs/styles.module.css +++ b/src/theme/DocBreadcrumbs/styles.module.css @@ -1,4 +1,4 @@ .breadcrumbsContainer { - --ifm-breadcrumb-size-multiplier: 0.8; - margin-bottom: 0.8rem; - } \ No newline at end of file + --ifm-breadcrumb-size-multiplier: 0.8; + margin-bottom: 0.8rem; +} diff --git a/src/theme/DocCard/index.tsx b/src/theme/DocCard/index.tsx index 95d0c1f835ef..6f7c699c2b73 100644 --- a/src/theme/DocCard/index.tsx +++ b/src/theme/DocCard/index.tsx @@ -4,9 +4,9 @@ import Link from '@docusaurus/Link'; import styles from './styles.module.css'; import { translate } from '@docusaurus/Translate'; import { - findFirstCategoryLink, + findFirstSidebarItemLink, useDocById, -} from '@docusaurus/theme-common/internal'; +} from '@docusaurus/plugin-content-docs/client'; function CardContainer({ href, @@ -54,7 +54,7 @@ function CardCategory({ }: { item: PropSidebarItemCategory; }): JSX.Element | null { - const href = findFirstCategoryLink(item); + const href = findFirstSidebarItemLink(item); // Unexpected: categories that don't have a link have been filtered upfront if (!href) { diff --git a/src/theme/DocItem/Footer/index.js b/src/theme/DocItem/Footer/index.jsx similarity index 97% rename from src/theme/DocItem/Footer/index.js rename to src/theme/DocItem/Footer/index.jsx index 5e6489673952..c9a82ce7d898 100644 --- a/src/theme/DocItem/Footer/index.js +++ b/src/theme/DocItem/Footer/index.jsx @@ -1,11 +1,11 @@ import React from 'react'; import clsx from 'clsx'; import { ThemeClassNames } from '@docusaurus/theme-common'; -import { useDoc } from '@docusaurus/theme-common/internal'; +import { useDoc } from '@docusaurus/plugin-content-docs/client'; import LastUpdated from '@theme/LastUpdated'; import TagsListInline from '@theme/TagsListInline'; import Translate from '@docusaurus/Translate'; -import { useLocation } from 'react-router-dom'; +import { useLocation } from '@docusaurus/router'; import styles from './styles.module.css'; function TagsRow({ tags }) { @@ -74,7 +74,7 @@ function EditMetaRow({ id="Commentaire_doc" data-name="Commentaire doc" xmlns="http://www.w3.org/2000/svg" - xmlns:xlink="http://www.w3.org/1999/xlink" + xmlnsXlink="http://www.w3.org/1999/xlink" width="24" height="24" viewBox="0 0 24 24" @@ -94,7 +94,7 @@ function EditMetaRow({ - + diff --git a/versioned_docs/version-22.10/administration/logging-configuration-changes.md b/versioned_docs/version-22.10/administration/logging-configuration-changes.md index 39d319b1a01d..b6a042789268 100644 --- a/versioned_docs/version-22.10/administration/logging-configuration-changes.md +++ b/versioned_docs/version-22.10/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table:
                                                    Modification type -

                                                    Contains the type of action effective. There are several types of action possible:

                                                    + +

                                                    Contains the type of action effective. There are several types of action possible:

                                                    • Added: Indicates that the object has been added
                                                    • Changed: Indicates that the object has been changed
                                                      • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                                                      The last column describes the change itself :

                                                      + +

                                                      The last column describes the change itself :

                                                      • Field name: Describes the field that has been changed
                                                      • Before: Indicates the previous value
                                                        • diff --git a/versioned_docs/version-22.10/administration/parameters/ldap.md b/versioned_docs/version-22.10/administration/parameters/ldap.md index 03fec5578969..bd99bf178691 100644 --- a/versioned_docs/version-22.10/administration/parameters/ldap.md +++ b/versioned_docs/version-22.10/administration/parameters/ldap.md @@ -98,8 +98,8 @@ on the MS Active Directory, Okta or of Posix type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for **Search group > base DN** field. With CentOS 7, it's possible to not check server certificate, follow procedure: diff --git a/versioned_docs/version-22.10/administration/secure-platform.md b/versioned_docs/version-22.10/administration/secure-platform.md index 03478227e061..779af5d4c05e 100644 --- a/versioned_docs/version-22.10/administration/secure-platform.md +++ b/versioned_docs/version-22.10/administration/secure-platform.md @@ -682,17 +682,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-22.10/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-22.10/alerts-notifications/notif-config-for-teams.md index 9e307b772095..bcdd62582bea 100644 --- a/versioned_docs/version-22.10/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-22.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-22.10/alerts-notifications/resources-status.md b/versioned_docs/version-22.10/alerts-notifications/resources-status.md index d7bc4177c240..65314ce13184 100644 --- a/versioned_docs/version-22.10/alerts-notifications/resources-status.md +++ b/versioned_docs/version-22.10/alerts-notifications/resources-status.md @@ -295,7 +295,7 @@ Graphs display metric evolution over a given period of time. This can be defined - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Anytime the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (respectively backward and forward in time) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (respectively backward and forward in time) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-22.10/alerts-notifications/ticketing.md b/versioned_docs/version-22.10/alerts-notifications/ticketing.md index e972496a0771..72d03af5dc3b 100644 --- a/versioned_docs/version-22.10/alerts-notifications/ticketing.md +++ b/versioned_docs/version-22.10/alerts-notifications/ticketing.md @@ -138,9 +138,9 @@ The module stores the user list selection in an array (can be used in smarty section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-22.10/api/clapi.md b/versioned_docs/version-22.10/api/clapi.md index 0b48a727cb2e..7ae3fe3ae6d3 100644 --- a/versioned_docs/version-22.10/api/clapi.md +++ b/versioned_docs/version-22.10/api/clapi.md @@ -990,23 +990,35 @@ ipv4: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1014,71 +1026,121 @@ ipv4:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        category

                                                        -

                                                        Filter category

                                                        -

                                                        Category filter for flux in input

                                                        + +

                                                        category

                                                        + + +

                                                        Filter category

                                                        + + +

                                                        Category filter for flux in input

                                                        +
                                                        -

                                                        ca_certificate

                                                        -

                                                        host

                                                        -

                                                        Trusted CA's certificate

                                                        -

                                                        Host to connect to

                                                        -

                                                        Trusted CA's certificate.

                                                        -

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        + +

                                                        ca_certificate

                                                        +

                                                        host

                                                        + + +

                                                        Trusted CA's certificate

                                                        +

                                                        Host to connect to

                                                        + + +

                                                        Trusted CA's certificate.

                                                        +

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        +
                                                        -

                                                        one_peer_retention_mode

                                                        -

                                                        port

                                                        -

                                                        One peer retention

                                                        -

                                                        Connection port

                                                        -

                                                        This allows the retention to work even if the socket is listening

                                                        -

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        + +

                                                        one_peer_retention_mode

                                                        +

                                                        port

                                                        + + +

                                                        One peer retention

                                                        +

                                                        Connection port

                                                        + + +

                                                        This allows the retention to work even if the socket is listening

                                                        +

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        +
                                                        -

                                                        private_key

                                                        -

                                                        Private key file.

                                                        -

                                                        Private key file path when TLS encryption is used.

                                                        + +

                                                        private_key

                                                        + + +

                                                        Private key file.

                                                        + + +

                                                        Private key file path when TLS encryption is used.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + -

                                                        public_cert

                                                        -

                                                        Public certificate

                                                        -

                                                        Public certificate file path when TLS encryption is used.

                                                        + +

                                                        public_cert

                                                        + + +

                                                        Public certificate

                                                        + + +

                                                        Public certificate file path when TLS encryption is used.

                                                        +
                                                        -

                                                        tls

                                                        -

                                                        Enable TLS encryption

                                                        -

                                                        Enable TLS encryption.

                                                        + +

                                                        tls

                                                        + + +

                                                        Enable TLS encryption

                                                        + + +

                                                        Enable TLS encryption.

                                                        +
                                                        @@ -1099,23 +1161,35 @@ ipv6: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1123,71 +1197,121 @@ ipv6:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        category

                                                        -

                                                        Filter category

                                                        -

                                                        Category filter for flux in input

                                                        + +

                                                        category

                                                        + + +

                                                        Filter category

                                                        + + +

                                                        Category filter for flux in input

                                                        +
                                                        -

                                                        ca_certificate

                                                        -

                                                        host

                                                        -

                                                        Trusted CA's certificate

                                                        -

                                                        Host to connect to

                                                        -

                                                        Trusted CA's certificate.

                                                        -

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        + +

                                                        ca_certificate

                                                        +

                                                        host

                                                        + + +

                                                        Trusted CA's certificate

                                                        +

                                                        Host to connect to

                                                        + + +

                                                        Trusted CA's certificate.

                                                        +

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        +
                                                        -

                                                        one_peer_retention_mode

                                                        -

                                                        port

                                                        -

                                                        One peer retention

                                                        -

                                                        Connection port

                                                        -

                                                        This allows the retention to work even if the socket is listening

                                                        -

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        + +

                                                        one_peer_retention_mode

                                                        +

                                                        port

                                                        + + +

                                                        One peer retention

                                                        +

                                                        Connection port

                                                        + + +

                                                        This allows the retention to work even if the socket is listening

                                                        +

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        +
                                                        -

                                                        private_key

                                                        -

                                                        Private key file.

                                                        -

                                                        Private key file path when TLS encryption is used.

                                                        + +

                                                        private_key

                                                        + + +

                                                        Private key file.

                                                        + + +

                                                        Private key file path when TLS encryption is used.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + -

                                                        public_cert

                                                        -

                                                        Public certificate

                                                        -

                                                        Public certificate file path when TLS encryption is used.

                                                        + +

                                                        public_cert

                                                        + + +

                                                        Public certificate

                                                        + + +

                                                        Public certificate file path when TLS encryption is used.

                                                        +
                                                        -

                                                        tls

                                                        -

                                                        Enable TLS encryption

                                                        -

                                                        Enable TLS encryption.

                                                        + +

                                                        tls

                                                        + + +

                                                        Enable TLS encryption

                                                        + + +

                                                        Enable TLS encryption.

                                                        +
                                                        @@ -1208,23 +1332,35 @@ file: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1232,34 +1368,60 @@ file:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        max_size

                                                        -

                                                        Maximum size of file

                                                        -

                                                        Maximum size in bytes.

                                                        + +

                                                        max_size

                                                        + + +

                                                        Maximum size of file

                                                        + + +

                                                        Maximum size in bytes.

                                                        +
                                                        -

                                                        path

                                                        -

                                                        File path

                                                        -

                                                        Path to the file.

                                                        + +

                                                        path

                                                        + + +

                                                        File path

                                                        + + +

                                                        Path to the file.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + @@ -1279,50 +1441,88 @@ file: -

                                                        config

                                                        -

                                                        Configuration messages

                                                        -

                                                        Enable or not configuration messages logging.

                                                        + +

                                                        config

                                                        + + +

                                                        Configuration messages

                                                        + + +

                                                        Enable or not configuration messages logging.

                                                        +
                                                        -

                                                        debug

                                                        -

                                                        Debug messages

                                                        -

                                                        Enable or not debug messages logging.

                                                        + +

                                                        debug

                                                        + + +

                                                        Debug messages

                                                        + + +

                                                        Enable or not debug messages logging.

                                                        +
                                                        -

                                                        error

                                                        -

                                                        Error messages

                                                        -

                                                        Enable or not error messages logging.

                                                        + +

                                                        error

                                                        + + +

                                                        Error messages

                                                        + + +

                                                        Enable or not error messages logging.

                                                        +
                                                        -

                                                        info

                                                        -

                                                        Informational messages

                                                        -

                                                        Enable or not informational messages logging.

                                                        + +

                                                        info

                                                        + + +

                                                        Informational messages

                                                        + + +

                                                        Enable or not informational messages logging.

                                                        +
                                                        -

                                                        level

                                                        -

                                                        Logging level

                                                        -

                                                        How much messages must be logged.

                                                        -

                                                        high,low,medium

                                                        + +

                                                        level

                                                        + + +

                                                        Logging level

                                                        + + +

                                                        How much messages must be logged.

                                                        + + +

                                                        high,low,medium

                                                        + -

                                                        max_size

                                                        -

                                                        name

                                                        -

                                                        Max file size in bytes

                                                        -

                                                        Name of the logger

                                                        -

                                                        The maximum size of log file.

                                                        -

                                                        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                        + +

                                                        max_size

                                                        +

                                                        name

                                                        + + +

                                                        Max file size in bytes

                                                        +

                                                        Name of the logger

                                                        + + +

                                                        The maximum size of log file.

                                                        +

                                                        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                        +
                                                        • @@ -1344,45 +1544,76 @@ standard: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          name

                                                          -

                                                          Logging level

                                                          -

                                                          Name of the logger

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          +

                                                          name

                                                          + + +

                                                          Logging level

                                                          +

                                                          Name of the logger

                                                          + + +

                                                          How much messages must be logged.

                                                          +

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          + + +

                                                          high,low,medium

                                                          @@ -1403,42 +1634,74 @@ syslog: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          Logging level

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          + + +

                                                          Logging level

                                                          + + +

                                                          How much messages must be logged.

                                                          + + +

                                                          high,low,medium

                                                          + @@ -1456,45 +1719,76 @@ monitoring: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          name

                                                          -

                                                          Logging level

                                                          -

                                                          Name of the logger

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          +

                                                          name

                                                          + + +

                                                          Logging level

                                                          +

                                                          Name of the logger

                                                          + + +

                                                          How much messages must be logged.

                                                          +

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          + + +

                                                          high,low,medium

                                                          @@ -1570,33 +1864,57 @@ rrd: -

                                                          buffering_timeout

                                                          -

                                                          Buffering timeout

                                                          -

                                                          Time in seconds to wait before launching failover.

                                                          + +

                                                          buffering_timeout

                                                          + + +

                                                          Buffering timeout

                                                          + + +

                                                          Time in seconds to wait before launching failover.

                                                          +
                                                          -

                                                          failover

                                                          -

                                                          Failover name

                                                          -

                                                          Name of the output which will act as failover

                                                          + +

                                                          failover

                                                          + + +

                                                          Failover name

                                                          + + +

                                                          Name of the output which will act as failover

                                                          +
                                                          -

                                                          retry_interval

                                                          -

                                                          Retry interval

                                                          -

                                                          Time in seconds to wait between each connection attempt.

                                                          + +

                                                          retry_interval

                                                          + + +

                                                          Retry interval

                                                          + + +

                                                          Time in seconds to wait between each connection attempt.

                                                          +
                                                          -

                                                          category

                                                          -

                                                          Filter category

                                                          -

                                                          Category filter for flux in output.

                                                          + +

                                                          category

                                                          + + +

                                                          Filter category

                                                          + + +

                                                          Category filter for flux in output.

                                                          +
                                                          • @@ -1604,15 +1922,21 @@ rrd:
                                                          -

                                                          metrics_path

                                                          + +

                                                          metrics_path

                                                          path

                                                          -

                                                          port

                                                          -

                                                          RRD file directory for metrics

                                                          +

                                                          port

                                                          + + +

                                                          RRD file directory for metrics

                                                          Unix socket

                                                          -

                                                          TCP port

                                                          -

                                                          RRD file directory, for example /var/lib/centreon/metrics

                                                          +

                                                          TCP port

                                                          + + +

                                                          RRD file directory, for example /var/lib/centreon/metrics

                                                          The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          -

                                                          The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          +

                                                          The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          +
                                                          • @@ -1620,33 +1944,57 @@ rrd:
                                                          -

                                                          status_path

                                                          -

                                                          RRD file directory for statuses

                                                          -

                                                          RRD file directory, for example /var/lib/centreon/status

                                                          + +

                                                          status_path

                                                          + + +

                                                          RRD file directory for statuses

                                                          + + +

                                                          RRD file directory, for example /var/lib/centreon/status

                                                          +
                                                          -

                                                          write_metrics

                                                          -

                                                          Enable write_metrics

                                                          -

                                                          Enable or not write_metrics.

                                                          + +

                                                          write_metrics

                                                          + + +

                                                          Enable write_metrics

                                                          + + +

                                                          Enable or not write_metrics.

                                                          +
                                                          -

                                                          write_status

                                                          -

                                                          Enable write_status

                                                          -

                                                          Enable or not write_status.

                                                          + +

                                                          write_status

                                                          + + +

                                                          Enable write_status

                                                          + + +

                                                          Enable or not write_status.

                                                          +
                                                          -

                                                          store_in_data_bin

                                                          -

                                                          Enable store_in_data_bin

                                                          -

                                                          Enable or not store in performance data in data_bin.

                                                          + +

                                                          store_in_data_bin

                                                          + + +

                                                          Enable store_in_data_bin

                                                          + + +

                                                          Enable or not store in performance data in data_bin.

                                                          +
                                                          • @@ -1669,36 +2017,60 @@ storage: -

                                                            buffering_timeout

                                                            -

                                                            Buffering timeout

                                                            -

                                                            Time in seconds to wait before launching failover.

                                                            + +

                                                            buffering_timeout

                                                            + + +

                                                            Buffering timeout

                                                            + + +

                                                            Time in seconds to wait before launching failover.

                                                            +
                                                            -

                                                            failover

                                                            -

                                                            Failover name

                                                            -

                                                            Name of the output which will act as failover

                                                            + +

                                                            failover

                                                            + + +

                                                            Failover name

                                                            + + +

                                                            Name of the output which will act as failover

                                                            +
                                                            -

                                                            retry_interval

                                                            -

                                                            Retry interval

                                                            -

                                                            Time in seconds to wait between each connection attempt.

                                                            + +

                                                            retry_interval

                                                            + + +

                                                            Retry interval

                                                            + + +

                                                            Time in seconds to wait between each connection attempt.

                                                            +
                                                            -

                                                            category

                                                            -

                                                            check_replication

                                                            -

                                                            Filter category

                                                            -

                                                            Replication enabled

                                                            -

                                                            Category filter for flux in output.

                                                            -

                                                            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                            + +

                                                            category

                                                            +

                                                            check_replication

                                                            + + +

                                                            Filter category

                                                            +

                                                            Replication enabled

                                                            + + +

                                                            Category filter for flux in output.

                                                            +

                                                            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                            +
                                                            • @@ -1709,91 +2081,159 @@ storage:
                                                            -

                                                            db_host

                                                            -

                                                            DB host

                                                            -

                                                            IP address or hostname of the database server.

                                                            + +

                                                            db_host

                                                            + + +

                                                            DB host

                                                            + + +

                                                            IP address or hostname of the database server.

                                                            +
                                                            -

                                                            db_name

                                                            -

                                                            DB name

                                                            -

                                                            Database name.

                                                            + +

                                                            db_name

                                                            + + +

                                                            DB name

                                                            + + +

                                                            Database name.

                                                            +
                                                            -

                                                            db_password

                                                            -

                                                            DB password

                                                            -

                                                            Password of database user.

                                                            + +

                                                            db_password

                                                            + + +

                                                            DB password

                                                            + + +

                                                            Password of database user.

                                                            +
                                                            -

                                                            db_port

                                                            -

                                                            DB port

                                                            -

                                                            Port on which the DB server listens

                                                            + +

                                                            db_port

                                                            + + +

                                                            DB port

                                                            + + +

                                                            Port on which the DB server listens

                                                            +
                                                            -

                                                            db_type

                                                            -

                                                            DB type

                                                            -

                                                            Target DBMS.

                                                            -

                                                            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                            + +

                                                            db_type

                                                            + + +

                                                            DB type

                                                            + + +

                                                            Target DBMS.

                                                            + + +

                                                            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                            + -

                                                            db_user

                                                            -

                                                            DB user

                                                            -

                                                            Database user.

                                                            + +

                                                            db_user

                                                            + + +

                                                            DB user

                                                            + + +

                                                            Database user.

                                                            +
                                                            -

                                                            interval

                                                            -

                                                            Interval length

                                                            -

                                                            Interval length in seconds.

                                                            + +

                                                            interval

                                                            + + +

                                                            Interval length

                                                            + + +

                                                            Interval length in seconds.

                                                            +
                                                            -

                                                            length

                                                            -

                                                            RRD length

                                                            -

                                                            RRD storage duration in seconds.

                                                            + +

                                                            length

                                                            + + +

                                                            RRD length

                                                            + + +

                                                            RRD storage duration in seconds.

                                                            +
                                                            -

                                                            queries_per_transaction

                                                            -

                                                            Maximum queries per transaction

                                                            -

                                                            The maximum queries per transaction before commit.

                                                            + +

                                                            queries_per_transaction

                                                            + + +

                                                            Maximum queries per transaction

                                                            + + +

                                                            The maximum queries per transaction before commit.

                                                            +
                                                            -

                                                            read_timeout

                                                            -

                                                            rebuild_check_interval

                                                            -

                                                            Transaction commit timeout

                                                            -

                                                            Rebuild check interval in seconds

                                                            -

                                                            The transaction timeout before running commit.

                                                            -

                                                            The interval between check if some metrics must be rebuild. The default value is 300s

                                                            + +

                                                            read_timeout

                                                            +

                                                            rebuild_check_interval

                                                            + + +

                                                            Transaction commit timeout

                                                            +

                                                            Rebuild check interval in seconds

                                                            + + +

                                                            The transaction timeout before running commit.

                                                            +

                                                            The interval between check if some metrics must be rebuild. The default value is 300s

                                                            +
                                                            -

                                                            store_in_data_bin

                                                            -

                                                            Enable store_in_data_bin

                                                            -

                                                            Enable or not store in performance data in data_bin.

                                                            + +

                                                            store_in_data_bin

                                                            + + +

                                                            Enable store_in_data_bin

                                                            + + +

                                                            Enable or not store in performance data in data_bin.

                                                            +
                                                            • @@ -1816,36 +2256,60 @@ sql: -

                                                              buffering_timeout

                                                              -

                                                              Buffering timeout

                                                              -

                                                              Time in seconds to wait before launching failover.

                                                              + +

                                                              buffering_timeout

                                                              + + +

                                                              Buffering timeout

                                                              + + +

                                                              Time in seconds to wait before launching failover.

                                                              +
                                                              -

                                                              failover

                                                              -

                                                              Failover name

                                                              -

                                                              Name of the output which will act as failover

                                                              + +

                                                              failover

                                                              + + +

                                                              Failover name

                                                              + + +

                                                              Name of the output which will act as failover

                                                              +
                                                              -

                                                              retry_interval

                                                              -

                                                              Retry interval

                                                              -

                                                              Time in seconds to wait between each connection attempt.

                                                              + +

                                                              retry_interval

                                                              + + +

                                                              Retry interval

                                                              + + +

                                                              Time in seconds to wait between each connection attempt.

                                                              +
                                                              -

                                                              category

                                                              -

                                                              check_replication

                                                              -

                                                              Filter category

                                                              -

                                                              Replication enabled

                                                              -

                                                              Category filter for flux in output.

                                                              -

                                                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                              + +

                                                              category

                                                              +

                                                              check_replication

                                                              + + +

                                                              Filter category

                                                              +

                                                              Replication enabled

                                                              + + +

                                                              Category filter for flux in output.

                                                              +

                                                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                              +
                                                              • @@ -1856,63 +2320,113 @@ sql:
                                                              -

                                                              db_host

                                                              -

                                                              DB host

                                                              -

                                                              IP address or hostname of the database server.

                                                              + +

                                                              db_host

                                                              + + +

                                                              DB host

                                                              + + +

                                                              IP address or hostname of the database server.

                                                              +
                                                              -

                                                              db_name

                                                              -

                                                              DB name

                                                              -

                                                              Database name.

                                                              + +

                                                              db_name

                                                              + + +

                                                              DB name

                                                              + + +

                                                              Database name.

                                                              +
                                                              -

                                                              db_password

                                                              -

                                                              DB password

                                                              -

                                                              Password of database user.

                                                              + +

                                                              db_password

                                                              + + +

                                                              DB password

                                                              + + +

                                                              Password of database user.

                                                              +
                                                              -

                                                              db_port

                                                              -

                                                              DB port

                                                              -

                                                              Port on which the DB server listens

                                                              + +

                                                              db_port

                                                              + + +

                                                              DB port

                                                              + + +

                                                              Port on which the DB server listens

                                                              +
                                                              -

                                                              db_type

                                                              -

                                                              DB type

                                                              -

                                                              Target DBMS.

                                                              -

                                                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                              + +

                                                              db_type

                                                              + + +

                                                              DB type

                                                              + + +

                                                              Target DBMS.

                                                              + + +

                                                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                              + -

                                                              db_user

                                                              -

                                                              DB user

                                                              -

                                                              Database user.

                                                              + +

                                                              db_user

                                                              + + +

                                                              DB user

                                                              + + +

                                                              Database user.

                                                              +
                                                              -

                                                              queries_per_transaction

                                                              -

                                                              Maximum queries per transaction

                                                              -

                                                              The maximum queries per transaction before commit.

                                                              + +

                                                              queries_per_transaction

                                                              + + +

                                                              Maximum queries per transaction

                                                              + + +

                                                              The maximum queries per transaction before commit.

                                                              +
                                                              -

                                                              read_timeout

                                                              -

                                                              Transaction commit timeout

                                                              -

                                                              The transaction timeout before running commit.

                                                              + +

                                                              read_timeout

                                                              + + +

                                                              Transaction commit timeout

                                                              + + +

                                                              The transaction timeout before running commit.

                                                              +
                                                              diff --git a/versioned_docs/version-22.10/api/graph-views-api.md b/versioned_docs/version-22.10/api/graph-views-api.md index 35bd67bcddce..df5a176b49a5 100644 --- a/versioned_docs/version-22.10/api/graph-views-api.md +++ b/versioned_docs/version-22.10/api/graph-views-api.md @@ -48,14 +48,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -69,7 +69,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -77,7 +77,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/versioned_docs/version-22.10/api/graph-views-map-api.md b/versioned_docs/version-22.10/api/graph-views-map-api.md index 362a6ee9e98e..69695aa69aa0 100644 --- a/versioned_docs/version-22.10/api/graph-views-map-api.md +++ b/versioned_docs/version-22.10/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 22.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 22.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-22.10/api/rest-api-v1.md b/versioned_docs/version-22.10/api/rest-api-v1.md index 193e248e42bd..891a7a8306ff 100644 --- a/versioned_docs/version-22.10/api/rest-api-v1.md +++ b/versioned_docs/version-22.10/api/rest-api-v1.md @@ -2483,8 +2483,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-22.10/connect/openid.md b/versioned_docs/version-22.10/connect/openid.md index c4f1388af411..68995e24982e 100644 --- a/versioned_docs/version-22.10/connect/openid.md +++ b/versioned_docs/version-22.10/connect/openid.md @@ -205,8 +205,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -217,7 +217,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -225,8 +225,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -237,7 +237,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -245,8 +245,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -265,8 +265,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-22.10/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-22.10/developer/developer-gorgone-client-server-communication.md index 5caa80bbb37d..7f52ac58ec57 100644 --- a/versioned_docs/version-22.10/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-22.10/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-22.10/developer/developer-translate-centreon.md b/versioned_docs/version-22.10/developer/developer-translate-centreon.md index 5efd4652d0cf..14f0f2e606b4 100644 --- a/versioned_docs/version-22.10/developer/developer-translate-centreon.md +++ b/versioned_docs/version-22.10/developer/developer-translate-centreon.md @@ -136,7 +136,7 @@ will allow for all person using Centreon to have access to your translation on t * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-22.10/developer/developer-widget.md b/versioned_docs/version-22.10/developer/developer-widget.md index cda4533aad87..b36d0051e1c6 100644 --- a/versioned_docs/version-22.10/developer/developer-widget.md +++ b/versioned_docs/version-22.10/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They have to be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-22.10/graph-views/install.md b/versioned_docs/version-22.10/graph-views/install.md index c2cdecb6e3b4..7bcc0cff6824 100644 --- a/versioned_docs/version-22.10/graph-views/install.md +++ b/versioned_docs/version-22.10/graph-views/install.md @@ -152,7 +152,7 @@ default value. Modify the following file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-22.10/graph-views/troubleshooter.md b/versioned_docs/version-22.10/graph-views/troubleshooter.md index a60c3e8afb10..bd6410f48107 100644 --- a/versioned_docs/version-22.10/graph-views/troubleshooter.md +++ b/versioned_docs/version-22.10/graph-views/troubleshooter.md @@ -157,7 +157,7 @@ To open the appropriate ports: /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Replace by the port your Centreon MAP server is using (mostly 8080 or +> Replace \ by the port your Centreon MAP server is using (mostly 8080 or > 8443 if you have configured it in SSL). To simply disable your firewall, execute: @@ -285,7 +285,7 @@ specify a new one to your desktop client. To do so, edit the file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -371,7 +371,7 @@ is working hard, your desktop client requires more memory. ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-22.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-22.10/installation/installation-of-a-central-server/using-packages.md index 622ed5f6a9f7..f3864d9d393e 100644 --- a/versioned_docs/version-22.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-22.10/installation/installation-of-a-central-server/using-packages.md @@ -477,9 +477,9 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTION FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** by the user's credentials. +> Replace **\** and **\** by the user's credentials. This user will only be used for the installation process: once the [web installation](../web-and-post-installation.md) is complete you can delete this user using: diff --git a/versioned_docs/version-22.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-22.10/installation/installation-of-a-poller/using-packages.md index 963b720e1219..44e9d647c6ed 100644 --- a/versioned_docs/version-22.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-22.10/installation/installation-of-a-poller/using-packages.md @@ -336,9 +336,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** by the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** by the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -389,19 +389,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md index 8e975f45c9f4..ee06c89fe983 100644 --- a/versioned_docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-22.10/installation/installation-of-a-remote-server/using-packages.md @@ -468,9 +468,9 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** by user's credentials. +> Replace **\** and **\** by user's credentials. This user will only be used for the installation process. Once the [web installation](../web-and-post-installation.md) is complete you can delete this user using: @@ -677,12 +677,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** by the IP of the central server, as seen by the remote server. +> Replace **\** by the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -759,19 +759,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-22.10/installation/prerequisites.md b/versioned_docs/version-22.10/installation/prerequisites.md index d19dd46dfd42..80f18b660e4e 100644 --- a/versioned_docs/version-22.10/installation/prerequisites.md +++ b/versioned_docs/version-22.10/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | **Database server** diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-clickhouse.md index f751a6badd42..f873d336f5bf 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-events.md index ca3cc67e0662..e46a71374753 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-events.md @@ -227,7 +227,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md index 46e968aa21b7..4810136eb778 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-datadog-metrics.md @@ -230,7 +230,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-logstash-events.md index f13346c08b4c..699f9062e000 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-logstash-events.md @@ -228,7 +228,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *8080*. diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-events.md index 2d0f5f4db5fe..1af1e4ab60fd 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md index 6b1209efb93a..a29dcb6fb7c5 100644 --- a/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-22.10/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-22.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-22.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md index 8006065df114..c7420a99257a 100644 --- a/versioned_docs/version-22.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-22.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-22.10/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-22.10/integrations/event-management/sc-opsgenie.md index 70ed74982f06..b8b15290a409 100644 --- a/versioned_docs/version-22.10/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-22.10/integrations/event-management/sc-opsgenie.md @@ -131,10 +131,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -178,7 +178,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg:\{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg:\{last_update\} is a timestamp macro. You can use\{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-22.10/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-22.10/integrations/event-management/sc-pagerduty-events.md index 4c7e0fd22399..2f413c810359 100644 --- a/versioned_docs/version-22.10/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-22.10/integrations/event-management/sc-pagerduty-events.md @@ -290,7 +290,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-22.10/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-22.10/integrations/itsm/ot-bmc-remedy.md index 95aaaf7944fd..dcc196ae6331 100644 --- a/versioned_docs/version-22.10/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-22.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-22.10/integrations/itsm/ot-mail.md b/versioned_docs/version-22.10/integrations/itsm/ot-mail.md index 193de09442c3..0064d99727a9 100644 --- a/versioned_docs/version-22.10/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-22.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.emai\l} | | To | | ## Possibilities diff --git a/versioned_docs/version-22.10/integrations/itsm/ot-serena.md b/versioned_docs/version-22.10/integrations/itsm/ot-serena.md index 0b3dff0fdc64..e918149875a8 100644 --- a/versioned_docs/version-22.10/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-22.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-22.10/integrations/notifications/plugin-telegram.md b/versioned_docs/version-22.10/integrations/notifications/plugin-telegram.md index 80d6f9aad7ca..7c04e923bcab 100644 --- a/versioned_docs/version-22.10/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-22.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-22.10/integrations/stream-connectors.md b/versioned_docs/version-22.10/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-22.10/integrations/stream-connectors.md +++ b/versioned_docs/version-22.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-22.10/migrate/migrate-from-3-4.md b/versioned_docs/version-22.10/migrate/migrate-from-3-4.md index 06fc24a855c6..fae5d0ac12a7 100644 --- a/versioned_docs/version-22.10/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-22.10/migrate/migrate-from-3-4.md @@ -2,6 +2,8 @@ id: migrate-from-3-4 title: Migrate from a Centreon 3.4 platform --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Prerequisites @@ -59,7 +61,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** by the IP or the new Centreon server. +> Replace **\** by the IP or the new Centreon server. ### Retrieve databases @@ -129,7 +131,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP or the new Centreon server. +> Replace **\** by the IP or the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-22.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-22.10/migrate/migrate-from-el-to-debian.md index 98fc3e2e9c90..761528aab9f4 100644 --- a/versioned_docs/version-22.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-22.10/migrate/migrate-from-el-to-debian.md @@ -61,7 +61,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -145,7 +145,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-22.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-22.10/migrate/migrate-from-el-to-el.md index 83c36e7bb8d2..a1926ece73ca 100644 --- a/versioned_docs/version-22.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-22.10/migrate/migrate-from-el-to-el.md @@ -61,7 +61,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -132,7 +132,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-22.10/migrate/nagios-to-centreon.md b/versioned_docs/version-22.10/migrate/nagios-to-centreon.md index a4566310fe74..9d2c43b75799 100644 --- a/versioned_docs/version-22.10/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-22.10/migrate/nagios-to-centreon.md @@ -98,4 +98,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** by password of **admin** Centreon web user. +Replace **\** by password of **admin** Centreon web user. diff --git a/versioned_docs/version-22.10/migrate/poller-display-to-remote-server.md b/versioned_docs/version-22.10/migrate/poller-display-to-remote-server.md index d28975878f9c..d6e8977b9e65 100644 --- a/versioned_docs/version-22.10/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-22.10/migrate/poller-display-to-remote-server.md @@ -51,7 +51,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -60,12 +60,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** by the IP of the Centreon server seen by the Remote Server. +> Replace **\** by the IP of the Centreon server seen by the Remote Server. -> The **** must have access to configuration API. You can use default **admin** account. +> The **\** must have access to configuration API. You can use default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -142,19 +142,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 14e3df5905f7..430b077a3dff 100644 --- a/versioned_docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-22.10/monitoring/monitoring-servers/communications.md b/versioned_docs/version-22.10/monitoring/monitoring-servers/communications.md index 4999380c21dd..c206ccb6831c 100644 --- a/versioned_docs/version-22.10/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-22.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow to retrieve Remote's thumbprint therefore it's > not possible to display Poller's Gorgone configuration from Centreon UI. diff --git a/versioned_docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index b94cb72f9d16..9b93a0d21f7b 100644 --- a/versioned_docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go into the **Configuration > SNMP traps > SNMP traps** menu and click on **Add* > It is possible to construct the output message yourself. For this, use the MIB to know the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by a OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-22.10/releases/centreon-commercial-extensions.md b/versioned_docs/version-22.10/releases/centreon-commercial-extensions.md index 0c94f4d4a9d1..dd7a4bbd3be4 100644 --- a/versioned_docs/version-22.10/releases/centreon-commercial-extensions.md +++ b/versioned_docs/version-22.10/releases/centreon-commercial-extensions.md @@ -653,7 +653,7 @@ Release date: `July 4, 2024` #### Bug fixes - [Packaging] Added missing dependencies on anomaly detection. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**. ### 22.10.5 diff --git a/versioned_docs/version-22.10/reporting/report-development.md b/versioned_docs/version-22.10/reporting/report-development.md index f79a8faaeac1..72e45d3ce683 100644 --- a/versioned_docs/version-22.10/reporting/report-development.md +++ b/versioned_docs/version-22.10/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-22.10/reporting/reports-publication-rule.md b/versioned_docs/version-22.10/reporting/reports-publication-rule.md index 9416a817ff9b..f1ad61ba74a4 100644 --- a/versioned_docs/version-22.10/reporting/reports-publication-rule.md +++ b/versioned_docs/version-22.10/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Reports publication rules {#publication_rules} +Reports publication rules \{#publication_rules\} ========================= The menu \"Reporting \> Business Intelligence \> Publication rules\" @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_docs/version-22.10/upgrade/upgrade-from-18-10.md b/versioned_docs/version-22.10/upgrade/upgrade-from-18-10.md index b22b3141c6f7..e815115ca15c 100644 --- a/versioned_docs/version-22.10/upgrade/upgrade-from-18-10.md +++ b/versioned_docs/version-22.10/upgrade/upgrade-from-18-10.md @@ -2,6 +2,8 @@ id: upgrade-from-18-10 title: Upgrade from Centreon 18.10 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 18.10 to version 22.10. diff --git a/versioned_docs/version-22.10/upgrade/upgrade-from-19-04.md b/versioned_docs/version-22.10/upgrade/upgrade-from-19-04.md index bde9f7a3d030..1d96b222fc54 100644 --- a/versioned_docs/version-22.10/upgrade/upgrade-from-19-04.md +++ b/versioned_docs/version-22.10/upgrade/upgrade-from-19-04.md @@ -2,6 +2,8 @@ id: upgrade-from-19-04 title: Upgrade from Centreon 19.04 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 19.04 to version 22.10. diff --git a/versioned_docs/version-22.10/upgrade/upgrade-from-19-10.md b/versioned_docs/version-22.10/upgrade/upgrade-from-19-10.md index e698ae86161b..945c2824f975 100644 --- a/versioned_docs/version-22.10/upgrade/upgrade-from-19-10.md +++ b/versioned_docs/version-22.10/upgrade/upgrade-from-19-10.md @@ -2,6 +2,8 @@ id: upgrade-from-19-10 title: Upgrade from Centreon 19.10 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 19.10 to version 22.10. diff --git a/versioned_docs/version-22.10/upgrade/upgrade-from-20-04.md b/versioned_docs/version-22.10/upgrade/upgrade-from-20-04.md index fe8c5c2d299f..af2b484f22b3 100644 --- a/versioned_docs/version-22.10/upgrade/upgrade-from-20-04.md +++ b/versioned_docs/version-22.10/upgrade/upgrade-from-20-04.md @@ -2,6 +2,8 @@ id: upgrade-from-20-04 title: Upgrade from Centreon 20.04 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 20.04 to version 22.10. diff --git a/versioned_docs/version-22.10/upgrade/upgrade-from-3-4.md b/versioned_docs/version-22.10/upgrade/upgrade-from-3-4.md index 45fff4cffbec..66cf39add83d 100644 --- a/versioned_docs/version-22.10/upgrade/upgrade-from-3-4.md +++ b/versioned_docs/version-22.10/upgrade/upgrade-from-3-4.md @@ -2,6 +2,8 @@ id: upgrade-from-3-4 title: Upgrade from Centreon 3.4 --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 3.4 (Centreon Web 2.8) to version 22.10. diff --git a/versioned_docs/version-23.04/administration/logging-configuration-changes.md b/versioned_docs/version-23.04/administration/logging-configuration-changes.md index 39d319b1a01d..b6a042789268 100644 --- a/versioned_docs/version-23.04/administration/logging-configuration-changes.md +++ b/versioned_docs/version-23.04/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table: Modification type -

                                                              Contains the type of action effective. There are several types of action possible:

                                                              + +

                                                              Contains the type of action effective. There are several types of action possible:

                                                              • Added: Indicates that the object has been added
                                                              • Changed: Indicates that the object has been changed
                                                                • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                                                                The last column describes the change itself :

                                                                + +

                                                                The last column describes the change itself :

                                                                • Field name: Describes the field that has been changed
                                                                • Before: Indicates the previous value
                                                                  • diff --git a/versioned_docs/version-23.04/administration/parameters/ldap.md b/versioned_docs/version-23.04/administration/parameters/ldap.md index 47f04e8e63ba..9ed9be75c6f9 100644 --- a/versioned_docs/version-23.04/administration/parameters/ldap.md +++ b/versioned_docs/version-23.04/administration/parameters/ldap.md @@ -98,6 +98,6 @@ on the MS Active Directory, Okta or of Posix type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for **Search group > base DN** field. \ No newline at end of file diff --git a/versioned_docs/version-23.04/administration/secure-platform.md b/versioned_docs/version-23.04/administration/secure-platform.md index b83283d3262f..05269e07b2ca 100644 --- a/versioned_docs/version-23.04/administration/secure-platform.md +++ b/versioned_docs/version-23.04/administration/secure-platform.md @@ -771,17 +771,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-23.04/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-23.04/alerts-notifications/notif-config-for-teams.md index 9ed4c4bd81cb..54f4445a9fe8 100644 --- a/versioned_docs/version-23.04/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-23.04/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-23.04/alerts-notifications/resources-status.md b/versioned_docs/version-23.04/alerts-notifications/resources-status.md index 7414f13eaa84..e105b4253ffb 100644 --- a/versioned_docs/version-23.04/alerts-notifications/resources-status.md +++ b/versioned_docs/version-23.04/alerts-notifications/resources-status.md @@ -284,7 +284,7 @@ Graphs display metric evolution over a given period of time. This can be defined - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Anytime the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (respectively backward and forward in time) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (respectively backward and forward in time) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-23.04/alerts-notifications/ticketing.md b/versioned_docs/version-23.04/alerts-notifications/ticketing.md index e972496a0771..72d03af5dc3b 100644 --- a/versioned_docs/version-23.04/alerts-notifications/ticketing.md +++ b/versioned_docs/version-23.04/alerts-notifications/ticketing.md @@ -138,9 +138,9 @@ The module stores the user list selection in an array (can be used in smarty section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-23.04/api/clapi.md b/versioned_docs/version-23.04/api/clapi.md index 41bb61fb9535..20929cf4bdc0 100644 --- a/versioned_docs/version-23.04/api/clapi.md +++ b/versioned_docs/version-23.04/api/clapi.md @@ -995,23 +995,35 @@ ipv4: -

                                                                  buffering_timeout

                                                                  -

                                                                  Buffering timeout

                                                                  -

                                                                  Time in seconds to wait before launching failover.

                                                                  + +

                                                                  buffering_timeout

                                                                  + + +

                                                                  Buffering timeout

                                                                  + + +

                                                                  Time in seconds to wait before launching failover.

                                                                  +
                                                                  -

                                                                  compression

                                                                  + +

                                                                  compression

                                                                  compression_buffer

                                                                  -

                                                                  compression_level

                                                                  -

                                                                  Compression (zlib)

                                                                  +

                                                                  compression_level

                                                                  + + +

                                                                  Compression (zlib)

                                                                  Compression buffer size

                                                                  -

                                                                  Compression level

                                                                  -

                                                                  Enable or not data stream compression.

                                                                  +

                                                                  Compression level

                                                                  + + +

                                                                  Enable or not data stream compression.

                                                                  The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                                  -

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +
                                                                  • @@ -1019,71 +1031,121 @@ ipv4:
                                                                  -

                                                                  retry_interval

                                                                  -

                                                                  Retry interval

                                                                  -

                                                                  Time in seconds to wait between each connection attempt.

                                                                  + +

                                                                  retry_interval

                                                                  + + +

                                                                  Retry interval

                                                                  + + +

                                                                  Time in seconds to wait between each connection attempt.

                                                                  +
                                                                  -

                                                                  category

                                                                  -

                                                                  Filter category

                                                                  -

                                                                  Category filter for flux in input

                                                                  + +

                                                                  category

                                                                  + + +

                                                                  Filter category

                                                                  + + +

                                                                  Category filter for flux in input

                                                                  +
                                                                  -

                                                                  ca_certificate

                                                                  -

                                                                  host

                                                                  -

                                                                  Trusted CA's certificate

                                                                  -

                                                                  Host to connect to

                                                                  -

                                                                  Trusted CA's certificate.

                                                                  -

                                                                  IP address or hostname of the host to connect to (leave blank for listening mode).

                                                                  + +

                                                                  ca_certificate

                                                                  +

                                                                  host

                                                                  + + +

                                                                  Trusted CA's certificate

                                                                  +

                                                                  Host to connect to

                                                                  + + +

                                                                  Trusted CA's certificate.

                                                                  +

                                                                  IP address or hostname of the host to connect to (leave blank for listening mode).

                                                                  +
                                                                  -

                                                                  one_peer_retention_mode

                                                                  -

                                                                  port

                                                                  -

                                                                  One peer retention

                                                                  -

                                                                  Connection port

                                                                  -

                                                                  This allows the retention to work even if the socket is listening

                                                                  -

                                                                  Port to listen on (empty host) or to connect to (with host filled).

                                                                  + +

                                                                  one_peer_retention_mode

                                                                  +

                                                                  port

                                                                  + + +

                                                                  One peer retention

                                                                  +

                                                                  Connection port

                                                                  + + +

                                                                  This allows the retention to work even if the socket is listening

                                                                  +

                                                                  Port to listen on (empty host) or to connect to (with host filled).

                                                                  +
                                                                  -

                                                                  private_key

                                                                  -

                                                                  Private key file.

                                                                  -

                                                                  Private key file path when TLS encryption is used.

                                                                  + +

                                                                  private_key

                                                                  + + +

                                                                  Private key file.

                                                                  + + +

                                                                  Private key file path when TLS encryption is used.

                                                                  +
                                                                  -

                                                                  protocol

                                                                  -

                                                                  Serialization protocol

                                                                  -

                                                                  Serialization protocol.

                                                                  -

                                                                  ndo

                                                                  + +

                                                                  protocol

                                                                  + + +

                                                                  Serialization protocol

                                                                  + + +

                                                                  Serialization protocol.

                                                                  + + +

                                                                  ndo

                                                                  + -

                                                                  public_cert

                                                                  -

                                                                  Public certificate

                                                                  -

                                                                  Public certificate file path when TLS encryption is used.

                                                                  + +

                                                                  public_cert

                                                                  + + +

                                                                  Public certificate

                                                                  + + +

                                                                  Public certificate file path when TLS encryption is used.

                                                                  +
                                                                  -

                                                                  tls

                                                                  -

                                                                  Enable TLS encryption

                                                                  -

                                                                  Enable TLS encryption.

                                                                  + +

                                                                  tls

                                                                  + + +

                                                                  Enable TLS encryption

                                                                  + + +

                                                                  Enable TLS encryption.

                                                                  +
                                                                  @@ -1104,23 +1166,35 @@ ipv6: -

                                                                  buffering_timeout

                                                                  -

                                                                  Buffering timeout

                                                                  -

                                                                  Time in seconds to wait before launching failover.

                                                                  + +

                                                                  buffering_timeout

                                                                  + + +

                                                                  Buffering timeout

                                                                  + + +

                                                                  Time in seconds to wait before launching failover.

                                                                  +
                                                                  -

                                                                  compression

                                                                  + +

                                                                  compression

                                                                  compression_buffer

                                                                  -

                                                                  compression_level

                                                                  -

                                                                  Compression (zlib)

                                                                  +

                                                                  compression_level

                                                                  + + +

                                                                  Compression (zlib)

                                                                  Compression buffer size

                                                                  -

                                                                  Compression level

                                                                  -

                                                                  Enable or not data stream compression.

                                                                  +

                                                                  Compression level

                                                                  + + +

                                                                  Enable or not data stream compression.

                                                                  The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                                  -

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +
                                                                  • @@ -1128,71 +1202,121 @@ ipv6:
                                                                  -

                                                                  retry_interval

                                                                  -

                                                                  Retry interval

                                                                  -

                                                                  Time in seconds to wait between each connection attempt.

                                                                  + +

                                                                  retry_interval

                                                                  + + +

                                                                  Retry interval

                                                                  + + +

                                                                  Time in seconds to wait between each connection attempt.

                                                                  +
                                                                  -

                                                                  category

                                                                  -

                                                                  Filter category

                                                                  -

                                                                  Category filter for flux in input

                                                                  + +

                                                                  category

                                                                  + + +

                                                                  Filter category

                                                                  + + +

                                                                  Category filter for flux in input

                                                                  +
                                                                  -

                                                                  ca_certificate

                                                                  -

                                                                  host

                                                                  -

                                                                  Trusted CA's certificate

                                                                  -

                                                                  Host to connect to

                                                                  -

                                                                  Trusted CA's certificate.

                                                                  -

                                                                  IP address or hostname of the host to connect to (leave blank for listening mode).

                                                                  + +

                                                                  ca_certificate

                                                                  +

                                                                  host

                                                                  + + +

                                                                  Trusted CA's certificate

                                                                  +

                                                                  Host to connect to

                                                                  + + +

                                                                  Trusted CA's certificate.

                                                                  +

                                                                  IP address or hostname of the host to connect to (leave blank for listening mode).

                                                                  +
                                                                  -

                                                                  one_peer_retention_mode

                                                                  -

                                                                  port

                                                                  -

                                                                  One peer retention

                                                                  -

                                                                  Connection port

                                                                  -

                                                                  This allows the retention to work even if the socket is listening

                                                                  -

                                                                  Port to listen on (empty host) or to connect to (with host filled).

                                                                  + +

                                                                  one_peer_retention_mode

                                                                  +

                                                                  port

                                                                  + + +

                                                                  One peer retention

                                                                  +

                                                                  Connection port

                                                                  + + +

                                                                  This allows the retention to work even if the socket is listening

                                                                  +

                                                                  Port to listen on (empty host) or to connect to (with host filled).

                                                                  +
                                                                  -

                                                                  private_key

                                                                  -

                                                                  Private key file.

                                                                  -

                                                                  Private key file path when TLS encryption is used.

                                                                  + +

                                                                  private_key

                                                                  + + +

                                                                  Private key file.

                                                                  + + +

                                                                  Private key file path when TLS encryption is used.

                                                                  +
                                                                  -

                                                                  protocol

                                                                  -

                                                                  Serialization protocol

                                                                  -

                                                                  Serialization protocol.

                                                                  -

                                                                  ndo

                                                                  + +

                                                                  protocol

                                                                  + + +

                                                                  Serialization protocol

                                                                  + + +

                                                                  Serialization protocol.

                                                                  + + +

                                                                  ndo

                                                                  + -

                                                                  public_cert

                                                                  -

                                                                  Public certificate

                                                                  -

                                                                  Public certificate file path when TLS encryption is used.

                                                                  + +

                                                                  public_cert

                                                                  + + +

                                                                  Public certificate

                                                                  + + +

                                                                  Public certificate file path when TLS encryption is used.

                                                                  +
                                                                  -

                                                                  tls

                                                                  -

                                                                  Enable TLS encryption

                                                                  -

                                                                  Enable TLS encryption.

                                                                  + +

                                                                  tls

                                                                  + + +

                                                                  Enable TLS encryption

                                                                  + + +

                                                                  Enable TLS encryption.

                                                                  +
                                                                  @@ -1213,23 +1337,35 @@ file: -

                                                                  buffering_timeout

                                                                  -

                                                                  Buffering timeout

                                                                  -

                                                                  Time in seconds to wait before launching failover.

                                                                  + +

                                                                  buffering_timeout

                                                                  + + +

                                                                  Buffering timeout

                                                                  + + +

                                                                  Time in seconds to wait before launching failover.

                                                                  +
                                                                  -

                                                                  compression

                                                                  + +

                                                                  compression

                                                                  compression_buffer

                                                                  -

                                                                  compression_level

                                                                  -

                                                                  Compression (zlib)

                                                                  +

                                                                  compression_level

                                                                  + + +

                                                                  Compression (zlib)

                                                                  Compression buffer size

                                                                  -

                                                                  Compression level

                                                                  -

                                                                  Enable or not data stream compression.

                                                                  +

                                                                  Compression level

                                                                  + + +

                                                                  Enable or not data stream compression.

                                                                  The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                                  -

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +

                                                                  Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                                  +
                                                                  • @@ -1237,34 +1373,60 @@ file:
                                                                  -

                                                                  retry_interval

                                                                  -

                                                                  Retry interval

                                                                  -

                                                                  Time in seconds to wait between each connection attempt.

                                                                  + +

                                                                  retry_interval

                                                                  + + +

                                                                  Retry interval

                                                                  + + +

                                                                  Time in seconds to wait between each connection attempt.

                                                                  +
                                                                  -

                                                                  max_size

                                                                  -

                                                                  Maximum size of file

                                                                  -

                                                                  Maximum size in bytes.

                                                                  + +

                                                                  max_size

                                                                  + + +

                                                                  Maximum size of file

                                                                  + + +

                                                                  Maximum size in bytes.

                                                                  +
                                                                  -

                                                                  path

                                                                  -

                                                                  File path

                                                                  -

                                                                  Path to the file.

                                                                  + +

                                                                  path

                                                                  + + +

                                                                  File path

                                                                  + + +

                                                                  Path to the file.

                                                                  +
                                                                  -

                                                                  protocol

                                                                  -

                                                                  Serialization protocol

                                                                  -

                                                                  Serialization protocol.

                                                                  -

                                                                  ndo

                                                                  + +

                                                                  protocol

                                                                  + + +

                                                                  Serialization protocol

                                                                  + + +

                                                                  Serialization protocol.

                                                                  + + +

                                                                  ndo

                                                                  + @@ -1284,50 +1446,88 @@ file: -

                                                                  config

                                                                  -

                                                                  Configuration messages

                                                                  -

                                                                  Enable or not configuration messages logging.

                                                                  + +

                                                                  config

                                                                  + + +

                                                                  Configuration messages

                                                                  + + +

                                                                  Enable or not configuration messages logging.

                                                                  +
                                                                  -

                                                                  debug

                                                                  -

                                                                  Debug messages

                                                                  -

                                                                  Enable or not debug messages logging.

                                                                  + +

                                                                  debug

                                                                  + + +

                                                                  Debug messages

                                                                  + + +

                                                                  Enable or not debug messages logging.

                                                                  +
                                                                  -

                                                                  error

                                                                  -

                                                                  Error messages

                                                                  -

                                                                  Enable or not error messages logging.

                                                                  + +

                                                                  error

                                                                  + + +

                                                                  Error messages

                                                                  + + +

                                                                  Enable or not error messages logging.

                                                                  +
                                                                  -

                                                                  info

                                                                  -

                                                                  Informational messages

                                                                  -

                                                                  Enable or not informational messages logging.

                                                                  + +

                                                                  info

                                                                  + + +

                                                                  Informational messages

                                                                  + + +

                                                                  Enable or not informational messages logging.

                                                                  +
                                                                  -

                                                                  level

                                                                  -

                                                                  Logging level

                                                                  -

                                                                  How much messages must be logged.

                                                                  -

                                                                  high,low,medium

                                                                  + +

                                                                  level

                                                                  + + +

                                                                  Logging level

                                                                  + + +

                                                                  How much messages must be logged.

                                                                  + + +

                                                                  high,low,medium

                                                                  + -

                                                                  max_size

                                                                  -

                                                                  name

                                                                  -

                                                                  Max file size in bytes

                                                                  -

                                                                  Name of the logger

                                                                  -

                                                                  The maximum size of log file.

                                                                  -

                                                                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                  + +

                                                                  max_size

                                                                  +

                                                                  name

                                                                  + + +

                                                                  Max file size in bytes

                                                                  +

                                                                  Name of the logger

                                                                  + + +

                                                                  The maximum size of log file.

                                                                  +

                                                                  For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                  +
                                                                  • @@ -1349,45 +1549,76 @@ standard: -

                                                                    config

                                                                    -

                                                                    Configuration messages

                                                                    -

                                                                    Enable or not configuration messages logging.

                                                                    + +

                                                                    config

                                                                    + + +

                                                                    Configuration messages

                                                                    + + +

                                                                    Enable or not configuration messages logging.

                                                                    +
                                                                    -

                                                                    debug

                                                                    -

                                                                    Debug messages

                                                                    -

                                                                    Enable or not debug messages logging.

                                                                    + +

                                                                    debug

                                                                    + + +

                                                                    Debug messages

                                                                    + + +

                                                                    Enable or not debug messages logging.

                                                                    +
                                                                    -

                                                                    error

                                                                    -

                                                                    Error messages

                                                                    -

                                                                    Enable or not error messages logging.

                                                                    + +

                                                                    error

                                                                    + + +

                                                                    Error messages

                                                                    + + +

                                                                    Enable or not error messages logging.

                                                                    +
                                                                    -

                                                                    info

                                                                    -

                                                                    Informational messages

                                                                    -

                                                                    Enable or not informational messages logging.

                                                                    + +

                                                                    info

                                                                    + + +

                                                                    Informational messages

                                                                    + + +

                                                                    Enable or not informational messages logging.

                                                                    +
                                                                    -

                                                                    level

                                                                    -

                                                                    name

                                                                    -

                                                                    Logging level

                                                                    -

                                                                    Name of the logger

                                                                    -

                                                                    How much messages must be logged.

                                                                    -

                                                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                    -

                                                                    high,low,medium

                                                                    + +

                                                                    level

                                                                    +

                                                                    name

                                                                    + + +

                                                                    Logging level

                                                                    +

                                                                    Name of the logger

                                                                    + + +

                                                                    How much messages must be logged.

                                                                    +

                                                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                    + + +

                                                                    high,low,medium

                                                                    @@ -1408,42 +1639,74 @@ syslog: -

                                                                    config

                                                                    -

                                                                    Configuration messages

                                                                    -

                                                                    Enable or not configuration messages logging.

                                                                    + +

                                                                    config

                                                                    + + +

                                                                    Configuration messages

                                                                    + + +

                                                                    Enable or not configuration messages logging.

                                                                    +
                                                                    -

                                                                    debug

                                                                    -

                                                                    Debug messages

                                                                    -

                                                                    Enable or not debug messages logging.

                                                                    + +

                                                                    debug

                                                                    + + +

                                                                    Debug messages

                                                                    + + +

                                                                    Enable or not debug messages logging.

                                                                    +
                                                                    -

                                                                    error

                                                                    -

                                                                    Error messages

                                                                    -

                                                                    Enable or not error messages logging.

                                                                    + +

                                                                    error

                                                                    + + +

                                                                    Error messages

                                                                    + + +

                                                                    Enable or not error messages logging.

                                                                    +
                                                                    -

                                                                    info

                                                                    -

                                                                    Informational messages

                                                                    -

                                                                    Enable or not informational messages logging.

                                                                    + +

                                                                    info

                                                                    + + +

                                                                    Informational messages

                                                                    + + +

                                                                    Enable or not informational messages logging.

                                                                    +
                                                                    -

                                                                    level

                                                                    -

                                                                    Logging level

                                                                    -

                                                                    How much messages must be logged.

                                                                    -

                                                                    high,low,medium

                                                                    + +

                                                                    level

                                                                    + + +

                                                                    Logging level

                                                                    + + +

                                                                    How much messages must be logged.

                                                                    + + +

                                                                    high,low,medium

                                                                    + @@ -1461,45 +1724,76 @@ monitoring: -

                                                                    config

                                                                    -

                                                                    Configuration messages

                                                                    -

                                                                    Enable or not configuration messages logging.

                                                                    + +

                                                                    config

                                                                    + + +

                                                                    Configuration messages

                                                                    + + +

                                                                    Enable or not configuration messages logging.

                                                                    +
                                                                    -

                                                                    debug

                                                                    -

                                                                    Debug messages

                                                                    -

                                                                    Enable or not debug messages logging.

                                                                    + +

                                                                    debug

                                                                    + + +

                                                                    Debug messages

                                                                    + + +

                                                                    Enable or not debug messages logging.

                                                                    +
                                                                    -

                                                                    error

                                                                    -

                                                                    Error messages

                                                                    -

                                                                    Enable or not error messages logging.

                                                                    + +

                                                                    error

                                                                    + + +

                                                                    Error messages

                                                                    + + +

                                                                    Enable or not error messages logging.

                                                                    +
                                                                    -

                                                                    info

                                                                    -

                                                                    Informational messages

                                                                    -

                                                                    Enable or not informational messages logging.

                                                                    + +

                                                                    info

                                                                    + + +

                                                                    Informational messages

                                                                    + + +

                                                                    Enable or not informational messages logging.

                                                                    +
                                                                    -

                                                                    level

                                                                    -

                                                                    name

                                                                    -

                                                                    Logging level

                                                                    -

                                                                    Name of the logger

                                                                    -

                                                                    How much messages must be logged.

                                                                    -

                                                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                    -

                                                                    high,low,medium

                                                                    + +

                                                                    level

                                                                    +

                                                                    name

                                                                    + + +

                                                                    Logging level

                                                                    +

                                                                    Name of the logger

                                                                    + + +

                                                                    How much messages must be logged.

                                                                    +

                                                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                                    + + +

                                                                    high,low,medium

                                                                    @@ -1575,33 +1869,57 @@ rrd: -

                                                                    buffering_timeout

                                                                    -

                                                                    Buffering timeout

                                                                    -

                                                                    Time in seconds to wait before launching failover.

                                                                    + +

                                                                    buffering_timeout

                                                                    + + +

                                                                    Buffering timeout

                                                                    + + +

                                                                    Time in seconds to wait before launching failover.

                                                                    +
                                                                    -

                                                                    failover

                                                                    -

                                                                    Failover name

                                                                    -

                                                                    Name of the output which will act as failover

                                                                    + +

                                                                    failover

                                                                    + + +

                                                                    Failover name

                                                                    + + +

                                                                    Name of the output which will act as failover

                                                                    +
                                                                    -

                                                                    retry_interval

                                                                    -

                                                                    Retry interval

                                                                    -

                                                                    Time in seconds to wait between each connection attempt.

                                                                    + +

                                                                    retry_interval

                                                                    + + +

                                                                    Retry interval

                                                                    + + +

                                                                    Time in seconds to wait between each connection attempt.

                                                                    +
                                                                    -

                                                                    category

                                                                    -

                                                                    Filter category

                                                                    -

                                                                    Category filter for flux in output.

                                                                    + +

                                                                    category

                                                                    + + +

                                                                    Filter category

                                                                    + + +

                                                                    Category filter for flux in output.

                                                                    +
                                                                    • @@ -1609,15 +1927,21 @@ rrd:
                                                                    -

                                                                    metrics_path

                                                                    + +

                                                                    metrics_path

                                                                    path

                                                                    -

                                                                    port

                                                                    -

                                                                    RRD file directory for metrics

                                                                    +

                                                                    port

                                                                    + + +

                                                                    RRD file directory for metrics

                                                                    Unix socket

                                                                    -

                                                                    TCP port

                                                                    -

                                                                    RRD file directory, for example /var/lib/centreon/metrics

                                                                    +

                                                                    TCP port

                                                                    + + +

                                                                    RRD file directory, for example /var/lib/centreon/metrics

                                                                    The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                                    -

                                                                    The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                                    +

                                                                    The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                                    +
                                                                    • @@ -1625,33 +1949,57 @@ rrd:
                                                                    -

                                                                    status_path

                                                                    -

                                                                    RRD file directory for statuses

                                                                    -

                                                                    RRD file directory, for example /var/lib/centreon/status

                                                                    + +

                                                                    status_path

                                                                    + + +

                                                                    RRD file directory for statuses

                                                                    + + +

                                                                    RRD file directory, for example /var/lib/centreon/status

                                                                    +
                                                                    -

                                                                    write_metrics

                                                                    -

                                                                    Enable write_metrics

                                                                    -

                                                                    Enable or not write_metrics.

                                                                    + +

                                                                    write_metrics

                                                                    + + +

                                                                    Enable write_metrics

                                                                    + + +

                                                                    Enable or not write_metrics.

                                                                    +
                                                                    -

                                                                    write_status

                                                                    -

                                                                    Enable write_status

                                                                    -

                                                                    Enable or not write_status.

                                                                    + +

                                                                    write_status

                                                                    + + +

                                                                    Enable write_status

                                                                    + + +

                                                                    Enable or not write_status.

                                                                    +
                                                                    -

                                                                    store_in_data_bin

                                                                    -

                                                                    Enable store_in_data_bin

                                                                    -

                                                                    Enable or not store in performance data in data_bin.

                                                                    + +

                                                                    store_in_data_bin

                                                                    + + +

                                                                    Enable store_in_data_bin

                                                                    + + +

                                                                    Enable or not store in performance data in data_bin.

                                                                    +
                                                                    • @@ -1674,36 +2022,60 @@ storage: -

                                                                      buffering_timeout

                                                                      -

                                                                      Buffering timeout

                                                                      -

                                                                      Time in seconds to wait before launching failover.

                                                                      + +

                                                                      buffering_timeout

                                                                      + + +

                                                                      Buffering timeout

                                                                      + + +

                                                                      Time in seconds to wait before launching failover.

                                                                      +
                                                                      -

                                                                      failover

                                                                      -

                                                                      Failover name

                                                                      -

                                                                      Name of the output which will act as failover

                                                                      + +

                                                                      failover

                                                                      + + +

                                                                      Failover name

                                                                      + + +

                                                                      Name of the output which will act as failover

                                                                      +
                                                                      -

                                                                      retry_interval

                                                                      -

                                                                      Retry interval

                                                                      -

                                                                      Time in seconds to wait between each connection attempt.

                                                                      + +

                                                                      retry_interval

                                                                      + + +

                                                                      Retry interval

                                                                      + + +

                                                                      Time in seconds to wait between each connection attempt.

                                                                      +
                                                                      -

                                                                      category

                                                                      -

                                                                      check_replication

                                                                      -

                                                                      Filter category

                                                                      -

                                                                      Replication enabled

                                                                      -

                                                                      Category filter for flux in output.

                                                                      -

                                                                      When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                                      + +

                                                                      category

                                                                      +

                                                                      check_replication

                                                                      + + +

                                                                      Filter category

                                                                      +

                                                                      Replication enabled

                                                                      + + +

                                                                      Category filter for flux in output.

                                                                      +

                                                                      When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                                      +
                                                                      • @@ -1714,91 +2086,159 @@ storage:
                                                                      -

                                                                      db_host

                                                                      -

                                                                      DB host

                                                                      -

                                                                      IP address or hostname of the database server.

                                                                      + +

                                                                      db_host

                                                                      + + +

                                                                      DB host

                                                                      + + +

                                                                      IP address or hostname of the database server.

                                                                      +
                                                                      -

                                                                      db_name

                                                                      -

                                                                      DB name

                                                                      -

                                                                      Database name.

                                                                      + +

                                                                      db_name

                                                                      + + +

                                                                      DB name

                                                                      + + +

                                                                      Database name.

                                                                      +
                                                                      -

                                                                      db_password

                                                                      -

                                                                      DB password

                                                                      -

                                                                      Password of database user.

                                                                      + +

                                                                      db_password

                                                                      + + +

                                                                      DB password

                                                                      + + +

                                                                      Password of database user.

                                                                      +
                                                                      -

                                                                      db_port

                                                                      -

                                                                      DB port

                                                                      -

                                                                      Port on which the DB server listens

                                                                      + +

                                                                      db_port

                                                                      + + +

                                                                      DB port

                                                                      + + +

                                                                      Port on which the DB server listens

                                                                      +
                                                                      -

                                                                      db_type

                                                                      -

                                                                      DB type

                                                                      -

                                                                      Target DBMS.

                                                                      -

                                                                      db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                                      + +

                                                                      db_type

                                                                      + + +

                                                                      DB type

                                                                      + + +

                                                                      Target DBMS.

                                                                      + + +

                                                                      db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                                      + -

                                                                      db_user

                                                                      -

                                                                      DB user

                                                                      -

                                                                      Database user.

                                                                      + +

                                                                      db_user

                                                                      + + +

                                                                      DB user

                                                                      + + +

                                                                      Database user.

                                                                      +
                                                                      -

                                                                      interval

                                                                      -

                                                                      Interval length

                                                                      -

                                                                      Interval length in seconds.

                                                                      + +

                                                                      interval

                                                                      + + +

                                                                      Interval length

                                                                      + + +

                                                                      Interval length in seconds.

                                                                      +
                                                                      -

                                                                      length

                                                                      -

                                                                      RRD length

                                                                      -

                                                                      RRD storage duration in seconds.

                                                                      + +

                                                                      length

                                                                      + + +

                                                                      RRD length

                                                                      + + +

                                                                      RRD storage duration in seconds.

                                                                      +
                                                                      -

                                                                      queries_per_transaction

                                                                      -

                                                                      Maximum queries per transaction

                                                                      -

                                                                      The maximum queries per transaction before commit.

                                                                      + +

                                                                      queries_per_transaction

                                                                      + + +

                                                                      Maximum queries per transaction

                                                                      + + +

                                                                      The maximum queries per transaction before commit.

                                                                      +
                                                                      -

                                                                      read_timeout

                                                                      -

                                                                      rebuild_check_interval

                                                                      -

                                                                      Transaction commit timeout

                                                                      -

                                                                      Rebuild check interval in seconds

                                                                      -

                                                                      The transaction timeout before running commit.

                                                                      -

                                                                      The interval between check if some metrics must be rebuild. The default value is 300s

                                                                      + +

                                                                      read_timeout

                                                                      +

                                                                      rebuild_check_interval

                                                                      + + +

                                                                      Transaction commit timeout

                                                                      +

                                                                      Rebuild check interval in seconds

                                                                      + + +

                                                                      The transaction timeout before running commit.

                                                                      +

                                                                      The interval between check if some metrics must be rebuild. The default value is 300s

                                                                      +
                                                                      -

                                                                      store_in_data_bin

                                                                      -

                                                                      Enable store_in_data_bin

                                                                      -

                                                                      Enable or not store in performance data in data_bin.

                                                                      + +

                                                                      store_in_data_bin

                                                                      + + +

                                                                      Enable store_in_data_bin

                                                                      + + +

                                                                      Enable or not store in performance data in data_bin.

                                                                      +
                                                                      • @@ -1821,36 +2261,60 @@ sql: -

                                                                        buffering_timeout

                                                                        -

                                                                        Buffering timeout

                                                                        -

                                                                        Time in seconds to wait before launching failover.

                                                                        + +

                                                                        buffering_timeout

                                                                        + + +

                                                                        Buffering timeout

                                                                        + + +

                                                                        Time in seconds to wait before launching failover.

                                                                        +
                                                                        -

                                                                        failover

                                                                        -

                                                                        Failover name

                                                                        -

                                                                        Name of the output which will act as failover

                                                                        + +

                                                                        failover

                                                                        + + +

                                                                        Failover name

                                                                        + + +

                                                                        Name of the output which will act as failover

                                                                        +
                                                                        -

                                                                        retry_interval

                                                                        -

                                                                        Retry interval

                                                                        -

                                                                        Time in seconds to wait between each connection attempt.

                                                                        + +

                                                                        retry_interval

                                                                        + + +

                                                                        Retry interval

                                                                        + + +

                                                                        Time in seconds to wait between each connection attempt.

                                                                        +
                                                                        -

                                                                        category

                                                                        -

                                                                        check_replication

                                                                        -

                                                                        Filter category

                                                                        -

                                                                        Replication enabled

                                                                        -

                                                                        Category filter for flux in output.

                                                                        -

                                                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                                        + +

                                                                        category

                                                                        +

                                                                        check_replication

                                                                        + + +

                                                                        Filter category

                                                                        +

                                                                        Replication enabled

                                                                        + + +

                                                                        Category filter for flux in output.

                                                                        +

                                                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                                        +
                                                                        • @@ -1861,63 +2325,113 @@ sql:
                                                                        -

                                                                        db_host

                                                                        -

                                                                        DB host

                                                                        -

                                                                        IP address or hostname of the database server.

                                                                        + +

                                                                        db_host

                                                                        + + +

                                                                        DB host

                                                                        + + +

                                                                        IP address or hostname of the database server.

                                                                        +
                                                                        -

                                                                        db_name

                                                                        -

                                                                        DB name

                                                                        -

                                                                        Database name.

                                                                        + +

                                                                        db_name

                                                                        + + +

                                                                        DB name

                                                                        + + +

                                                                        Database name.

                                                                        +
                                                                        -

                                                                        db_password

                                                                        -

                                                                        DB password

                                                                        -

                                                                        Password of database user.

                                                                        + +

                                                                        db_password

                                                                        + + +

                                                                        DB password

                                                                        + + +

                                                                        Password of database user.

                                                                        +
                                                                        -

                                                                        db_port

                                                                        -

                                                                        DB port

                                                                        -

                                                                        Port on which the DB server listens

                                                                        + +

                                                                        db_port

                                                                        + + +

                                                                        DB port

                                                                        + + +

                                                                        Port on which the DB server listens

                                                                        +
                                                                        -

                                                                        db_type

                                                                        -

                                                                        DB type

                                                                        -

                                                                        Target DBMS.

                                                                        -

                                                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                                        + +

                                                                        db_type

                                                                        + + +

                                                                        DB type

                                                                        + + +

                                                                        Target DBMS.

                                                                        + + +

                                                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                                        + -

                                                                        db_user

                                                                        -

                                                                        DB user

                                                                        -

                                                                        Database user.

                                                                        + +

                                                                        db_user

                                                                        + + +

                                                                        DB user

                                                                        + + +

                                                                        Database user.

                                                                        +
                                                                        -

                                                                        queries_per_transaction

                                                                        -

                                                                        Maximum queries per transaction

                                                                        -

                                                                        The maximum queries per transaction before commit.

                                                                        + +

                                                                        queries_per_transaction

                                                                        + + +

                                                                        Maximum queries per transaction

                                                                        + + +

                                                                        The maximum queries per transaction before commit.

                                                                        +
                                                                        -

                                                                        read_timeout

                                                                        -

                                                                        Transaction commit timeout

                                                                        -

                                                                        The transaction timeout before running commit.

                                                                        + +

                                                                        read_timeout

                                                                        + + +

                                                                        Transaction commit timeout

                                                                        + + +

                                                                        The transaction timeout before running commit.

                                                                        +
                                                                        diff --git a/versioned_docs/version-23.04/api/graph-views-api.md b/versioned_docs/version-23.04/api/graph-views-api.md index 35bd67bcddce..df5a176b49a5 100644 --- a/versioned_docs/version-23.04/api/graph-views-api.md +++ b/versioned_docs/version-23.04/api/graph-views-api.md @@ -48,14 +48,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token), you'll need to +In the result, retrieve the \{studio-session\} (token), you'll need to use it all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -69,7 +69,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -77,7 +77,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/versioned_docs/version-23.04/api/graph-views-map-api.md b/versioned_docs/version-23.04/api/graph-views-map-api.md index c4c2a325680f..bd2a0fdcb217 100644 --- a/versioned_docs/version-23.04/api/graph-views-map-api.md +++ b/versioned_docs/version-23.04/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 23.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 23.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-23.04/api/rest-api-v1.md b/versioned_docs/version-23.04/api/rest-api-v1.md index 193e248e42bd..891a7a8306ff 100644 --- a/versioned_docs/version-23.04/api/rest-api-v1.md +++ b/versioned_docs/version-23.04/api/rest-api-v1.md @@ -2483,8 +2483,8 @@ Use the GET method and URL below: : Additionnal information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-23.04/api/rest-api-v2.md b/versioned_docs/version-23.04/api/rest-api-v2.md index f3ed99ce646b..01eccba94ccd 100644 --- a/versioned_docs/version-23.04/api/rest-api-v2.md +++ b/versioned_docs/version-23.04/api/rest-api-v2.md @@ -66,12 +66,12 @@ Then click on **Add**, and select it in the environments list. > > Here is an exemple of output for this command: > -> { +> \{ > "version": "23.04.6", > "major": "23", > "minor": "04", > "fix": "6" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/versioned_docs/version-23.04/connect/openid.md b/versioned_docs/version-23.04/connect/openid.md index 1fada7aba416..3c2b32af1fa2 100644 --- a/versioned_docs/version-23.04/connect/openid.md +++ b/versioned_docs/version-23.04/connect/openid.md @@ -213,8 +213,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -225,7 +225,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -233,8 +233,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -245,7 +245,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -253,8 +253,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -273,8 +273,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-23.04/connect/saml.md b/versioned_docs/version-23.04/connect/saml.md index 20dd4e503a69..8520fe7de8ce 100644 --- a/versioned_docs/version-23.04/connect/saml.md +++ b/versioned_docs/version-23.04/connect/saml.md @@ -127,6 +127,6 @@ users. Here is an example of fields you may have to fill in: | IdP option | Centreon value | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https:/\ | +| Assertion Consumer Service (ACS) URL | https:/\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https:/\/centreon/api/latest/saml/sls | diff --git a/versioned_docs/version-23.04/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-23.04/developer/developer-gorgone-client-server-communication.md index 5caa80bbb37d..7f52ac58ec57 100644 --- a/versioned_docs/version-23.04/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-23.04/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-23.04/developer/developer-translate-centreon.md b/versioned_docs/version-23.04/developer/developer-translate-centreon.md index 489bc5c4d7e5..a9ff1810aca1 100644 --- a/versioned_docs/version-23.04/developer/developer-translate-centreon.md +++ b/versioned_docs/version-23.04/developer/developer-translate-centreon.md @@ -142,7 +142,7 @@ will allow for all person using Centreon to have access to your translation on t * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-23.04/developer/developer-widget.md b/versioned_docs/version-23.04/developer/developer-widget.md index cda4533aad87..b36d0051e1c6 100644 --- a/versioned_docs/version-23.04/developer/developer-widget.md +++ b/versioned_docs/version-23.04/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They have to be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-23.04/graph-views/install.md b/versioned_docs/version-23.04/graph-views/install.md index 743f2836e5d1..6d7b6ff282c9 100644 --- a/versioned_docs/version-23.04/graph-views/install.md +++ b/versioned_docs/version-23.04/graph-views/install.md @@ -152,7 +152,7 @@ default value. Modify the following file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-23.04/graph-views/troubleshooter.md b/versioned_docs/version-23.04/graph-views/troubleshooter.md index 190580f7c852..6dadbdc88b4a 100644 --- a/versioned_docs/version-23.04/graph-views/troubleshooter.md +++ b/versioned_docs/version-23.04/graph-views/troubleshooter.md @@ -157,7 +157,7 @@ To open the appropriate ports: /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Replace by the port your Centreon MAP server is using (mostly 8080 or +> Replace \ by the port your Centreon MAP server is using (mostly 8080 or > 8443 if you have configured it in SSL). To simply disable your firewall, execute: @@ -285,7 +285,7 @@ specify a new one to your desktop client. To do so, edit the file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -371,7 +371,7 @@ is working hard, your desktop client requires more memory. ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-23.04/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-23.04/installation/installation-of-a-central-server/using-packages.md index d3c30c4c5232..0cc8904c801c 100644 --- a/versioned_docs/version-23.04/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-23.04/installation/installation-of-a-central-server/using-packages.md @@ -540,9 +540,9 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTION FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** by the user's credentials. +> Replace **\** and **\** by the user's credentials. This user will only be used for the installation process: once the [web installation](../web-and-post-installation.md) is complete you can delete this user using: diff --git a/versioned_docs/version-23.04/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-23.04/installation/installation-of-a-poller/using-packages.md index 20a7e7b269ac..dfc31d480463 100644 --- a/versioned_docs/version-23.04/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-23.04/installation/installation-of-a-poller/using-packages.md @@ -394,9 +394,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** by the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** by the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -447,19 +447,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2023-05-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2023-05-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2023-05-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md index 431e4ab30d4d..ef5d1cbf67e8 100644 --- a/versioned_docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-23.04/installation/installation-of-a-remote-server/using-packages.md @@ -530,9 +530,9 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** by user's credentials. +> Replace **\** and **\** by user's credentials. This user will only be used for the installation process. Once the [web installation](../web-and-post-installation.md) is complete you can delete this user using: @@ -754,7 +754,7 @@ To transform the server into a Remote Server and to register it to the Central s ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -763,12 +763,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** by the IP of the central server, as seen by the remote server. +> Replace **\** by the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -845,19 +845,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.04/installation/prerequisites.md b/versioned_docs/version-23.04/installation/prerequisites.md index 903787a6f5c6..9514ccf424a2 100644 --- a/versioned_docs/version-23.04/installation/prerequisites.md +++ b/versioned_docs/version-23.04/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                                        If you perform backups, use the following characteristics:

                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually

                                                                        | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                                        If you perform backups, use the following characteristics:
                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually
                                                                        | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                                        If you perform backups, use the following characteristics:

                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually

                                                                        | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                                        If you perform backups, use the following characteristics:
                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually
                                                                        | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                                        If you perform backups, use the following characteristics:

                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually

                                                                        | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                                        If you perform backups, use the following characteristics:
                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually
                                                                        | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                                        If you perform backups, use the following characteristics:

                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually

                                                                        | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                                        If you perform backups, use the following characteristics:
                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually
                                                                        | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                                        If you perform backups, use the following characteristics:

                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually

                                                                        | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                                        If you perform backups, use the following characteristics:
                                                                        • size of the /var/lib/mysql partition * 0,6
                                                                        • this size is meant for 1 full backup and 6 partial ones
                                                                        • this is only an estimate, size should be checked manually
                                                                        | **Database server** diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-clickhouse.md index f751a6badd42..f873d336f5bf 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-events.md index 0b0aa67e9b2b..27015e24557c 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-events.md @@ -147,7 +147,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md index 4ff3ba57e949..98025e94b41f 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-datadog-metrics.md @@ -150,7 +150,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-logstash-events.md index c9b668a40cb3..63754be51156 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-logstash-events.md @@ -148,7 +148,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *8080*. diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-events.md index 2d0f5f4db5fe..1af1e4ab60fd 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md index 6b1209efb93a..a29dcb6fb7c5 100644 --- a/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-23.04/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-23.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-23.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md index b4df9a7f0c80..7c919f76d116 100644 --- a/versioned_docs/version-23.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-23.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-23.04/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-23.04/integrations/event-management/sc-opsgenie.md index 11ca4f35304c..ec0f6c5c437e 100644 --- a/versioned_docs/version-23.04/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-23.04/integrations/event-management/sc-opsgenie.md @@ -139,10 +139,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -186,7 +186,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg:\{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg:\{last_update\} is a timestamp macro. You can use\{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-23.04/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-23.04/integrations/event-management/sc-pagerduty-events.md index 252ed7d62adb..85f6f45e7df2 100644 --- a/versioned_docs/version-23.04/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-23.04/integrations/event-management/sc-pagerduty-events.md @@ -196,7 +196,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-23.04/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-23.04/integrations/itsm/ot-bmc-remedy.md index 5f3575f52783..2fdd808fbf8b 100644 --- a/versioned_docs/version-23.04/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-23.04/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-23.04/integrations/itsm/ot-mail.md b/versioned_docs/version-23.04/integrations/itsm/ot-mail.md index c1cebed25eb4..8d19670732b5 100644 --- a/versioned_docs/version-23.04/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-23.04/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.emai\l} | | To | | ## Possibilities diff --git a/versioned_docs/version-23.04/integrations/itsm/ot-serena.md b/versioned_docs/version-23.04/integrations/itsm/ot-serena.md index c8baea432be2..1d7f5c60419b 100644 --- a/versioned_docs/version-23.04/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-23.04/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-23.04/integrations/notifications/plugin-telegram.md b/versioned_docs/version-23.04/integrations/notifications/plugin-telegram.md index d218e24bd569..4feb052f61e6 100644 --- a/versioned_docs/version-23.04/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-23.04/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-23.04/integrations/stream-connectors.md b/versioned_docs/version-23.04/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-23.04/integrations/stream-connectors.md +++ b/versioned_docs/version-23.04/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-23.04/metrology/grafana.md b/versioned_docs/version-23.04/metrology/grafana.md index c64eafa03233..f7a750f997d1 100644 --- a/versioned_docs/version-23.04/metrology/grafana.md +++ b/versioned_docs/version-23.04/metrology/grafana.md @@ -86,5 +86,5 @@ Use [variables](https://grafana.com/docs/grafana/latest/variables/) to select a You can customize how the labels for the curves are displayed: go to **Time Series > Standard options**, then use [the **Display name** field](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* For instance, if you enter **${__field.labels}**, the label includes all possible label customizations (host, service, metric_name). -* If you enter **${__field.labels.host}: ${__field.labels.metric_name}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. +* For instance, if you enter **$\{__field.labels\}**, the label includes all possible label customizations (host, service, metric_name). +* If you enter **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. diff --git a/versioned_docs/version-23.04/migrate/migrate-from-3-4.md b/versioned_docs/version-23.04/migrate/migrate-from-3-4.md index 3ea95590fc0d..923fe6f3244e 100644 --- a/versioned_docs/version-23.04/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-23.04/migrate/migrate-from-3-4.md @@ -79,7 +79,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** by the IP or the new Centreon server. +> Replace **\** by the IP or the new Centreon server. ### Retrieve databases @@ -149,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP or the new Centreon server. +> Replace **\** by the IP or the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-23.04/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-23.04/migrate/migrate-from-el-to-debian.md index 0e5ba518db4f..505cbd4d4c60 100644 --- a/versioned_docs/version-23.04/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-23.04/migrate/migrate-from-el-to-debian.md @@ -65,7 +65,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -149,7 +149,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-23.04/migrate/migrate-from-el-to-el.md b/versioned_docs/version-23.04/migrate/migrate-from-el-to-el.md index 4cc7132dac92..11c0dc2472cc 100644 --- a/versioned_docs/version-23.04/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-23.04/migrate/migrate-from-el-to-el.md @@ -85,7 +85,7 @@ apt update rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -156,7 +156,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-23.04/migrate/nagios-to-centreon.md b/versioned_docs/version-23.04/migrate/nagios-to-centreon.md index 32779a2fd96a..edd8b942958c 100644 --- a/versioned_docs/version-23.04/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-23.04/migrate/nagios-to-centreon.md @@ -105,4 +105,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** by password of **admin** Centreon web user. +Replace **\** by password of **admin** Centreon web user. diff --git a/versioned_docs/version-23.04/migrate/poller-display-to-remote-server.md b/versioned_docs/version-23.04/migrate/poller-display-to-remote-server.md index b7d3a4ac16f4..3cb5a3e77072 100644 --- a/versioned_docs/version-23.04/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-23.04/migrate/poller-display-to-remote-server.md @@ -47,7 +47,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -56,12 +56,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** by the IP of the Centreon server seen by the Remote Server. +> Replace **\** by the IP of the Centreon server seen by the Remote Server. -> The **** must have access to configuration API. You can use default **admin** account. +> The **\** must have access to configuration API. You can use default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -138,19 +138,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed connect to 192.168.0.1:444; Connection refused ``` -> Unable to access to the API. Please check ****, scheme and port. +> Unable to access to the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 14e3df5905f7..430b077a3dff 100644 --- a/versioned_docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-23.04/monitoring/monitoring-servers/communications.md b/versioned_docs/version-23.04/monitoring/monitoring-servers/communications.md index 4999380c21dd..c206ccb6831c 100644 --- a/versioned_docs/version-23.04/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-23.04/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow to retrieve Remote's thumbprint therefore it's > not possible to display Poller's Gorgone configuration from Centreon UI. diff --git a/versioned_docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md index b94cb72f9d16..f6075e3259cb 100644 --- a/versioned_docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go into the **Configuration > SNMP traps > SNMP traps** menu and click on **Add* > It is possible to construct the output message yourself. For this, use the MIB to know the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by a OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-23.04/releases/centreon-commercial-extensions.mdx b/versioned_docs/version-23.04/releases/centreon-commercial-extensions.mdx index 5c2b9f0ab387..e36aeedbbb48 100644 --- a/versioned_docs/version-23.04/releases/centreon-commercial-extensions.mdx +++ b/versioned_docs/version-23.04/releases/centreon-commercial-extensions.mdx @@ -998,7 +998,7 @@ Release date: `July 4, 2024` Bug fixes - [Packaging] Added missing dependencies on anomaly detection. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**.
                      diff --git a/versioned_docs/version-23.04/reporting/report-development.md b/versioned_docs/version-23.04/reporting/report-development.md index f79a8faaeac1..72e45d3ce683 100644 --- a/versioned_docs/version-23.04/reporting/report-development.md +++ b/versioned_docs/version-23.04/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-23.04/reporting/reports-publication-rule.md b/versioned_docs/version-23.04/reporting/reports-publication-rule.md index 9416a817ff9b..f1ad61ba74a4 100644 --- a/versioned_docs/version-23.04/reporting/reports-publication-rule.md +++ b/versioned_docs/version-23.04/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Reports publication rules {#publication_rules} +Reports publication rules \{#publication_rules\} ========================= The menu \"Reporting \> Business Intelligence \> Publication rules\" @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_docs/version-23.10/administration/logging-configuration-changes.md b/versioned_docs/version-23.10/administration/logging-configuration-changes.md index 2e13b45e3076..32ed0c77f04f 100644 --- a/versioned_docs/version-23.10/administration/logging-configuration-changes.md +++ b/versioned_docs/version-23.10/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table: Modification type -

                      Contains the type of action applied. There are several possible types of action:

                      + +

                      Contains the type of action applied. There are several possible types of action:

                      • Added: Indicates that the object has been added
                      • Changed: Indicates that the object has been changed
                        • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                        The last column describes the change itself :

                        + +

                        The last column describes the change itself :

                        • Field name: Describes the field that has been changed
                        • Before: Indicates the previous value
                          • diff --git a/versioned_docs/version-23.10/administration/parameters/ldap.md b/versioned_docs/version-23.10/administration/parameters/ldap.md index 769c7622b8df..9b75c0fa6a90 100644 --- a/versioned_docs/version-23.10/administration/parameters/ldap.md +++ b/versioned_docs/version-23.10/administration/parameters/ldap.md @@ -98,6 +98,6 @@ on the MS Active Directory, Okta, or Posix-type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for the **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for the **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for the **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for the **Search group > base DN** field. \ No newline at end of file diff --git a/versioned_docs/version-23.10/administration/secure-platform.md b/versioned_docs/version-23.10/administration/secure-platform.md index ac8af3cf5021..49fc5dd88478 100644 --- a/versioned_docs/version-23.10/administration/secure-platform.md +++ b/versioned_docs/version-23.10/administration/secure-platform.md @@ -771,17 +771,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-23.10/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-23.10/alerts-notifications/notif-config-for-teams.md index 9ed4c4bd81cb..54f4445a9fe8 100644 --- a/versioned_docs/version-23.10/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-23.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-23.10/alerts-notifications/resources-status.md b/versioned_docs/version-23.10/alerts-notifications/resources-status.md index 4311d9fa8bae..e3facb4454f8 100644 --- a/versioned_docs/version-23.10/alerts-notifications/resources-status.md +++ b/versioned_docs/version-23.10/alerts-notifications/resources-status.md @@ -293,7 +293,7 @@ Graphs display metric evolution over a given period. This can be defined in the - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Whenever the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-23.10/alerts-notifications/ticketing.md b/versioned_docs/version-23.10/alerts-notifications/ticketing.md index 3d41997a6d69..4b4c97827b3b 100644 --- a/versioned_docs/version-23.10/alerts-notifications/ticketing.md +++ b/versioned_docs/version-23.10/alerts-notifications/ticketing.md @@ -138,9 +138,9 @@ The module stores the user list selection in an array (can be used in a smart section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-23.10/api/clapi.md b/versioned_docs/version-23.10/api/clapi.md index fb2dd8995659..d1c375664c3e 100644 --- a/versioned_docs/version-23.10/api/clapi.md +++ b/versioned_docs/version-23.10/api/clapi.md @@ -573,13 +573,13 @@ Let's assume that you would like to grant full access to the \[Monitoring\] menu centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Monitoring" ``` -Then you would like to grant access to the \[Home\] \> \[Poller statistics\] menu: +Then you would like to grant access to the \[Home\] > \[Poller statistics\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Home;Poller statistics" ``` -Then you would like to grant read-only access to the \[Configuration\] \> \[Hosts\] menu: +Then you would like to grant read-only access to the \[Configuration\] > \[Hosts\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantro -v "ACL Menu test;1;Configuration;Hosts" @@ -994,23 +994,35 @@ ipv4: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1018,71 +1030,121 @@ ipv4:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1103,23 +1165,35 @@ ipv6: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1127,71 +1201,121 @@ ipv6:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          category

                          -

                          Filter category

                          -

                          Category filter for flux in input

                          + +

                          category

                          + + +

                          Filter category

                          + + +

                          Category filter for flux in input

                          +
                          -

                          ca_certificate

                          -

                          host

                          -

                          Trusted CA's certificate

                          -

                          Host to connect to

                          -

                          Trusted CA's certificate.

                          -

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          + +

                          ca_certificate

                          +

                          host

                          + + +

                          Trusted CA's certificate

                          +

                          Host to connect to

                          + + +

                          Trusted CA's certificate.

                          +

                          IP address or hostname of the host to connect to (leave blank for listening mode).

                          +
                          -

                          one_peer_retention_mode

                          -

                          port

                          -

                          One peer retention

                          -

                          Connection port

                          -

                          This allows the retention to work even if the socket is listening

                          -

                          Port to listen on (empty host) or to connect to (with host filled).

                          + +

                          one_peer_retention_mode

                          +

                          port

                          + + +

                          One peer retention

                          +

                          Connection port

                          + + +

                          This allows the retention to work even if the socket is listening

                          +

                          Port to listen on (empty host) or to connect to (with host filled).

                          +
                          -

                          private_key

                          -

                          Private key file.

                          -

                          Private key file path when TLS encryption is used.

                          + +

                          private_key

                          + + +

                          Private key file.

                          + + +

                          Private key file path when TLS encryption is used.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + -

                          public_cert

                          -

                          Public certificate

                          -

                          Public certificate file path when TLS encryption is used.

                          + +

                          public_cert

                          + + +

                          Public certificate

                          + + +

                          Public certificate file path when TLS encryption is used.

                          +
                          -

                          tls

                          -

                          Enable TLS encryption

                          -

                          Enable TLS encryption.

                          + +

                          tls

                          + + +

                          Enable TLS encryption

                          + + +

                          Enable TLS encryption.

                          +
                          @@ -1212,23 +1336,35 @@ file: -

                          buffering_timeout

                          -

                          Buffering timeout

                          -

                          Time in seconds to wait before launching failover.

                          + +

                          buffering_timeout

                          + + +

                          Buffering timeout

                          + + +

                          Time in seconds to wait before launching failover.

                          +
                          -

                          compression

                          + +

                          compression

                          compression_buffer

                          -

                          compression_level

                          -

                          Compression (zlib)

                          +

                          compression_level

                          + + +

                          Compression (zlib)

                          Compression buffer size

                          -

                          Compression level

                          -

                          Enable or not data stream compression.

                          +

                          Compression level

                          + + +

                          Enable or not data stream compression.

                          The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                          -

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +

                          Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                          +
                          • @@ -1236,34 +1372,60 @@ file:
                          -

                          retry_interval

                          -

                          Retry interval

                          -

                          Time in seconds to wait between each connection attempt.

                          + +

                          retry_interval

                          + + +

                          Retry interval

                          + + +

                          Time in seconds to wait between each connection attempt.

                          +
                          -

                          max_size

                          -

                          Maximum size of file

                          -

                          Maximum size in bytes.

                          + +

                          max_size

                          + + +

                          Maximum size of file

                          + + +

                          Maximum size in bytes.

                          +
                          -

                          path

                          -

                          File path

                          -

                          Path to the file.

                          + +

                          path

                          + + +

                          File path

                          + + +

                          Path to the file.

                          +
                          -

                          protocol

                          -

                          Serialization protocol

                          -

                          Serialization protocol.

                          -

                          ndo

                          + +

                          protocol

                          + + +

                          Serialization protocol

                          + + +

                          Serialization protocol.

                          + + +

                          ndo

                          + @@ -1283,50 +1445,88 @@ file: -

                          config

                          -

                          Configuration messages

                          -

                          Enable or not configuration messages logging.

                          + +

                          config

                          + + +

                          Configuration messages

                          + + +

                          Enable or not configuration messages logging.

                          +
                          -

                          debug

                          -

                          Debug messages

                          -

                          Enable or not debug messages logging.

                          + +

                          debug

                          + + +

                          Debug messages

                          + + +

                          Enable or not debug messages logging.

                          +
                          -

                          error

                          -

                          Error messages

                          -

                          Enable or not error messages logging.

                          + +

                          error

                          + + +

                          Error messages

                          + + +

                          Enable or not error messages logging.

                          +
                          -

                          info

                          -

                          Informational messages

                          -

                          Enable or not informational messages logging.

                          + +

                          info

                          + + +

                          Informational messages

                          + + +

                          Enable or not informational messages logging.

                          +
                          -

                          level

                          -

                          Logging level

                          -

                          How much messages must be logged.

                          -

                          high,low,medium

                          + +

                          level

                          + + +

                          Logging level

                          + + +

                          How much messages must be logged.

                          + + +

                          high,low,medium

                          + -

                          max_size

                          -

                          name

                          -

                          Max file size in bytes

                          -

                          Name of the logger

                          -

                          The maximum size of log file.

                          -

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          + +

                          max_size

                          +

                          name

                          + + +

                          Max file size in bytes

                          +

                          Name of the logger

                          + + +

                          The maximum size of log file.

                          +

                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                          +
                          • @@ -1348,45 +1548,76 @@ standard: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1407,42 +1638,74 @@ syslog: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            Logging level

                            -

                            How much messages must be logged.

                            -

                            high,low,medium

                            + +

                            level

                            + + +

                            Logging level

                            + + +

                            How much messages must be logged.

                            + + +

                            high,low,medium

                            + @@ -1460,45 +1723,76 @@ monitoring: -

                            config

                            -

                            Configuration messages

                            -

                            Enable or not configuration messages logging.

                            + +

                            config

                            + + +

                            Configuration messages

                            + + +

                            Enable or not configuration messages logging.

                            +
                            -

                            debug

                            -

                            Debug messages

                            -

                            Enable or not debug messages logging.

                            + +

                            debug

                            + + +

                            Debug messages

                            + + +

                            Enable or not debug messages logging.

                            +
                            -

                            error

                            -

                            Error messages

                            -

                            Enable or not error messages logging.

                            + +

                            error

                            + + +

                            Error messages

                            + + +

                            Enable or not error messages logging.

                            +
                            -

                            info

                            -

                            Informational messages

                            -

                            Enable or not informational messages logging.

                            + +

                            info

                            + + +

                            Informational messages

                            + + +

                            Enable or not informational messages logging.

                            +
                            -

                            level

                            -

                            name

                            -

                            Logging level

                            -

                            Name of the logger

                            -

                            How much messages must be logged.

                            -

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            -

                            high,low,medium

                            + +

                            level

                            +

                            name

                            + + +

                            Logging level

                            +

                            Name of the logger

                            + + +

                            How much messages must be logged.

                            +

                            For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                            + + +

                            high,low,medium

                            @@ -1574,33 +1868,57 @@ rrd: -

                            buffering_timeout

                            -

                            Buffering timeout

                            -

                            Time in seconds to wait before launching failover.

                            + +

                            buffering_timeout

                            + + +

                            Buffering timeout

                            + + +

                            Time in seconds to wait before launching failover.

                            +
                            -

                            failover

                            -

                            Failover name

                            -

                            Name of the output which will act as failover

                            + +

                            failover

                            + + +

                            Failover name

                            + + +

                            Name of the output which will act as failover

                            +
                            -

                            retry_interval

                            -

                            Retry interval

                            -

                            Time in seconds to wait between each connection attempt.

                            + +

                            retry_interval

                            + + +

                            Retry interval

                            + + +

                            Time in seconds to wait between each connection attempt.

                            +
                            -

                            category

                            -

                            Filter category

                            -

                            Category filter for flux in output.

                            + +

                            category

                            + + +

                            Filter category

                            + + +

                            Category filter for flux in output.

                            +
                            • @@ -1608,15 +1926,21 @@ rrd:
                            -

                            metrics_path

                            + +

                            metrics_path

                            path

                            -

                            port

                            -

                            RRD file directory for metrics

                            +

                            port

                            + + +

                            RRD file directory for metrics

                            Unix socket

                            -

                            TCP port

                            -

                            RRD file directory, for example /var/lib/centreon/metrics

                            +

                            TCP port

                            + + +

                            RRD file directory, for example /var/lib/centreon/metrics

                            The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            -

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +

                            The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                            +
                            • @@ -1624,33 +1948,57 @@ rrd:
                            -

                            status_path

                            -

                            RRD file directory for statuses

                            -

                            RRD file directory, for example /var/lib/centreon/status

                            + +

                            status_path

                            + + +

                            RRD file directory for statuses

                            + + +

                            RRD file directory, for example /var/lib/centreon/status

                            +
                            -

                            write_metrics

                            -

                            Enable write_metrics

                            -

                            Enable or not write_metrics.

                            + +

                            write_metrics

                            + + +

                            Enable write_metrics

                            + + +

                            Enable or not write_metrics.

                            +
                            -

                            write_status

                            -

                            Enable write_status

                            -

                            Enable or not write_status.

                            + +

                            write_status

                            + + +

                            Enable write_status

                            + + +

                            Enable or not write_status.

                            +
                            -

                            store_in_data_bin

                            -

                            Enable store_in_data_bin

                            -

                            Enable or not the storage of performance data in 'data_bin'

                            + +

                            store_in_data_bin

                            + + +

                            Enable store_in_data_bin

                            + + +

                            Enable or not the storage of performance data in 'data_bin'

                            +
                            • @@ -1673,36 +2021,60 @@ storage: -

                              buffering_timeout

                              -

                              Buffering timeout

                              -

                              Time in seconds to wait before launching failover.

                              + +

                              buffering_timeout

                              + + +

                              Buffering timeout

                              + + +

                              Time in seconds to wait before launching failover.

                              +
                              -

                              failover

                              -

                              Failover name

                              -

                              Name of the output which will act as failover

                              + +

                              failover

                              + + +

                              Failover name

                              + + +

                              Name of the output which will act as failover

                              +
                              -

                              retry_interval

                              -

                              Retry interval

                              -

                              Time in seconds to wait between each connection attempt.

                              + +

                              retry_interval

                              + + +

                              Retry interval

                              + + +

                              Time in seconds to wait between each connection attempt.

                              +
                              -

                              category

                              -

                              check_replication

                              -

                              Filter category

                              -

                              Replication enabled

                              -

                              Category filter for flux in output.

                              -

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              + +

                              category

                              +

                              check_replication

                              + + +

                              Filter category

                              +

                              Replication enabled

                              + + +

                              Category filter for flux in output.

                              +

                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                              +
                              • @@ -1713,91 +2085,159 @@ storage:
                              -

                              db_host

                              -

                              DB host

                              -

                              IP address or hostname of the database server.

                              + +

                              db_host

                              + + +

                              DB host

                              + + +

                              IP address or hostname of the database server.

                              +
                              -

                              db_name

                              -

                              DB name

                              -

                              Database name.

                              + +

                              db_name

                              + + +

                              DB name

                              + + +

                              Database name.

                              +
                              -

                              db_password

                              -

                              DB password

                              -

                              Password of database user.

                              + +

                              db_password

                              + + +

                              DB password

                              + + +

                              Password of database user.

                              +
                              -

                              db_port

                              -

                              DB port

                              -

                              Port on which the DB server listens

                              + +

                              db_port

                              + + +

                              DB port

                              + + +

                              Port on which the DB server listens

                              +
                              -

                              db_type

                              -

                              DB type

                              -

                              Target DBMS.

                              -

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + +

                              db_type

                              + + +

                              DB type

                              + + +

                              Target DBMS.

                              + + +

                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                              + -

                              db_user

                              -

                              DB user

                              -

                              Database user.

                              + +

                              db_user

                              + + +

                              DB user

                              + + +

                              Database user.

                              +
                              -

                              interval

                              -

                              Interval length

                              -

                              Interval length in seconds.

                              + +

                              interval

                              + + +

                              Interval length

                              + + +

                              Interval length in seconds.

                              +
                              -

                              length

                              -

                              RRD length

                              -

                              RRD storage duration in seconds.

                              + +

                              length

                              + + +

                              RRD length

                              + + +

                              RRD storage duration in seconds.

                              +
                              -

                              queries_per_transaction

                              -

                              Maximum queries per transaction

                              -

                              The maximum queries per transaction before commit.

                              + +

                              queries_per_transaction

                              + + +

                              Maximum queries per transaction

                              + + +

                              The maximum queries per transaction before commit.

                              +
                              -

                              read_timeout

                              -

                              rebuild_check_interval

                              -

                              Transaction commit timeout

                              -

                              Rebuild check interval in seconds

                              -

                              The transaction timeout before running commit.

                              -

                              The interval between checks if some metrics must be rebuilt. The default value is 300s.

                              + +

                              read_timeout

                              +

                              rebuild_check_interval

                              + + +

                              Transaction commit timeout

                              +

                              Rebuild check interval in seconds

                              + + +

                              The transaction timeout before running commit.

                              +

                              The interval between checks if some metrics must be rebuilt. The default value is 300s.

                              +
                              -

                              store_in_data_bin

                              -

                              Enable store_in_data_bin

                              -

                              Enable or not the storage of performance data in 'data_bin.

                              + +

                              store_in_data_bin

                              + + +

                              Enable store_in_data_bin

                              + + +

                              Enable or not the storage of performance data in 'data_bin.

                              +
                              • @@ -1820,36 +2260,60 @@ sql: -

                                buffering_timeout

                                -

                                Buffering timeout

                                -

                                Time in seconds to wait before launching failover.

                                + +

                                buffering_timeout

                                + + +

                                Buffering timeout

                                + + +

                                Time in seconds to wait before launching failover.

                                +
                                -

                                failover

                                -

                                Failover name

                                -

                                Name of the output which will act as failover

                                + +

                                failover

                                + + +

                                Failover name

                                + + +

                                Name of the output which will act as failover

                                +
                                -

                                retry_interval

                                -

                                Retry interval

                                -

                                Time in seconds to wait between each connection attempt.

                                + +

                                retry_interval

                                + + +

                                Retry interval

                                + + +

                                Time in seconds to wait between each connection attempt.

                                +
                                -

                                category

                                -

                                check_replication

                                -

                                Filter category

                                -

                                Replication enabled

                                -

                                Category filter for flux in output.

                                -

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                + +

                                category

                                +

                                check_replication

                                + + +

                                Filter category

                                +

                                Replication enabled

                                + + +

                                Category filter for flux in output.

                                +

                                When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                +
                                • @@ -1860,63 +2324,113 @@ sql:
                                -

                                db_host

                                -

                                DB host

                                -

                                IP address or hostname of the database server.

                                + +

                                db_host

                                + + +

                                DB host

                                + + +

                                IP address or hostname of the database server.

                                +
                                -

                                db_name

                                -

                                DB name

                                -

                                Database name.

                                + +

                                db_name

                                + + +

                                DB name

                                + + +

                                Database name.

                                +
                                -

                                db_password

                                -

                                DB password

                                -

                                Password of database user.

                                + +

                                db_password

                                + + +

                                DB password

                                + + +

                                Password of database user.

                                +
                                -

                                db_port

                                -

                                DB port

                                -

                                Port on which the DB server listens.

                                + +

                                db_port

                                + + +

                                DB port

                                + + +

                                Port on which the DB server listens.

                                +
                                -

                                db_type

                                -

                                DB type

                                -

                                Target DBMS.

                                -

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + +

                                db_type

                                + + +

                                DB type

                                + + +

                                Target DBMS.

                                + + +

                                db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                + -

                                db_user

                                -

                                DB user

                                -

                                Database user.

                                + +

                                db_user

                                + + +

                                DB user

                                + + +

                                Database user.

                                +
                                -

                                queries_per_transaction

                                -

                                Maximum queries per transaction

                                -

                                The maximum queries per transaction.

                                + +

                                queries_per_transaction

                                + + +

                                Maximum queries per transaction

                                + + +

                                The maximum queries per transaction.

                                +
                                -

                                read_timeout

                                -

                                Transaction commit timeout

                                -

                                Timeout delay for a transaction.

                                + +

                                read_timeout

                                + + +

                                Transaction commit timeout

                                + + +

                                Timeout delay for a transaction.

                                +
                                diff --git a/versioned_docs/version-23.10/api/graph-views-api.md b/versioned_docs/version-23.10/api/graph-views-api.md index b4461c3074c2..fa5004fb1448 100644 --- a/versioned_docs/version-23.10/api/graph-views-api.md +++ b/versioned_docs/version-23.10/api/graph-views-api.md @@ -48,14 +48,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token); you'll need to +In the result, retrieve the \{studio-session\} (token); you'll need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -69,7 +69,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -77,7 +77,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/versioned_docs/version-23.10/api/graph-views-map-api.md b/versioned_docs/version-23.10/api/graph-views-map-api.md index f67e6c01ce51..63ec13dff0e8 100644 --- a/versioned_docs/version-23.10/api/graph-views-map-api.md +++ b/versioned_docs/version-23.10/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 23.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 23.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-23.10/api/rest-api-v1.md b/versioned_docs/version-23.10/api/rest-api-v1.md index 8feb29d1bd54..004ca96670c2 100644 --- a/versioned_docs/version-23.10/api/rest-api-v1.md +++ b/versioned_docs/version-23.10/api/rest-api-v1.md @@ -2483,8 +2483,8 @@ Use the GET method and URL below: : Additional information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-23.10/api/rest-api-v2.md b/versioned_docs/version-23.10/api/rest-api-v2.md index 40629d1ae2f2..003283864ea9 100644 --- a/versioned_docs/version-23.10/api/rest-api-v2.md +++ b/versioned_docs/version-23.10/api/rest-api-v2.md @@ -66,12 +66,12 @@ Then click **Add**, and select it in the environments list. > > Here is an example of output for this command: > -> { +> \{ > "version": "23.10.6", > "major": "23", > "minor": "10", > "fix": "6" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/versioned_docs/version-23.10/connect/openid.md b/versioned_docs/version-23.10/connect/openid.md index da5d81f851d9..154b67c59e9d 100644 --- a/versioned_docs/version-23.10/connect/openid.md +++ b/versioned_docs/version-23.10/connect/openid.md @@ -213,8 +213,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -225,7 +225,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -233,8 +233,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -245,7 +245,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -253,8 +253,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -273,8 +273,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-23.10/connect/saml.md b/versioned_docs/version-23.10/connect/saml.md index 58c8d09d9239..ea855ff01bb3 100644 --- a/versioned_docs/version-23.10/connect/saml.md +++ b/versioned_docs/version-23.10/connect/saml.md @@ -127,6 +127,6 @@ users. Here is an example of fields you may have to fill in: | IdP option | Centreon value | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https:/\ | +| Assertion Consumer Service (ACS) URL | https:/\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https:/\/centreon/api/latest/saml/sls | diff --git a/versioned_docs/version-23.10/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-23.10/developer/developer-gorgone-client-server-communication.md index 084ede67e0cf..f670faf9efeb 100644 --- a/versioned_docs/version-23.10/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-23.10/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-23.10/developer/developer-translate-centreon.md b/versioned_docs/version-23.10/developer/developer-translate-centreon.md index a8de0b9eb110..7c14c667d6bc 100644 --- a/versioned_docs/version-23.10/developer/developer-translate-centreon.md +++ b/versioned_docs/version-23.10/developer/developer-translate-centreon.md @@ -143,7 +143,7 @@ will allow all users of Centreon to have access to your translation on their Cen * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-23.10/developer/developer-widget.md b/versioned_docs/version-23.10/developer/developer-widget.md index 3823b9fa8130..f433352049e7 100644 --- a/versioned_docs/version-23.10/developer/developer-widget.md +++ b/versioned_docs/version-23.10/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They must be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-23.10/graph-views/install.md b/versioned_docs/version-23.10/graph-views/install.md index d739f6b1baa3..32e136bfdab8 100644 --- a/versioned_docs/version-23.10/graph-views/install.md +++ b/versioned_docs/version-23.10/graph-views/install.md @@ -152,7 +152,7 @@ default value. Modify the following file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-23.10/graph-views/troubleshooter.md b/versioned_docs/version-23.10/graph-views/troubleshooter.md index 18f04c63132f..3b1d07c406a2 100644 --- a/versioned_docs/version-23.10/graph-views/troubleshooter.md +++ b/versioned_docs/version-23.10/graph-views/troubleshooter.md @@ -157,7 +157,7 @@ To open the appropriate ports: /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Replace by the port your Centreon MAP server is using (mostly 8080 or +> Replace \ by the port your Centreon MAP server is using (mostly 8080 or > 8443 if you have configured it in SSL). To simply disable your firewall, execute: @@ -285,7 +285,7 @@ specify a new one to your desktop client. To do so, edit the file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -371,7 +371,7 @@ is working hard, your desktop client requires more memory. ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-23.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-23.10/installation/installation-of-a-central-server/using-packages.md index 6129e00f7506..c614a65314c8 100644 --- a/versioned_docs/version-23.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-23.10/installation/installation-of-a-central-server/using-packages.md @@ -542,9 +542,9 @@ GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTION FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** with the user's credentials. +> Replace **\** and **\** with the user's credentials. This user will only be used for the installation process; once the [web installation](../web-and-post-installation.md) is complete you can delete this user using: diff --git a/versioned_docs/version-23.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-23.10/installation/installation-of-a-poller/using-packages.md index 311858f513c5..ed2fc54195a9 100644 --- a/versioned_docs/version-23.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-23.10/installation/installation-of-a-poller/using-packages.md @@ -395,9 +395,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -448,19 +448,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2023-05-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2023-05-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2023-05-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md index 841aa49fcf3f..e9a1f75f9303 100644 --- a/versioned_docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-23.10/installation/installation-of-a-remote-server/using-packages.md @@ -532,9 +532,9 @@ GRANT ALL PRIVILEGES ON *.* TO ''@'' WITH GRANT OPTION; FLUSH PRIVILEGES; ``` -> Replace **** with the Centreon Central IP address that will connect to the database server. +> Replace **\** with the Centreon Central IP address that will connect to the database server. > -> Replace **** and **** with the user's credentials. +> Replace **\** and **\** with the user's credentials. This user will only be used for the installation process. Once the [web installation](../web-and-post-installation.md) is complete, you can delete this user using: @@ -756,7 +756,7 @@ To transform the server into a Remote Server and to register it to the Central s ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -765,12 +765,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the central server, as seen by the remote server. +> Replace **\** with the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -847,19 +847,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.10/installation/prerequisites.md b/versioned_docs/version-23.10/installation/prerequisites.md index 461c4c1efa83..6197026208dd 100644 --- a/versioned_docs/version-23.10/installation/prerequisites.md +++ b/versioned_docs/version-23.10/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                If you perform backups, use the following characteristics:

                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually

                                | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                If you perform backups, use the following characteristics:
                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually
                                | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                If you perform backups, use the following characteristics:

                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually

                                | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                If you perform backups, use the following characteristics:
                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually
                                | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                If you perform backups, use the following characteristics:

                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually

                                | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                If you perform backups, use the following characteristics:
                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually
                                | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                If you perform backups, use the following characteristics:

                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually

                                | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                If you perform backups, use the following characteristics:
                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually
                                | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                If you perform backups, use the following characteristics:

                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually

                                | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                If you perform backups, use the following characteristics:
                                • size of the /var/lib/mysql partition * 0,6
                                • this size is meant for 1 full backup and 6 partial ones
                                • this is only an estimate, size should be checked manually
                                | **Database server** diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-clickhouse.md index 2a675700f2d2..04b06eba517c 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-events.md index 0b0aa67e9b2b..27015e24557c 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-events.md @@ -147,7 +147,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md index 4ff3ba57e949..98025e94b41f 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-datadog-metrics.md @@ -150,7 +150,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-logstash-events.md index 026cf08becce..7b01f25b947d 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-logstash-events.md @@ -175,9 +175,9 @@ If you want to test that events are sent to Logstash correctly: 2. Run the following command: ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -> Replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +> Replace all the *``* inside the above command with their appropriate value. \* may become *8080*. 3. Check that the data has been received by Logstash. diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-events.md index 2d0f5f4db5fe..1af1e4ab60fd 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md index 6b1209efb93a..a29dcb6fb7c5 100644 --- a/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-23.10/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-23.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-23.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md index 6099d18a2253..f2323c603921 100644 --- a/versioned_docs/version-23.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-23.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-23.10/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-23.10/integrations/event-management/sc-opsgenie.md index 11ca4f35304c..ec0f6c5c437e 100644 --- a/versioned_docs/version-23.10/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-23.10/integrations/event-management/sc-opsgenie.md @@ -139,10 +139,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -186,7 +186,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg:\{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg:\{last_update\} is a timestamp macro. You can use\{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-23.10/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-23.10/integrations/event-management/sc-pagerduty-events.md index 252ed7d62adb..85f6f45e7df2 100644 --- a/versioned_docs/version-23.10/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-23.10/integrations/event-management/sc-pagerduty-events.md @@ -196,7 +196,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-23.10/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-23.10/integrations/itsm/ot-bmc-remedy.md index 5f3575f52783..2fdd808fbf8b 100644 --- a/versioned_docs/version-23.10/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-23.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-23.10/integrations/itsm/ot-mail.md b/versioned_docs/version-23.10/integrations/itsm/ot-mail.md index c1cebed25eb4..8d19670732b5 100644 --- a/versioned_docs/version-23.10/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-23.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.emai\l} | | To | | ## Possibilities diff --git a/versioned_docs/version-23.10/integrations/itsm/ot-serena.md b/versioned_docs/version-23.10/integrations/itsm/ot-serena.md index c8baea432be2..1d7f5c60419b 100644 --- a/versioned_docs/version-23.10/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-23.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-23.10/integrations/notifications/plugin-telegram.md b/versioned_docs/version-23.10/integrations/notifications/plugin-telegram.md index d218e24bd569..4feb052f61e6 100644 --- a/versioned_docs/version-23.10/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-23.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-23.10/integrations/stream-connectors.md b/versioned_docs/version-23.10/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-23.10/integrations/stream-connectors.md +++ b/versioned_docs/version-23.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-23.10/metrology/grafana.md b/versioned_docs/version-23.10/metrology/grafana.md index d50dc5bdb5c6..8f36593eee09 100644 --- a/versioned_docs/version-23.10/metrology/grafana.md +++ b/versioned_docs/version-23.10/metrology/grafana.md @@ -86,5 +86,5 @@ Use [variables](https://grafana.com/docs/grafana/latest/variables/) to select a You can customize how the labels for the curves are displayed: go to **Time Series > Standard options**, then use [the **Display name** field](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* For instance, if you enter **${__field.labels}**, the label includes all possible label customizations (host, service, metric_name). -* If you enter **${__field.labels.host}: ${__field.labels.metric_name}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. +* For instance, if you enter **$\{__field.labels\}**, the label includes all possible label customizations (host, service, metric_name). +* If you enter **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. diff --git a/versioned_docs/version-23.10/migrate/migrate-from-3-4.md b/versioned_docs/version-23.10/migrate/migrate-from-3-4.md index 3918903fd02f..bb088c1aba62 100644 --- a/versioned_docs/version-23.10/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-23.10/migrate/migrate-from-3-4.md @@ -2,6 +2,8 @@ id: migrate-from-3-4 title: Migrate from a Centreon 3.4 platform --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Prerequisites @@ -77,7 +79,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Retrieve databases @@ -147,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-23.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-23.10/migrate/migrate-from-el-to-debian.md index 061f26cb88da..11e8372476ce 100644 --- a/versioned_docs/version-23.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-23.10/migrate/migrate-from-el-to-debian.md @@ -65,7 +65,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -149,7 +149,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-23.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-23.10/migrate/migrate-from-el-to-el.md index d43989cbf5b3..9178c984e787 100644 --- a/versioned_docs/version-23.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-23.10/migrate/migrate-from-el-to-el.md @@ -85,7 +85,7 @@ apt update rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -156,7 +156,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-23.10/migrate/nagios-to-centreon.md b/versioned_docs/version-23.10/migrate/nagios-to-centreon.md index 0be2bdc7c1f2..619eae4535e9 100644 --- a/versioned_docs/version-23.10/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-23.10/migrate/nagios-to-centreon.md @@ -105,4 +105,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** with the password of the **admin** Centreon web user. +Replace **\** with the password of the **admin** Centreon web user. diff --git a/versioned_docs/version-23.10/migrate/poller-display-to-remote-server.md b/versioned_docs/version-23.10/migrate/poller-display-to-remote-server.md index 17c2e70d4655..539152e1cb93 100644 --- a/versioned_docs/version-23.10/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-23.10/migrate/poller-display-to-remote-server.md @@ -47,7 +47,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -56,12 +56,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the Centreon server seen by the Remote Server. +> Replace **\** with the IP of the Centreon server seen by the Remote Server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -138,19 +138,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed to connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 46015124a51b..c36801d47755 100644 --- a/versioned_docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-23.10/monitoring/monitoring-servers/communications.md b/versioned_docs/version-23.10/monitoring/monitoring-servers/communications.md index 4e2b74a753c7..636c4dd62f2d 100644 --- a/versioned_docs/version-23.10/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-23.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc., and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow retrieval of the remote's thumbprint, therefore it is > not possible to display the poller's Gorgone configuration from the Centreon UI. diff --git a/versioned_docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 45254a509b20..c140688115e1 100644 --- a/versioned_docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go to **Configuration > SNMP traps > SNMP traps** and click **Add** > It is possible to construct the output message yourself. To do this, use the MIB to find out the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by an OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked, the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-23.10/releases/centreon-commercial-extensions.mdx b/versioned_docs/version-23.10/releases/centreon-commercial-extensions.mdx index b48537babe43..d7de07711a10 100644 --- a/versioned_docs/version-23.10/releases/centreon-commercial-extensions.mdx +++ b/versioned_docs/version-23.10/releases/centreon-commercial-extensions.mdx @@ -771,7 +771,7 @@ Release date: `July 4, 2024` - [Anomaly Detection] Improved ergonomics by displaying the entire window with a default screen resolution, making all buttons visible. - [Packaging] Added missing dependencies on anomaly detection. - [Packaging] Anomaly_detection perl script is now correctly deployed on Debian. -- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%{perl_vendorlib}/centreon**. +- [Packaging] Various anomaly detection perl installation scripts are now deployed on **/usr/share/perl5/centreon/anomalydetection** instead of **/%\{perl_vendorlib\}/centreon**. diff --git a/versioned_docs/version-23.10/reporting/report-development.md b/versioned_docs/version-23.10/reporting/report-development.md index 6c08fd1ee83b..1d58d6aac3d7 100644 --- a/versioned_docs/version-23.10/reporting/report-development.md +++ b/versioned_docs/version-23.10/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-23.10/reporting/reports-publication-rule.md b/versioned_docs/version-23.10/reporting/reports-publication-rule.md index c1d6ec23a15c..b11b0d76daab 100644 --- a/versioned_docs/version-23.10/reporting/reports-publication-rule.md +++ b/versioned_docs/version-23.10/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Report publication rules {#publication_rules} +Report publication rules \{#publication_rules\} ========================= The \"Reporting \> Business Intelligence \> Publication rules\” menu @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_docs/version-24.04/administration/logging-configuration-changes.md b/versioned_docs/version-24.04/administration/logging-configuration-changes.md index 2e13b45e3076..32ed0c77f04f 100644 --- a/versioned_docs/version-24.04/administration/logging-configuration-changes.md +++ b/versioned_docs/version-24.04/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table: Modification type -

                                Contains the type of action applied. There are several possible types of action:

                                + +

                                Contains the type of action applied. There are several possible types of action:

                                • Added: Indicates that the object has been added
                                • Changed: Indicates that the object has been changed
                                  • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                                  The last column describes the change itself :

                                  + +

                                  The last column describes the change itself :

                                  • Field name: Describes the field that has been changed
                                  • Before: Indicates the previous value
                                    • diff --git a/versioned_docs/version-24.04/administration/parameters/ldap.md b/versioned_docs/version-24.04/administration/parameters/ldap.md index 769c7622b8df..9b75c0fa6a90 100644 --- a/versioned_docs/version-24.04/administration/parameters/ldap.md +++ b/versioned_docs/version-24.04/administration/parameters/ldap.md @@ -98,6 +98,6 @@ on the MS Active Directory, Okta, or Posix-type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for the **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for the **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for the **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for the **Search group > base DN** field. \ No newline at end of file diff --git a/versioned_docs/version-24.04/administration/secure-platform.md b/versioned_docs/version-24.04/administration/secure-platform.md index 711e715ba88f..9cf1812e9298 100644 --- a/versioned_docs/version-24.04/administration/secure-platform.md +++ b/versioned_docs/version-24.04/administration/secure-platform.md @@ -784,17 +784,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-24.04/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-24.04/alerts-notifications/notif-config-for-teams.md index 1e9dc17c42c0..cc38fc691b69 100644 --- a/versioned_docs/version-24.04/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-24.04/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-24.04/alerts-notifications/resources-status.md b/versioned_docs/version-24.04/alerts-notifications/resources-status.md index 4311d9fa8bae..e3facb4454f8 100644 --- a/versioned_docs/version-24.04/alerts-notifications/resources-status.md +++ b/versioned_docs/version-24.04/alerts-notifications/resources-status.md @@ -293,7 +293,7 @@ Graphs display metric evolution over a given period. This can be defined in the - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Whenever the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-24.04/alerts-notifications/ticketing.md b/versioned_docs/version-24.04/alerts-notifications/ticketing.md index 3d41997a6d69..4b4c97827b3b 100644 --- a/versioned_docs/version-24.04/alerts-notifications/ticketing.md +++ b/versioned_docs/version-24.04/alerts-notifications/ticketing.md @@ -138,9 +138,9 @@ The module stores the user list selection in an array (can be used in a smart section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-24.04/api/clapi.md b/versioned_docs/version-24.04/api/clapi.md index 6ac33a300fe9..a82a2ad0ec53 100644 --- a/versioned_docs/version-24.04/api/clapi.md +++ b/versioned_docs/version-24.04/api/clapi.md @@ -573,13 +573,13 @@ Let's assume that you would like to grant full access to the \[Monitoring\] menu centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Monitoring" ``` -Then you would like to grant access to the \[Home\] \> \[Poller statistics\] menu: +Then you would like to grant access to the \[Home\] > \[Poller statistics\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Home;Poller statistics" ``` -Then you would like to grant read-only access to the \[Configuration\] \> \[Hosts\] menu: +Then you would like to grant read-only access to the \[Configuration\] > \[Hosts\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantro -v "ACL Menu test;1;Configuration;Hosts" @@ -994,23 +994,35 @@ ipv4: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1018,71 +1030,121 @@ ipv4:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    category

                                    -

                                    Filter category

                                    -

                                    Category filter for flux in input

                                    + +

                                    category

                                    + + +

                                    Filter category

                                    + + +

                                    Category filter for flux in input

                                    +
                                    -

                                    ca_certificate

                                    -

                                    host

                                    -

                                    Trusted CA's certificate

                                    -

                                    Host to connect to

                                    -

                                    Trusted CA's certificate.

                                    -

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    + +

                                    ca_certificate

                                    +

                                    host

                                    + + +

                                    Trusted CA's certificate

                                    +

                                    Host to connect to

                                    + + +

                                    Trusted CA's certificate.

                                    +

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    +
                                    -

                                    one_peer_retention_mode

                                    -

                                    port

                                    -

                                    One peer retention

                                    -

                                    Connection port

                                    -

                                    This allows the retention to work even if the socket is listening

                                    -

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    + +

                                    one_peer_retention_mode

                                    +

                                    port

                                    + + +

                                    One peer retention

                                    +

                                    Connection port

                                    + + +

                                    This allows the retention to work even if the socket is listening

                                    +

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    +
                                    -

                                    private_key

                                    -

                                    Private key file.

                                    -

                                    Private key file path when TLS encryption is used.

                                    + +

                                    private_key

                                    + + +

                                    Private key file.

                                    + + +

                                    Private key file path when TLS encryption is used.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + -

                                    public_cert

                                    -

                                    Public certificate

                                    -

                                    Public certificate file path when TLS encryption is used.

                                    + +

                                    public_cert

                                    + + +

                                    Public certificate

                                    + + +

                                    Public certificate file path when TLS encryption is used.

                                    +
                                    -

                                    tls

                                    -

                                    Enable TLS encryption

                                    -

                                    Enable TLS encryption.

                                    + +

                                    tls

                                    + + +

                                    Enable TLS encryption

                                    + + +

                                    Enable TLS encryption.

                                    +
                                    @@ -1103,23 +1165,35 @@ ipv6: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1127,71 +1201,121 @@ ipv6:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    category

                                    -

                                    Filter category

                                    -

                                    Category filter for flux in input

                                    + +

                                    category

                                    + + +

                                    Filter category

                                    + + +

                                    Category filter for flux in input

                                    +
                                    -

                                    ca_certificate

                                    -

                                    host

                                    -

                                    Trusted CA's certificate

                                    -

                                    Host to connect to

                                    -

                                    Trusted CA's certificate.

                                    -

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    + +

                                    ca_certificate

                                    +

                                    host

                                    + + +

                                    Trusted CA's certificate

                                    +

                                    Host to connect to

                                    + + +

                                    Trusted CA's certificate.

                                    +

                                    IP address or hostname of the host to connect to (leave blank for listening mode).

                                    +
                                    -

                                    one_peer_retention_mode

                                    -

                                    port

                                    -

                                    One peer retention

                                    -

                                    Connection port

                                    -

                                    This allows the retention to work even if the socket is listening

                                    -

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    + +

                                    one_peer_retention_mode

                                    +

                                    port

                                    + + +

                                    One peer retention

                                    +

                                    Connection port

                                    + + +

                                    This allows the retention to work even if the socket is listening

                                    +

                                    Port to listen on (empty host) or to connect to (with host filled).

                                    +
                                    -

                                    private_key

                                    -

                                    Private key file.

                                    -

                                    Private key file path when TLS encryption is used.

                                    + +

                                    private_key

                                    + + +

                                    Private key file.

                                    + + +

                                    Private key file path when TLS encryption is used.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + -

                                    public_cert

                                    -

                                    Public certificate

                                    -

                                    Public certificate file path when TLS encryption is used.

                                    + +

                                    public_cert

                                    + + +

                                    Public certificate

                                    + + +

                                    Public certificate file path when TLS encryption is used.

                                    +
                                    -

                                    tls

                                    -

                                    Enable TLS encryption

                                    -

                                    Enable TLS encryption.

                                    + +

                                    tls

                                    + + +

                                    Enable TLS encryption

                                    + + +

                                    Enable TLS encryption.

                                    +
                                    @@ -1212,23 +1336,35 @@ file: -

                                    buffering_timeout

                                    -

                                    Buffering timeout

                                    -

                                    Time in seconds to wait before launching failover.

                                    + +

                                    buffering_timeout

                                    + + +

                                    Buffering timeout

                                    + + +

                                    Time in seconds to wait before launching failover.

                                    +
                                    -

                                    compression

                                    + +

                                    compression

                                    compression_buffer

                                    -

                                    compression_level

                                    -

                                    Compression (zlib)

                                    +

                                    compression_level

                                    + + +

                                    Compression (zlib)

                                    Compression buffer size

                                    -

                                    Compression level

                                    -

                                    Enable or not data stream compression.

                                    +

                                    Compression level

                                    + + +

                                    Enable or not data stream compression.

                                    The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                    -

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +

                                    Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                    +
                                    • @@ -1236,34 +1372,60 @@ file:
                                    -

                                    retry_interval

                                    -

                                    Retry interval

                                    -

                                    Time in seconds to wait between each connection attempt.

                                    + +

                                    retry_interval

                                    + + +

                                    Retry interval

                                    + + +

                                    Time in seconds to wait between each connection attempt.

                                    +
                                    -

                                    max_size

                                    -

                                    Maximum size of file

                                    -

                                    Maximum size in bytes.

                                    + +

                                    max_size

                                    + + +

                                    Maximum size of file

                                    + + +

                                    Maximum size in bytes.

                                    +
                                    -

                                    path

                                    -

                                    File path

                                    -

                                    Path to the file.

                                    + +

                                    path

                                    + + +

                                    File path

                                    + + +

                                    Path to the file.

                                    +
                                    -

                                    protocol

                                    -

                                    Serialization protocol

                                    -

                                    Serialization protocol.

                                    -

                                    ndo

                                    + +

                                    protocol

                                    + + +

                                    Serialization protocol

                                    + + +

                                    Serialization protocol.

                                    + + +

                                    ndo

                                    + @@ -1283,50 +1445,88 @@ file: -

                                    config

                                    -

                                    Configuration messages

                                    -

                                    Enable or not configuration messages logging.

                                    + +

                                    config

                                    + + +

                                    Configuration messages

                                    + + +

                                    Enable or not configuration messages logging.

                                    +
                                    -

                                    debug

                                    -

                                    Debug messages

                                    -

                                    Enable or not debug messages logging.

                                    + +

                                    debug

                                    + + +

                                    Debug messages

                                    + + +

                                    Enable or not debug messages logging.

                                    +
                                    -

                                    error

                                    -

                                    Error messages

                                    -

                                    Enable or not error messages logging.

                                    + +

                                    error

                                    + + +

                                    Error messages

                                    + + +

                                    Enable or not error messages logging.

                                    +
                                    -

                                    info

                                    -

                                    Informational messages

                                    -

                                    Enable or not informational messages logging.

                                    + +

                                    info

                                    + + +

                                    Informational messages

                                    + + +

                                    Enable or not informational messages logging.

                                    +
                                    -

                                    level

                                    -

                                    Logging level

                                    -

                                    How much messages must be logged.

                                    -

                                    high,low,medium

                                    + +

                                    level

                                    + + +

                                    Logging level

                                    + + +

                                    How much messages must be logged.

                                    + + +

                                    high,low,medium

                                    + -

                                    max_size

                                    -

                                    name

                                    -

                                    Max file size in bytes

                                    -

                                    Name of the logger

                                    -

                                    The maximum size of log file.

                                    -

                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                    + +

                                    max_size

                                    +

                                    name

                                    + + +

                                    Max file size in bytes

                                    +

                                    Name of the logger

                                    + + +

                                    The maximum size of log file.

                                    +

                                    For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                    +
                                    • @@ -1348,45 +1548,76 @@ standard: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      name

                                      -

                                      Logging level

                                      -

                                      Name of the logger

                                      -

                                      How much messages must be logged.

                                      -

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      +

                                      name

                                      + + +

                                      Logging level

                                      +

                                      Name of the logger

                                      + + +

                                      How much messages must be logged.

                                      +

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      + + +

                                      high,low,medium

                                      @@ -1407,42 +1638,74 @@ syslog: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      Logging level

                                      -

                                      How much messages must be logged.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      + + +

                                      Logging level

                                      + + +

                                      How much messages must be logged.

                                      + + +

                                      high,low,medium

                                      + @@ -1460,45 +1723,76 @@ monitoring: -

                                      config

                                      -

                                      Configuration messages

                                      -

                                      Enable or not configuration messages logging.

                                      + +

                                      config

                                      + + +

                                      Configuration messages

                                      + + +

                                      Enable or not configuration messages logging.

                                      +
                                      -

                                      debug

                                      -

                                      Debug messages

                                      -

                                      Enable or not debug messages logging.

                                      + +

                                      debug

                                      + + +

                                      Debug messages

                                      + + +

                                      Enable or not debug messages logging.

                                      +
                                      -

                                      error

                                      -

                                      Error messages

                                      -

                                      Enable or not error messages logging.

                                      + +

                                      error

                                      + + +

                                      Error messages

                                      + + +

                                      Enable or not error messages logging.

                                      +
                                      -

                                      info

                                      -

                                      Informational messages

                                      -

                                      Enable or not informational messages logging.

                                      + +

                                      info

                                      + + +

                                      Informational messages

                                      + + +

                                      Enable or not informational messages logging.

                                      +
                                      -

                                      level

                                      -

                                      name

                                      -

                                      Logging level

                                      -

                                      Name of the logger

                                      -

                                      How much messages must be logged.

                                      -

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      -

                                      high,low,medium

                                      + +

                                      level

                                      +

                                      name

                                      + + +

                                      Logging level

                                      +

                                      Name of the logger

                                      + + +

                                      How much messages must be logged.

                                      +

                                      For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                      + + +

                                      high,low,medium

                                      @@ -1574,33 +1868,57 @@ rrd: -

                                      buffering_timeout

                                      -

                                      Buffering timeout

                                      -

                                      Time in seconds to wait before launching failover.

                                      + +

                                      buffering_timeout

                                      + + +

                                      Buffering timeout

                                      + + +

                                      Time in seconds to wait before launching failover.

                                      +
                                      -

                                      failover

                                      -

                                      Failover name

                                      -

                                      Name of the output which will act as failover

                                      + +

                                      failover

                                      + + +

                                      Failover name

                                      + + +

                                      Name of the output which will act as failover

                                      +
                                      -

                                      retry_interval

                                      -

                                      Retry interval

                                      -

                                      Time in seconds to wait between each connection attempt.

                                      + +

                                      retry_interval

                                      + + +

                                      Retry interval

                                      + + +

                                      Time in seconds to wait between each connection attempt.

                                      +
                                      -

                                      category

                                      -

                                      Filter category

                                      -

                                      Category filter for flux in output.

                                      + +

                                      category

                                      + + +

                                      Filter category

                                      + + +

                                      Category filter for flux in output.

                                      +
                                      • @@ -1608,15 +1926,21 @@ rrd:
                                      -

                                      metrics_path

                                      + +

                                      metrics_path

                                      path

                                      -

                                      port

                                      -

                                      RRD file directory for metrics

                                      +

                                      port

                                      + + +

                                      RRD file directory for metrics

                                      Unix socket

                                      -

                                      TCP port

                                      -

                                      RRD file directory, for example /var/lib/centreon/metrics

                                      +

                                      TCP port

                                      + + +

                                      RRD file directory, for example /var/lib/centreon/metrics

                                      The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      -

                                      The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      +

                                      The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                      +
                                      • @@ -1624,33 +1948,57 @@ rrd:
                                      -

                                      status_path

                                      -

                                      RRD file directory for statuses

                                      -

                                      RRD file directory, for example /var/lib/centreon/status

                                      + +

                                      status_path

                                      + + +

                                      RRD file directory for statuses

                                      + + +

                                      RRD file directory, for example /var/lib/centreon/status

                                      +
                                      -

                                      write_metrics

                                      -

                                      Enable write_metrics

                                      -

                                      Enable or not write_metrics.

                                      + +

                                      write_metrics

                                      + + +

                                      Enable write_metrics

                                      + + +

                                      Enable or not write_metrics.

                                      +
                                      -

                                      write_status

                                      -

                                      Enable write_status

                                      -

                                      Enable or not write_status.

                                      + +

                                      write_status

                                      + + +

                                      Enable write_status

                                      + + +

                                      Enable or not write_status.

                                      +
                                      -

                                      store_in_data_bin

                                      -

                                      Enable store_in_data_bin

                                      -

                                      Enable or not the storage of performance data in 'data_bin'

                                      + +

                                      store_in_data_bin

                                      + + +

                                      Enable store_in_data_bin

                                      + + +

                                      Enable or not the storage of performance data in 'data_bin'

                                      +
                                      • @@ -1673,36 +2021,60 @@ storage: -

                                        buffering_timeout

                                        -

                                        Buffering timeout

                                        -

                                        Time in seconds to wait before launching failover.

                                        + +

                                        buffering_timeout

                                        + + +

                                        Buffering timeout

                                        + + +

                                        Time in seconds to wait before launching failover.

                                        +
                                        -

                                        failover

                                        -

                                        Failover name

                                        -

                                        Name of the output which will act as failover

                                        + +

                                        failover

                                        + + +

                                        Failover name

                                        + + +

                                        Name of the output which will act as failover

                                        +
                                        -

                                        retry_interval

                                        -

                                        Retry interval

                                        -

                                        Time in seconds to wait between each connection attempt.

                                        + +

                                        retry_interval

                                        + + +

                                        Retry interval

                                        + + +

                                        Time in seconds to wait between each connection attempt.

                                        +
                                        -

                                        category

                                        -

                                        check_replication

                                        -

                                        Filter category

                                        -

                                        Replication enabled

                                        -

                                        Category filter for flux in output.

                                        -

                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                        + +

                                        category

                                        +

                                        check_replication

                                        + + +

                                        Filter category

                                        +

                                        Replication enabled

                                        + + +

                                        Category filter for flux in output.

                                        +

                                        When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                        +
                                        • @@ -1713,91 +2085,159 @@ storage:
                                        -

                                        db_host

                                        -

                                        DB host

                                        -

                                        IP address or hostname of the database server.

                                        + +

                                        db_host

                                        + + +

                                        DB host

                                        + + +

                                        IP address or hostname of the database server.

                                        +
                                        -

                                        db_name

                                        -

                                        DB name

                                        -

                                        Database name.

                                        + +

                                        db_name

                                        + + +

                                        DB name

                                        + + +

                                        Database name.

                                        +
                                        -

                                        db_password

                                        -

                                        DB password

                                        -

                                        Password of database user.

                                        + +

                                        db_password

                                        + + +

                                        DB password

                                        + + +

                                        Password of database user.

                                        +
                                        -

                                        db_port

                                        -

                                        DB port

                                        -

                                        Port on which the DB server listens

                                        + +

                                        db_port

                                        + + +

                                        DB port

                                        + + +

                                        Port on which the DB server listens

                                        +
                                        -

                                        db_type

                                        -

                                        DB type

                                        -

                                        Target DBMS.

                                        -

                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                        + +

                                        db_type

                                        + + +

                                        DB type

                                        + + +

                                        Target DBMS.

                                        + + +

                                        db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                        + -

                                        db_user

                                        -

                                        DB user

                                        -

                                        Database user.

                                        + +

                                        db_user

                                        + + +

                                        DB user

                                        + + +

                                        Database user.

                                        +
                                        -

                                        interval

                                        -

                                        Interval length

                                        -

                                        Interval length in seconds.

                                        + +

                                        interval

                                        + + +

                                        Interval length

                                        + + +

                                        Interval length in seconds.

                                        +
                                        -

                                        length

                                        -

                                        RRD length

                                        -

                                        RRD storage duration in seconds.

                                        + +

                                        length

                                        + + +

                                        RRD length

                                        + + +

                                        RRD storage duration in seconds.

                                        +
                                        -

                                        queries_per_transaction

                                        -

                                        Maximum queries per transaction

                                        -

                                        The maximum queries per transaction before commit.

                                        + +

                                        queries_per_transaction

                                        + + +

                                        Maximum queries per transaction

                                        + + +

                                        The maximum queries per transaction before commit.

                                        +
                                        -

                                        read_timeout

                                        -

                                        rebuild_check_interval

                                        -

                                        Transaction commit timeout

                                        -

                                        Rebuild check interval in seconds

                                        -

                                        The transaction timeout before running commit.

                                        -

                                        The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                        + +

                                        read_timeout

                                        +

                                        rebuild_check_interval

                                        + + +

                                        Transaction commit timeout

                                        +

                                        Rebuild check interval in seconds

                                        + + +

                                        The transaction timeout before running commit.

                                        +

                                        The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                        +
                                        -

                                        store_in_data_bin

                                        -

                                        Enable store_in_data_bin

                                        -

                                        Enable or not the storage of performance data in 'data_bin.

                                        + +

                                        store_in_data_bin

                                        + + +

                                        Enable store_in_data_bin

                                        + + +

                                        Enable or not the storage of performance data in 'data_bin.

                                        +
                                        • @@ -1820,36 +2260,60 @@ sql: -

                                          buffering_timeout

                                          -

                                          Buffering timeout

                                          -

                                          Time in seconds to wait before launching failover.

                                          + +

                                          buffering_timeout

                                          + + +

                                          Buffering timeout

                                          + + +

                                          Time in seconds to wait before launching failover.

                                          +
                                          -

                                          failover

                                          -

                                          Failover name

                                          -

                                          Name of the output which will act as failover

                                          + +

                                          failover

                                          + + +

                                          Failover name

                                          + + +

                                          Name of the output which will act as failover

                                          +
                                          -

                                          retry_interval

                                          -

                                          Retry interval

                                          -

                                          Time in seconds to wait between each connection attempt.

                                          + +

                                          retry_interval

                                          + + +

                                          Retry interval

                                          + + +

                                          Time in seconds to wait between each connection attempt.

                                          +
                                          -

                                          category

                                          -

                                          check_replication

                                          -

                                          Filter category

                                          -

                                          Replication enabled

                                          -

                                          Category filter for flux in output.

                                          -

                                          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                          + +

                                          category

                                          +

                                          check_replication

                                          + + +

                                          Filter category

                                          +

                                          Replication enabled

                                          + + +

                                          Category filter for flux in output.

                                          +

                                          When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                          +
                                          • @@ -1860,63 +2324,113 @@ sql:
                                          -

                                          db_host

                                          -

                                          DB host

                                          -

                                          IP address or hostname of the database server.

                                          + +

                                          db_host

                                          + + +

                                          DB host

                                          + + +

                                          IP address or hostname of the database server.

                                          +
                                          -

                                          db_name

                                          -

                                          DB name

                                          -

                                          Database name.

                                          + +

                                          db_name

                                          + + +

                                          DB name

                                          + + +

                                          Database name.

                                          +
                                          -

                                          db_password

                                          -

                                          DB password

                                          -

                                          Password of database user.

                                          + +

                                          db_password

                                          + + +

                                          DB password

                                          + + +

                                          Password of database user.

                                          +
                                          -

                                          db_port

                                          -

                                          DB port

                                          -

                                          Port on which the DB server listens.

                                          + +

                                          db_port

                                          + + +

                                          DB port

                                          + + +

                                          Port on which the DB server listens.

                                          +
                                          -

                                          db_type

                                          -

                                          DB type

                                          -

                                          Target DBMS.

                                          -

                                          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                          + +

                                          db_type

                                          + + +

                                          DB type

                                          + + +

                                          Target DBMS.

                                          + + +

                                          db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                          + -

                                          db_user

                                          -

                                          DB user

                                          -

                                          Database user.

                                          + +

                                          db_user

                                          + + +

                                          DB user

                                          + + +

                                          Database user.

                                          +
                                          -

                                          queries_per_transaction

                                          -

                                          Maximum queries per transaction

                                          -

                                          The maximum queries per transaction.

                                          + +

                                          queries_per_transaction

                                          + + +

                                          Maximum queries per transaction

                                          + + +

                                          The maximum queries per transaction.

                                          +
                                          -

                                          read_timeout

                                          -

                                          Transaction commit timeout

                                          -

                                          Timeout delay for a transaction.

                                          + +

                                          read_timeout

                                          + + +

                                          Transaction commit timeout

                                          + + +

                                          Timeout delay for a transaction.

                                          +
                                          diff --git a/versioned_docs/version-24.04/api/graph-views-api.md b/versioned_docs/version-24.04/api/graph-views-api.md index eac1cc41487f..48cf09b2e3c7 100644 --- a/versioned_docs/version-24.04/api/graph-views-api.md +++ b/versioned_docs/version-24.04/api/graph-views-api.md @@ -48,14 +48,14 @@ Body { } ``` -In the result, retrieve the {studio-session} (token); you'll need to +In the result, retrieve the \{studio-session\} (token); you'll need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } ``` @@ -69,7 +69,7 @@ POST http://{{serverURL}}:8080/centreon-studio/api/beta/maps Headers { Content-Type = application/json X-client-version = 19.10.0 - studio-session = {studio-session} + studio-session = \{studio-session\} } Body { @@ -77,7 +77,7 @@ Body { } ``` -Retrieve the ID of the view returned: {viewId} +Retrieve the ID of the view returned: \{viewId\} **3.Open the Map** diff --git a/versioned_docs/version-24.04/api/graph-views-map-api.md b/versioned_docs/version-24.04/api/graph-views-map-api.md index 4371eef24b62..4a5c020744cb 100644 --- a/versioned_docs/version-24.04/api/graph-views-map-api.md +++ b/versioned_docs/version-24.04/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 24.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.04.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-24.04/api/rest-api-v1.md b/versioned_docs/version-24.04/api/rest-api-v1.md index bbaf0b027723..1b4290a6096e 100644 --- a/versioned_docs/version-24.04/api/rest-api-v1.md +++ b/versioned_docs/version-24.04/api/rest-api-v1.md @@ -2628,8 +2628,8 @@ Use the GET method and URL below: : Additional information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-24.04/api/rest-api-v2.md b/versioned_docs/version-24.04/api/rest-api-v2.md index 0a054f126bcb..ddac11907bba 100644 --- a/versioned_docs/version-24.04/api/rest-api-v2.md +++ b/versioned_docs/version-24.04/api/rest-api-v2.md @@ -66,12 +66,12 @@ Then click **Add**, and select it in the environments list. > > Here is an example of output for this command: > -> { +> \{ > "version": "24.04.1", > "major": "24", > "minor": "04", > "fix": "1" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/versioned_docs/version-24.04/connect/openid.md b/versioned_docs/version-24.04/connect/openid.md index da5d81f851d9..154b67c59e9d 100644 --- a/versioned_docs/version-24.04/connect/openid.md +++ b/versioned_docs/version-24.04/connect/openid.md @@ -213,8 +213,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -225,7 +225,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -233,8 +233,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -245,7 +245,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -253,8 +253,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -273,8 +273,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-24.04/connect/saml.md b/versioned_docs/version-24.04/connect/saml.md index 58c8d09d9239..ea855ff01bb3 100644 --- a/versioned_docs/version-24.04/connect/saml.md +++ b/versioned_docs/version-24.04/connect/saml.md @@ -127,6 +127,6 @@ users. Here is an example of fields you may have to fill in: | IdP option | Centreon value | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https:/\ | +| Assertion Consumer Service (ACS) URL | https:/\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https:/\/centreon/api/latest/saml/sls | diff --git a/versioned_docs/version-24.04/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-24.04/developer/developer-gorgone-client-server-communication.md index 084ede67e0cf..f670faf9efeb 100644 --- a/versioned_docs/version-24.04/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-24.04/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-24.04/developer/developer-translate-centreon.md b/versioned_docs/version-24.04/developer/developer-translate-centreon.md index a8de0b9eb110..7c14c667d6bc 100644 --- a/versioned_docs/version-24.04/developer/developer-translate-centreon.md +++ b/versioned_docs/version-24.04/developer/developer-translate-centreon.md @@ -143,7 +143,7 @@ will allow all users of Centreon to have access to your translation on their Cen * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-24.04/developer/developer-widget.md b/versioned_docs/version-24.04/developer/developer-widget.md index 3823b9fa8130..f433352049e7 100644 --- a/versioned_docs/version-24.04/developer/developer-widget.md +++ b/versioned_docs/version-24.04/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They must be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-24.04/graph-views/install.md b/versioned_docs/version-24.04/graph-views/install.md index e18365aa2bd6..74d12b0631bb 100644 --- a/versioned_docs/version-24.04/graph-views/install.md +++ b/versioned_docs/version-24.04/graph-views/install.md @@ -151,7 +151,7 @@ default value. Modify the following file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-24.04/graph-views/troubleshooter.md b/versioned_docs/version-24.04/graph-views/troubleshooter.md index 18f04c63132f..3b1d07c406a2 100644 --- a/versioned_docs/version-24.04/graph-views/troubleshooter.md +++ b/versioned_docs/version-24.04/graph-views/troubleshooter.md @@ -157,7 +157,7 @@ To open the appropriate ports: /sbin/iptables -A INPUT -p tcp --dport -j ACCEPT ``` -> Replace by the port your Centreon MAP server is using (mostly 8080 or +> Replace \ by the port your Centreon MAP server is using (mostly 8080 or > 8443 if you have configured it in SSL). To simply disable your firewall, execute: @@ -285,7 +285,7 @@ specify a new one to your desktop client. To do so, edit the file: ```shell -C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini +C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` @@ -371,7 +371,7 @@ is working hard, your desktop client requires more memory. ```shell - C:\Users\\AppData\Local\Centreon-Map4\Centreon-Map4.ini + C:\Users\AppData\Local\Centreon-Map4\Centreon-Map4.ini ``` diff --git a/versioned_docs/version-24.04/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-24.04/installation/installation-of-a-poller/using-packages.md index 8e3e82f4dd3d..27fa37987404 100644 --- a/versioned_docs/version-24.04/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-24.04/installation/installation-of-a-poller/using-packages.md @@ -392,9 +392,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -445,19 +445,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2023-05-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2023-05-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2023-05-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md index 7074dcc89d7a..76137231374b 100644 --- a/versioned_docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-24.04/installation/installation-of-a-remote-server/using-packages.md @@ -587,7 +587,7 @@ To transform the server into a Remote Server and to register it to the Central s ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -596,12 +596,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the central server, as seen by the remote server. +> Replace **\** with the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -678,19 +678,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.04/installation/prerequisites.md b/versioned_docs/version-24.04/installation/prerequisites.md index 461c4c1efa83..6197026208dd 100644 --- a/versioned_docs/version-24.04/installation/prerequisites.md +++ b/versioned_docs/version-24.04/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                          If you perform backups, use the following characteristics:

                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually

                                          | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                          If you perform backups, use the following characteristics:
                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually
                                          | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                          If you perform backups, use the following characteristics:

                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually

                                          | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                          If you perform backups, use the following characteristics:
                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually
                                          | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                          If you perform backups, use the following characteristics:

                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually

                                          | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                          If you perform backups, use the following characteristics:
                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually
                                          | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                          If you perform backups, use the following characteristics:

                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually

                                          | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                          If you perform backups, use the following characteristics:
                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually
                                          | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                          If you perform backups, use the following characteristics:

                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually

                                          | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                          If you perform backups, use the following characteristics:
                                          • size of the /var/lib/mysql partition * 0,6
                                          • this size is meant for 1 full backup and 6 partial ones
                                          • this is only an estimate, size should be checked manually
                                          | **Database server** diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-clickhouse.md index f751a6badd42..f873d336f5bf 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-events.md index 0b0aa67e9b2b..27015e24557c 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-events.md @@ -147,7 +147,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md index 4ff3ba57e949..98025e94b41f 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-datadog-metrics.md @@ -150,7 +150,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-logstash-events.md index c9b668a40cb3..63754be51156 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-logstash-events.md @@ -148,7 +148,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *8080*. diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-events.md index 2d0f5f4db5fe..1af1e4ab60fd 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md index 6b1209efb93a..a29dcb6fb7c5 100644 --- a/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-24.04/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-24.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-24.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/versioned_docs/version-24.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-24.04/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-24.04/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-24.04/integrations/event-management/sc-opsgenie.md index 11ca4f35304c..ec0f6c5c437e 100644 --- a/versioned_docs/version-24.04/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-24.04/integrations/event-management/sc-opsgenie.md @@ -139,10 +139,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -186,7 +186,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg:\{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg:\{last_update\} is a timestamp macro. You can use\{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-24.04/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-24.04/integrations/event-management/sc-pagerduty-events.md index 252ed7d62adb..85f6f45e7df2 100644 --- a/versioned_docs/version-24.04/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-24.04/integrations/event-management/sc-pagerduty-events.md @@ -196,7 +196,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-24.04/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-24.04/integrations/itsm/ot-bmc-remedy.md index 5f3575f52783..2fdd808fbf8b 100644 --- a/versioned_docs/version-24.04/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-24.04/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-24.04/integrations/itsm/ot-mail.md b/versioned_docs/version-24.04/integrations/itsm/ot-mail.md index c1cebed25eb4..8d19670732b5 100644 --- a/versioned_docs/version-24.04/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-24.04/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.emai\l} | | To | | ## Possibilities diff --git a/versioned_docs/version-24.04/integrations/itsm/ot-serena.md b/versioned_docs/version-24.04/integrations/itsm/ot-serena.md index c8baea432be2..1d7f5c60419b 100644 --- a/versioned_docs/version-24.04/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-24.04/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-24.04/integrations/notifications/plugin-telegram.md b/versioned_docs/version-24.04/integrations/notifications/plugin-telegram.md index d218e24bd569..4feb052f61e6 100644 --- a/versioned_docs/version-24.04/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-24.04/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-24.04/integrations/stream-connectors.md b/versioned_docs/version-24.04/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-24.04/integrations/stream-connectors.md +++ b/versioned_docs/version-24.04/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-24.04/metrology/grafana.md b/versioned_docs/version-24.04/metrology/grafana.md index d50dc5bdb5c6..8f36593eee09 100644 --- a/versioned_docs/version-24.04/metrology/grafana.md +++ b/versioned_docs/version-24.04/metrology/grafana.md @@ -86,5 +86,5 @@ Use [variables](https://grafana.com/docs/grafana/latest/variables/) to select a You can customize how the labels for the curves are displayed: go to **Time Series > Standard options**, then use [the **Display name** field](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* For instance, if you enter **${__field.labels}**, the label includes all possible label customizations (host, service, metric_name). -* If you enter **${__field.labels.host}: ${__field.labels.metric_name}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. +* For instance, if you enter **$\{__field.labels\}**, the label includes all possible label customizations (host, service, metric_name). +* If you enter **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. diff --git a/versioned_docs/version-24.04/migrate/migrate-from-3-4.md b/versioned_docs/version-24.04/migrate/migrate-from-3-4.md index d10d8094f84a..a6c3e0e2e30f 100644 --- a/versioned_docs/version-24.04/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-24.04/migrate/migrate-from-3-4.md @@ -2,6 +2,8 @@ id: migrate-from-3-4 title: Migrate from a Centreon 3.4 platform --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Prerequisites @@ -77,7 +79,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Retrieve databases @@ -147,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-24.04/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-24.04/migrate/migrate-from-el-to-debian.md index e00d4328638b..2ba14c61758d 100644 --- a/versioned_docs/version-24.04/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-24.04/migrate/migrate-from-el-to-debian.md @@ -65,7 +65,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -149,7 +149,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-24.04/migrate/migrate-from-el-to-el.md b/versioned_docs/version-24.04/migrate/migrate-from-el-to-el.md index 6b4b32011884..bd09a898a9d6 100644 --- a/versioned_docs/version-24.04/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-24.04/migrate/migrate-from-el-to-el.md @@ -78,7 +78,7 @@ dnf update rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -149,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-24.04/migrate/nagios-to-centreon.md b/versioned_docs/version-24.04/migrate/nagios-to-centreon.md index 2111edfe661d..76bd05d8b6c5 100644 --- a/versioned_docs/version-24.04/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-24.04/migrate/nagios-to-centreon.md @@ -105,4 +105,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** with the password of the **admin** Centreon web user. +Replace **\** with the password of the **admin** Centreon web user. diff --git a/versioned_docs/version-24.04/migrate/poller-display-to-remote-server.md b/versioned_docs/version-24.04/migrate/poller-display-to-remote-server.md index 17c2e70d4655..539152e1cb93 100644 --- a/versioned_docs/version-24.04/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-24.04/migrate/poller-display-to-remote-server.md @@ -47,7 +47,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -56,12 +56,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the Centreon server seen by the Remote Server. +> Replace **\** with the IP of the Centreon server seen by the Remote Server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -138,19 +138,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed to connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 46015124a51b..c36801d47755 100644 --- a/versioned_docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-24.04/monitoring/monitoring-servers/communications.md b/versioned_docs/version-24.04/monitoring/monitoring-servers/communications.md index e1ba4b5cba69..67a29d2c1191 100644 --- a/versioned_docs/version-24.04/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-24.04/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc., and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow retrieval of the remote's thumbprint, therefore it is > not possible to display the poller's Gorgone configuration from the Centreon UI. diff --git a/versioned_docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 45254a509b20..c140688115e1 100644 --- a/versioned_docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go to **Configuration > SNMP traps > SNMP traps** and click **Add** > It is possible to construct the output message yourself. To do this, use the MIB to find out the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by an OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked, the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-24.04/reporting/report-development.md b/versioned_docs/version-24.04/reporting/report-development.md index 74fe6b3a0f91..0daf02963849 100644 --- a/versioned_docs/version-24.04/reporting/report-development.md +++ b/versioned_docs/version-24.04/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-24.04/reporting/reports-publication-rule.md b/versioned_docs/version-24.04/reporting/reports-publication-rule.md index c1d6ec23a15c..b11b0d76daab 100644 --- a/versioned_docs/version-24.04/reporting/reports-publication-rule.md +++ b/versioned_docs/version-24.04/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Report publication rules {#publication_rules} +Report publication rules \{#publication_rules\} ========================= The \"Reporting \> Business Intelligence \> Publication rules\” menu @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_docs/version-24.10/administration/logging-configuration-changes.md b/versioned_docs/version-24.10/administration/logging-configuration-changes.md index 2e13b45e3076..32ed0c77f04f 100644 --- a/versioned_docs/version-24.10/administration/logging-configuration-changes.md +++ b/versioned_docs/version-24.10/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table: Modification type -

                                          Contains the type of action applied. There are several possible types of action:

                                          + +

                                          Contains the type of action applied. There are several possible types of action:

                                          • Added: Indicates that the object has been added
                                          • Changed: Indicates that the object has been changed
                                            • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                                            The last column describes the change itself :

                                            + +

                                            The last column describes the change itself :

                                            • Field name: Describes the field that has been changed
                                            • Before: Indicates the previous value
                                              • diff --git a/versioned_docs/version-24.10/administration/parameters/ldap.md b/versioned_docs/version-24.10/administration/parameters/ldap.md index 769c7622b8df..9b75c0fa6a90 100644 --- a/versioned_docs/version-24.10/administration/parameters/ldap.md +++ b/versioned_docs/version-24.10/administration/parameters/ldap.md @@ -98,6 +98,6 @@ on the MS Active Directory, Okta, or Posix-type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for the **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for the **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for the **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for the **Search group > base DN** field. \ No newline at end of file diff --git a/versioned_docs/version-24.10/administration/secure-platform.md b/versioned_docs/version-24.10/administration/secure-platform.md index ed2de50d58a6..5b316b5431d6 100644 --- a/versioned_docs/version-24.10/administration/secure-platform.md +++ b/versioned_docs/version-24.10/administration/secure-platform.md @@ -784,17 +784,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-24.10/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-24.10/alerts-notifications/notif-config-for-teams.md index 59233be7bf79..7b9ac4c6d4c4 100644 --- a/versioned_docs/version-24.10/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-24.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-24.10/alerts-notifications/resources-status.md b/versioned_docs/version-24.10/alerts-notifications/resources-status.md index 4311d9fa8bae..e3facb4454f8 100644 --- a/versioned_docs/version-24.10/alerts-notifications/resources-status.md +++ b/versioned_docs/version-24.10/alerts-notifications/resources-status.md @@ -293,7 +293,7 @@ Graphs display metric evolution over a given period. This can be defined in the - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Whenever the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-24.10/alerts-notifications/ticketing.md b/versioned_docs/version-24.10/alerts-notifications/ticketing.md index b4afb8c150a2..d49aec8d1a7e 100644 --- a/versioned_docs/version-24.10/alerts-notifications/ticketing.md +++ b/versioned_docs/version-24.10/alerts-notifications/ticketing.md @@ -146,9 +146,9 @@ The module stores the user list selection in an array (can be used in a smart section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-24.10/api/clapi.md b/versioned_docs/version-24.10/api/clapi.md index 6ac33a300fe9..a82a2ad0ec53 100644 --- a/versioned_docs/version-24.10/api/clapi.md +++ b/versioned_docs/version-24.10/api/clapi.md @@ -573,13 +573,13 @@ Let's assume that you would like to grant full access to the \[Monitoring\] menu centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Monitoring" ``` -Then you would like to grant access to the \[Home\] \> \[Poller statistics\] menu: +Then you would like to grant access to the \[Home\] > \[Poller statistics\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Home;Poller statistics" ``` -Then you would like to grant read-only access to the \[Configuration\] \> \[Hosts\] menu: +Then you would like to grant read-only access to the \[Configuration\] > \[Hosts\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantro -v "ACL Menu test;1;Configuration;Hosts" @@ -994,23 +994,35 @@ ipv4: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1018,71 +1030,121 @@ ipv4:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              category

                                              -

                                              Filter category

                                              -

                                              Category filter for flux in input

                                              + +

                                              category

                                              + + +

                                              Filter category

                                              + + +

                                              Category filter for flux in input

                                              +
                                              -

                                              ca_certificate

                                              -

                                              host

                                              -

                                              Trusted CA's certificate

                                              -

                                              Host to connect to

                                              -

                                              Trusted CA's certificate.

                                              -

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              + +

                                              ca_certificate

                                              +

                                              host

                                              + + +

                                              Trusted CA's certificate

                                              +

                                              Host to connect to

                                              + + +

                                              Trusted CA's certificate.

                                              +

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              +
                                              -

                                              one_peer_retention_mode

                                              -

                                              port

                                              -

                                              One peer retention

                                              -

                                              Connection port

                                              -

                                              This allows the retention to work even if the socket is listening

                                              -

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              + +

                                              one_peer_retention_mode

                                              +

                                              port

                                              + + +

                                              One peer retention

                                              +

                                              Connection port

                                              + + +

                                              This allows the retention to work even if the socket is listening

                                              +

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              +
                                              -

                                              private_key

                                              -

                                              Private key file.

                                              -

                                              Private key file path when TLS encryption is used.

                                              + +

                                              private_key

                                              + + +

                                              Private key file.

                                              + + +

                                              Private key file path when TLS encryption is used.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + -

                                              public_cert

                                              -

                                              Public certificate

                                              -

                                              Public certificate file path when TLS encryption is used.

                                              + +

                                              public_cert

                                              + + +

                                              Public certificate

                                              + + +

                                              Public certificate file path when TLS encryption is used.

                                              +
                                              -

                                              tls

                                              -

                                              Enable TLS encryption

                                              -

                                              Enable TLS encryption.

                                              + +

                                              tls

                                              + + +

                                              Enable TLS encryption

                                              + + +

                                              Enable TLS encryption.

                                              +
                                              @@ -1103,23 +1165,35 @@ ipv6: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1127,71 +1201,121 @@ ipv6:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              category

                                              -

                                              Filter category

                                              -

                                              Category filter for flux in input

                                              + +

                                              category

                                              + + +

                                              Filter category

                                              + + +

                                              Category filter for flux in input

                                              +
                                              -

                                              ca_certificate

                                              -

                                              host

                                              -

                                              Trusted CA's certificate

                                              -

                                              Host to connect to

                                              -

                                              Trusted CA's certificate.

                                              -

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              + +

                                              ca_certificate

                                              +

                                              host

                                              + + +

                                              Trusted CA's certificate

                                              +

                                              Host to connect to

                                              + + +

                                              Trusted CA's certificate.

                                              +

                                              IP address or hostname of the host to connect to (leave blank for listening mode).

                                              +
                                              -

                                              one_peer_retention_mode

                                              -

                                              port

                                              -

                                              One peer retention

                                              -

                                              Connection port

                                              -

                                              This allows the retention to work even if the socket is listening

                                              -

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              + +

                                              one_peer_retention_mode

                                              +

                                              port

                                              + + +

                                              One peer retention

                                              +

                                              Connection port

                                              + + +

                                              This allows the retention to work even if the socket is listening

                                              +

                                              Port to listen on (empty host) or to connect to (with host filled).

                                              +
                                              -

                                              private_key

                                              -

                                              Private key file.

                                              -

                                              Private key file path when TLS encryption is used.

                                              + +

                                              private_key

                                              + + +

                                              Private key file.

                                              + + +

                                              Private key file path when TLS encryption is used.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + -

                                              public_cert

                                              -

                                              Public certificate

                                              -

                                              Public certificate file path when TLS encryption is used.

                                              + +

                                              public_cert

                                              + + +

                                              Public certificate

                                              + + +

                                              Public certificate file path when TLS encryption is used.

                                              +
                                              -

                                              tls

                                              -

                                              Enable TLS encryption

                                              -

                                              Enable TLS encryption.

                                              + +

                                              tls

                                              + + +

                                              Enable TLS encryption

                                              + + +

                                              Enable TLS encryption.

                                              +
                                              @@ -1212,23 +1336,35 @@ file: -

                                              buffering_timeout

                                              -

                                              Buffering timeout

                                              -

                                              Time in seconds to wait before launching failover.

                                              + +

                                              buffering_timeout

                                              + + +

                                              Buffering timeout

                                              + + +

                                              Time in seconds to wait before launching failover.

                                              +
                                              -

                                              compression

                                              + +

                                              compression

                                              compression_buffer

                                              -

                                              compression_level

                                              -

                                              Compression (zlib)

                                              +

                                              compression_level

                                              + + +

                                              Compression (zlib)

                                              Compression buffer size

                                              -

                                              Compression level

                                              -

                                              Enable or not data stream compression.

                                              +

                                              Compression level

                                              + + +

                                              Enable or not data stream compression.

                                              The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                              -

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +

                                              Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                              +
                                              • @@ -1236,34 +1372,60 @@ file:
                                              -

                                              retry_interval

                                              -

                                              Retry interval

                                              -

                                              Time in seconds to wait between each connection attempt.

                                              + +

                                              retry_interval

                                              + + +

                                              Retry interval

                                              + + +

                                              Time in seconds to wait between each connection attempt.

                                              +
                                              -

                                              max_size

                                              -

                                              Maximum size of file

                                              -

                                              Maximum size in bytes.

                                              + +

                                              max_size

                                              + + +

                                              Maximum size of file

                                              + + +

                                              Maximum size in bytes.

                                              +
                                              -

                                              path

                                              -

                                              File path

                                              -

                                              Path to the file.

                                              + +

                                              path

                                              + + +

                                              File path

                                              + + +

                                              Path to the file.

                                              +
                                              -

                                              protocol

                                              -

                                              Serialization protocol

                                              -

                                              Serialization protocol.

                                              -

                                              ndo

                                              + +

                                              protocol

                                              + + +

                                              Serialization protocol

                                              + + +

                                              Serialization protocol.

                                              + + +

                                              ndo

                                              + @@ -1283,50 +1445,88 @@ file: -

                                              config

                                              -

                                              Configuration messages

                                              -

                                              Enable or not configuration messages logging.

                                              + +

                                              config

                                              + + +

                                              Configuration messages

                                              + + +

                                              Enable or not configuration messages logging.

                                              +
                                              -

                                              debug

                                              -

                                              Debug messages

                                              -

                                              Enable or not debug messages logging.

                                              + +

                                              debug

                                              + + +

                                              Debug messages

                                              + + +

                                              Enable or not debug messages logging.

                                              +
                                              -

                                              error

                                              -

                                              Error messages

                                              -

                                              Enable or not error messages logging.

                                              + +

                                              error

                                              + + +

                                              Error messages

                                              + + +

                                              Enable or not error messages logging.

                                              +
                                              -

                                              info

                                              -

                                              Informational messages

                                              -

                                              Enable or not informational messages logging.

                                              + +

                                              info

                                              + + +

                                              Informational messages

                                              + + +

                                              Enable or not informational messages logging.

                                              +
                                              -

                                              level

                                              -

                                              Logging level

                                              -

                                              How much messages must be logged.

                                              -

                                              high,low,medium

                                              + +

                                              level

                                              + + +

                                              Logging level

                                              + + +

                                              How much messages must be logged.

                                              + + +

                                              high,low,medium

                                              + -

                                              max_size

                                              -

                                              name

                                              -

                                              Max file size in bytes

                                              -

                                              Name of the logger

                                              -

                                              The maximum size of log file.

                                              -

                                              For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                              + +

                                              max_size

                                              +

                                              name

                                              + + +

                                              Max file size in bytes

                                              +

                                              Name of the logger

                                              + + +

                                              The maximum size of log file.

                                              +

                                              For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                              +
                                              • @@ -1348,45 +1548,76 @@ standard: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                name

                                                -

                                                Logging level

                                                -

                                                Name of the logger

                                                -

                                                How much messages must be logged.

                                                -

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                +

                                                name

                                                + + +

                                                Logging level

                                                +

                                                Name of the logger

                                                + + +

                                                How much messages must be logged.

                                                +

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                + + +

                                                high,low,medium

                                                @@ -1407,42 +1638,74 @@ syslog: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                Logging level

                                                -

                                                How much messages must be logged.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                + + +

                                                Logging level

                                                + + +

                                                How much messages must be logged.

                                                + + +

                                                high,low,medium

                                                + @@ -1460,45 +1723,76 @@ monitoring: -

                                                config

                                                -

                                                Configuration messages

                                                -

                                                Enable or not configuration messages logging.

                                                + +

                                                config

                                                + + +

                                                Configuration messages

                                                + + +

                                                Enable or not configuration messages logging.

                                                +
                                                -

                                                debug

                                                -

                                                Debug messages

                                                -

                                                Enable or not debug messages logging.

                                                + +

                                                debug

                                                + + +

                                                Debug messages

                                                + + +

                                                Enable or not debug messages logging.

                                                +
                                                -

                                                error

                                                -

                                                Error messages

                                                -

                                                Enable or not error messages logging.

                                                + +

                                                error

                                                + + +

                                                Error messages

                                                + + +

                                                Enable or not error messages logging.

                                                +
                                                -

                                                info

                                                -

                                                Informational messages

                                                -

                                                Enable or not informational messages logging.

                                                + +

                                                info

                                                + + +

                                                Informational messages

                                                + + +

                                                Enable or not informational messages logging.

                                                +
                                                -

                                                level

                                                -

                                                name

                                                -

                                                Logging level

                                                -

                                                Name of the logger

                                                -

                                                How much messages must be logged.

                                                -

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                -

                                                high,low,medium

                                                + +

                                                level

                                                +

                                                name

                                                + + +

                                                Logging level

                                                +

                                                Name of the logger

                                                + + +

                                                How much messages must be logged.

                                                +

                                                For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                + + +

                                                high,low,medium

                                                @@ -1574,33 +1868,57 @@ rrd: -

                                                buffering_timeout

                                                -

                                                Buffering timeout

                                                -

                                                Time in seconds to wait before launching failover.

                                                + +

                                                buffering_timeout

                                                + + +

                                                Buffering timeout

                                                + + +

                                                Time in seconds to wait before launching failover.

                                                +
                                                -

                                                failover

                                                -

                                                Failover name

                                                -

                                                Name of the output which will act as failover

                                                + +

                                                failover

                                                + + +

                                                Failover name

                                                + + +

                                                Name of the output which will act as failover

                                                +
                                                -

                                                retry_interval

                                                -

                                                Retry interval

                                                -

                                                Time in seconds to wait between each connection attempt.

                                                + +

                                                retry_interval

                                                + + +

                                                Retry interval

                                                + + +

                                                Time in seconds to wait between each connection attempt.

                                                +
                                                -

                                                category

                                                -

                                                Filter category

                                                -

                                                Category filter for flux in output.

                                                + +

                                                category

                                                + + +

                                                Filter category

                                                + + +

                                                Category filter for flux in output.

                                                +
                                                • @@ -1608,15 +1926,21 @@ rrd:
                                                -

                                                metrics_path

                                                + +

                                                metrics_path

                                                path

                                                -

                                                port

                                                -

                                                RRD file directory for metrics

                                                +

                                                port

                                                + + +

                                                RRD file directory for metrics

                                                Unix socket

                                                -

                                                TCP port

                                                -

                                                RRD file directory, for example /var/lib/centreon/metrics

                                                +

                                                TCP port

                                                + + +

                                                RRD file directory, for example /var/lib/centreon/metrics

                                                The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                -

                                                The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                +

                                                The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                +
                                                • @@ -1624,33 +1948,57 @@ rrd:
                                                -

                                                status_path

                                                -

                                                RRD file directory for statuses

                                                -

                                                RRD file directory, for example /var/lib/centreon/status

                                                + +

                                                status_path

                                                + + +

                                                RRD file directory for statuses

                                                + + +

                                                RRD file directory, for example /var/lib/centreon/status

                                                +
                                                -

                                                write_metrics

                                                -

                                                Enable write_metrics

                                                -

                                                Enable or not write_metrics.

                                                + +

                                                write_metrics

                                                + + +

                                                Enable write_metrics

                                                + + +

                                                Enable or not write_metrics.

                                                +
                                                -

                                                write_status

                                                -

                                                Enable write_status

                                                -

                                                Enable or not write_status.

                                                + +

                                                write_status

                                                + + +

                                                Enable write_status

                                                + + +

                                                Enable or not write_status.

                                                +
                                                -

                                                store_in_data_bin

                                                -

                                                Enable store_in_data_bin

                                                -

                                                Enable or not the storage of performance data in 'data_bin'

                                                + +

                                                store_in_data_bin

                                                + + +

                                                Enable store_in_data_bin

                                                + + +

                                                Enable or not the storage of performance data in 'data_bin'

                                                +
                                                • @@ -1673,36 +2021,60 @@ storage: -

                                                  buffering_timeout

                                                  -

                                                  Buffering timeout

                                                  -

                                                  Time in seconds to wait before launching failover.

                                                  + +

                                                  buffering_timeout

                                                  + + +

                                                  Buffering timeout

                                                  + + +

                                                  Time in seconds to wait before launching failover.

                                                  +
                                                  -

                                                  failover

                                                  -

                                                  Failover name

                                                  -

                                                  Name of the output which will act as failover

                                                  + +

                                                  failover

                                                  + + +

                                                  Failover name

                                                  + + +

                                                  Name of the output which will act as failover

                                                  +
                                                  -

                                                  retry_interval

                                                  -

                                                  Retry interval

                                                  -

                                                  Time in seconds to wait between each connection attempt.

                                                  + +

                                                  retry_interval

                                                  + + +

                                                  Retry interval

                                                  + + +

                                                  Time in seconds to wait between each connection attempt.

                                                  +
                                                  -

                                                  category

                                                  -

                                                  check_replication

                                                  -

                                                  Filter category

                                                  -

                                                  Replication enabled

                                                  -

                                                  Category filter for flux in output.

                                                  -

                                                  When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                  + +

                                                  category

                                                  +

                                                  check_replication

                                                  + + +

                                                  Filter category

                                                  +

                                                  Replication enabled

                                                  + + +

                                                  Category filter for flux in output.

                                                  +

                                                  When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                  +
                                                  • @@ -1713,91 +2085,159 @@ storage:
                                                  -

                                                  db_host

                                                  -

                                                  DB host

                                                  -

                                                  IP address or hostname of the database server.

                                                  + +

                                                  db_host

                                                  + + +

                                                  DB host

                                                  + + +

                                                  IP address or hostname of the database server.

                                                  +
                                                  -

                                                  db_name

                                                  -

                                                  DB name

                                                  -

                                                  Database name.

                                                  + +

                                                  db_name

                                                  + + +

                                                  DB name

                                                  + + +

                                                  Database name.

                                                  +
                                                  -

                                                  db_password

                                                  -

                                                  DB password

                                                  -

                                                  Password of database user.

                                                  + +

                                                  db_password

                                                  + + +

                                                  DB password

                                                  + + +

                                                  Password of database user.

                                                  +
                                                  -

                                                  db_port

                                                  -

                                                  DB port

                                                  -

                                                  Port on which the DB server listens

                                                  + +

                                                  db_port

                                                  + + +

                                                  DB port

                                                  + + +

                                                  Port on which the DB server listens

                                                  +
                                                  -

                                                  db_type

                                                  -

                                                  DB type

                                                  -

                                                  Target DBMS.

                                                  -

                                                  db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                  + +

                                                  db_type

                                                  + + +

                                                  DB type

                                                  + + +

                                                  Target DBMS.

                                                  + + +

                                                  db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                  + -

                                                  db_user

                                                  -

                                                  DB user

                                                  -

                                                  Database user.

                                                  + +

                                                  db_user

                                                  + + +

                                                  DB user

                                                  + + +

                                                  Database user.

                                                  +
                                                  -

                                                  interval

                                                  -

                                                  Interval length

                                                  -

                                                  Interval length in seconds.

                                                  + +

                                                  interval

                                                  + + +

                                                  Interval length

                                                  + + +

                                                  Interval length in seconds.

                                                  +
                                                  -

                                                  length

                                                  -

                                                  RRD length

                                                  -

                                                  RRD storage duration in seconds.

                                                  + +

                                                  length

                                                  + + +

                                                  RRD length

                                                  + + +

                                                  RRD storage duration in seconds.

                                                  +
                                                  -

                                                  queries_per_transaction

                                                  -

                                                  Maximum queries per transaction

                                                  -

                                                  The maximum queries per transaction before commit.

                                                  + +

                                                  queries_per_transaction

                                                  + + +

                                                  Maximum queries per transaction

                                                  + + +

                                                  The maximum queries per transaction before commit.

                                                  +
                                                  -

                                                  read_timeout

                                                  -

                                                  rebuild_check_interval

                                                  -

                                                  Transaction commit timeout

                                                  -

                                                  Rebuild check interval in seconds

                                                  -

                                                  The transaction timeout before running commit.

                                                  -

                                                  The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                                  + +

                                                  read_timeout

                                                  +

                                                  rebuild_check_interval

                                                  + + +

                                                  Transaction commit timeout

                                                  +

                                                  Rebuild check interval in seconds

                                                  + + +

                                                  The transaction timeout before running commit.

                                                  +

                                                  The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                                  +
                                                  -

                                                  store_in_data_bin

                                                  -

                                                  Enable store_in_data_bin

                                                  -

                                                  Enable or not the storage of performance data in 'data_bin.

                                                  + +

                                                  store_in_data_bin

                                                  + + +

                                                  Enable store_in_data_bin

                                                  + + +

                                                  Enable or not the storage of performance data in 'data_bin.

                                                  +
                                                  • @@ -1820,36 +2260,60 @@ sql: -

                                                    buffering_timeout

                                                    -

                                                    Buffering timeout

                                                    -

                                                    Time in seconds to wait before launching failover.

                                                    + +

                                                    buffering_timeout

                                                    + + +

                                                    Buffering timeout

                                                    + + +

                                                    Time in seconds to wait before launching failover.

                                                    +
                                                    -

                                                    failover

                                                    -

                                                    Failover name

                                                    -

                                                    Name of the output which will act as failover

                                                    + +

                                                    failover

                                                    + + +

                                                    Failover name

                                                    + + +

                                                    Name of the output which will act as failover

                                                    +
                                                    -

                                                    retry_interval

                                                    -

                                                    Retry interval

                                                    -

                                                    Time in seconds to wait between each connection attempt.

                                                    + +

                                                    retry_interval

                                                    + + +

                                                    Retry interval

                                                    + + +

                                                    Time in seconds to wait between each connection attempt.

                                                    +
                                                    -

                                                    category

                                                    -

                                                    check_replication

                                                    -

                                                    Filter category

                                                    -

                                                    Replication enabled

                                                    -

                                                    Category filter for flux in output.

                                                    -

                                                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                    + +

                                                    category

                                                    +

                                                    check_replication

                                                    + + +

                                                    Filter category

                                                    +

                                                    Replication enabled

                                                    + + +

                                                    Category filter for flux in output.

                                                    +

                                                    When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                    +
                                                    • @@ -1860,63 +2324,113 @@ sql:
                                                    -

                                                    db_host

                                                    -

                                                    DB host

                                                    -

                                                    IP address or hostname of the database server.

                                                    + +

                                                    db_host

                                                    + + +

                                                    DB host

                                                    + + +

                                                    IP address or hostname of the database server.

                                                    +
                                                    -

                                                    db_name

                                                    -

                                                    DB name

                                                    -

                                                    Database name.

                                                    + +

                                                    db_name

                                                    + + +

                                                    DB name

                                                    + + +

                                                    Database name.

                                                    +
                                                    -

                                                    db_password

                                                    -

                                                    DB password

                                                    -

                                                    Password of database user.

                                                    + +

                                                    db_password

                                                    + + +

                                                    DB password

                                                    + + +

                                                    Password of database user.

                                                    +
                                                    -

                                                    db_port

                                                    -

                                                    DB port

                                                    -

                                                    Port on which the DB server listens.

                                                    + +

                                                    db_port

                                                    + + +

                                                    DB port

                                                    + + +

                                                    Port on which the DB server listens.

                                                    +
                                                    -

                                                    db_type

                                                    -

                                                    DB type

                                                    -

                                                    Target DBMS.

                                                    -

                                                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                    + +

                                                    db_type

                                                    + + +

                                                    DB type

                                                    + + +

                                                    Target DBMS.

                                                    + + +

                                                    db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                    + -

                                                    db_user

                                                    -

                                                    DB user

                                                    -

                                                    Database user.

                                                    + +

                                                    db_user

                                                    + + +

                                                    DB user

                                                    + + +

                                                    Database user.

                                                    +
                                                    -

                                                    queries_per_transaction

                                                    -

                                                    Maximum queries per transaction

                                                    -

                                                    The maximum queries per transaction.

                                                    + +

                                                    queries_per_transaction

                                                    + + +

                                                    Maximum queries per transaction

                                                    + + +

                                                    The maximum queries per transaction.

                                                    +
                                                    -

                                                    read_timeout

                                                    -

                                                    Transaction commit timeout

                                                    -

                                                    Timeout delay for a transaction.

                                                    + +

                                                    read_timeout

                                                    + + +

                                                    Transaction commit timeout

                                                    + + +

                                                    Timeout delay for a transaction.

                                                    +
                                                    diff --git a/versioned_docs/version-24.10/api/graph-views-map-api.md b/versioned_docs/version-24.10/api/graph-views-map-api.md index 0b6ca7460d7c..d4fe495bfc2e 100644 --- a/versioned_docs/version-24.10/api/graph-views-map-api.md +++ b/versioned_docs/version-24.10/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-24.10/api/rest-api-v1.md b/versioned_docs/version-24.10/api/rest-api-v1.md index bbaf0b027723..1b4290a6096e 100644 --- a/versioned_docs/version-24.10/api/rest-api-v1.md +++ b/versioned_docs/version-24.10/api/rest-api-v1.md @@ -2628,8 +2628,8 @@ Use the GET method and URL below: : Additional information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-24.10/api/rest-api-v2.md b/versioned_docs/version-24.10/api/rest-api-v2.md index dee197e2fd99..faf306da80ba 100644 --- a/versioned_docs/version-24.10/api/rest-api-v2.md +++ b/versioned_docs/version-24.10/api/rest-api-v2.md @@ -66,12 +66,12 @@ Then click **Add**, and select it in the environments list. > > Here is an example of output for this command: > -> { +> \{ > "version": "24.10.1", > "major": "24", > "minor": "10", > "fix": "1" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/versioned_docs/version-24.10/connect/openid.md b/versioned_docs/version-24.10/connect/openid.md index da5d81f851d9..154b67c59e9d 100644 --- a/versioned_docs/version-24.10/connect/openid.md +++ b/versioned_docs/version-24.10/connect/openid.md @@ -213,8 +213,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -225,7 +225,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -233,8 +233,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -245,7 +245,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -253,8 +253,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -273,8 +273,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-24.10/connect/saml.md b/versioned_docs/version-24.10/connect/saml.md index 58c8d09d9239..ea855ff01bb3 100644 --- a/versioned_docs/version-24.10/connect/saml.md +++ b/versioned_docs/version-24.10/connect/saml.md @@ -127,6 +127,6 @@ users. Here is an example of fields you may have to fill in: | IdP option | Centreon value | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https:/\ | +| Assertion Consumer Service (ACS) URL | https:/\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https:/\/centreon/api/latest/saml/sls | diff --git a/versioned_docs/version-24.10/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-24.10/developer/developer-gorgone-client-server-communication.md index 084ede67e0cf..f670faf9efeb 100644 --- a/versioned_docs/version-24.10/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-24.10/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-24.10/developer/developer-translate-centreon.md b/versioned_docs/version-24.10/developer/developer-translate-centreon.md index a8de0b9eb110..7c14c667d6bc 100644 --- a/versioned_docs/version-24.10/developer/developer-translate-centreon.md +++ b/versioned_docs/version-24.10/developer/developer-translate-centreon.md @@ -143,7 +143,7 @@ will allow all users of Centreon to have access to your translation on their Cen * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-24.10/developer/developer-widget.md b/versioned_docs/version-24.10/developer/developer-widget.md index 3823b9fa8130..f433352049e7 100644 --- a/versioned_docs/version-24.10/developer/developer-widget.md +++ b/versioned_docs/version-24.10/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They must be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-24.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-24.10/installation/installation-of-a-poller/using-packages.md index a3b5c9c9544d..39220c071ecd 100644 --- a/versioned_docs/version-24.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-24.10/installation/installation-of-a-poller/using-packages.md @@ -392,9 +392,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -445,19 +445,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2023-05-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2023-05-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2023-05-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md index 7ff6ee7f5a65..bbcec779477e 100644 --- a/versioned_docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-24.10/installation/installation-of-a-remote-server/using-packages.md @@ -524,7 +524,7 @@ To transform the server into a Remote Server and to register it to the Central s ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -533,12 +533,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the central server, as seen by the remote server. +> Replace **\** with the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -615,19 +615,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.10/installation/prerequisites.md b/versioned_docs/version-24.10/installation/prerequisites.md index 461c4c1efa83..6197026208dd 100644 --- a/versioned_docs/version-24.10/installation/prerequisites.md +++ b/versioned_docs/version-24.10/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                    If you perform backups, use the following characteristics:

                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually

                                                    | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                    If you perform backups, use the following characteristics:
                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually
                                                    | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                    If you perform backups, use the following characteristics:

                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually

                                                    | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                    If you perform backups, use the following characteristics:
                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually
                                                    | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                    If you perform backups, use the following characteristics:

                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually

                                                    | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                    If you perform backups, use the following characteristics:
                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually
                                                    | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                    If you perform backups, use the following characteristics:

                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually

                                                    | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                    If you perform backups, use the following characteristics:
                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually
                                                    | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                    If you perform backups, use the following characteristics:

                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually

                                                    | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                    If you perform backups, use the following characteristics:
                                                    • size of the /var/lib/mysql partition * 0,6
                                                    • this size is meant for 1 full backup and 6 partial ones
                                                    • this is only an estimate, size should be checked manually
                                                    | **Database server** diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-clickhouse.md index aac3d08e51ba..4a932a103a0b 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-events.md index ed970f8a81e2..c2a98f4f1439 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-events.md @@ -147,7 +147,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md index fb2ed1078669..4307063c3acf 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-datadog-metrics.md @@ -150,7 +150,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-logstash-events.md index 5593aee1701b..dc4f208531be 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-logstash-events.md @@ -148,7 +148,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *8080*. diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-events.md index 4f8521f576a9..f5accc14db18 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md index 1696a2a2c5b8..5359ca70e6c6 100644 --- a/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-24.10/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-24.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-24.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/versioned_docs/version-24.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-24.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-24.10/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-24.10/integrations/event-management/sc-opsgenie.md index 90f21529eabe..9c7125446ad1 100644 --- a/versioned_docs/version-24.10/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-24.10/integrations/event-management/sc-opsgenie.md @@ -139,10 +139,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -186,7 +186,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg:\{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg:\{last_update\} is a timestamp macro. You can use\{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-24.10/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-24.10/integrations/event-management/sc-pagerduty-events.md index 9c4a2b35e234..183f0d8df036 100644 --- a/versioned_docs/version-24.10/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-24.10/integrations/event-management/sc-pagerduty-events.md @@ -196,7 +196,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-24.10/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-24.10/integrations/itsm/ot-bmc-remedy.md index 5f3575f52783..2fdd808fbf8b 100644 --- a/versioned_docs/version-24.10/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-24.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-24.10/integrations/itsm/ot-mail.md b/versioned_docs/version-24.10/integrations/itsm/ot-mail.md index c1cebed25eb4..8d19670732b5 100644 --- a/versioned_docs/version-24.10/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-24.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.emai\l} | | To | | ## Possibilities diff --git a/versioned_docs/version-24.10/integrations/itsm/ot-serena.md b/versioned_docs/version-24.10/integrations/itsm/ot-serena.md index c8baea432be2..1d7f5c60419b 100644 --- a/versioned_docs/version-24.10/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-24.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-24.10/integrations/notifications/plugin-telegram.md b/versioned_docs/version-24.10/integrations/notifications/plugin-telegram.md index d218e24bd569..4feb052f61e6 100644 --- a/versioned_docs/version-24.10/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-24.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-24.10/integrations/stream-connectors.md b/versioned_docs/version-24.10/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-24.10/integrations/stream-connectors.md +++ b/versioned_docs/version-24.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-24.10/metrology/grafana.md b/versioned_docs/version-24.10/metrology/grafana.md index d50dc5bdb5c6..8f36593eee09 100644 --- a/versioned_docs/version-24.10/metrology/grafana.md +++ b/versioned_docs/version-24.10/metrology/grafana.md @@ -86,5 +86,5 @@ Use [variables](https://grafana.com/docs/grafana/latest/variables/) to select a You can customize how the labels for the curves are displayed: go to **Time Series > Standard options**, then use [the **Display name** field](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* For instance, if you enter **${__field.labels}**, the label includes all possible label customizations (host, service, metric_name). -* If you enter **${__field.labels.host}: ${__field.labels.metric_name}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. +* For instance, if you enter **$\{__field.labels\}**, the label includes all possible label customizations (host, service, metric_name). +* If you enter **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. diff --git a/versioned_docs/version-24.10/migrate/migrate-from-3-4.md b/versioned_docs/version-24.10/migrate/migrate-from-3-4.md index 473fa8423127..e319f0d8ff11 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-3-4.md @@ -2,6 +2,8 @@ id: migrate-from-3-4 title: Migrate from a Centreon 3.4 platform --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Prerequisites @@ -77,7 +79,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Retrieve databases @@ -147,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md index d0bec569e9d5..2270014a747c 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md @@ -62,7 +62,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -146,7 +146,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md index f22e319b86d4..b391f52bd715 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md @@ -65,7 +65,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -149,7 +149,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md index f3a9160d8c1d..986f4d345103 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md @@ -78,7 +78,7 @@ dnf update rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -149,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-24.10/migrate/nagios-to-centreon.md b/versioned_docs/version-24.10/migrate/nagios-to-centreon.md index 64238133e10b..b0f9576de2c1 100644 --- a/versioned_docs/version-24.10/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-24.10/migrate/nagios-to-centreon.md @@ -105,4 +105,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** with the password of the **admin** Centreon web user. +Replace **\** with the password of the **admin** Centreon web user. diff --git a/versioned_docs/version-24.10/migrate/poller-display-to-remote-server.md b/versioned_docs/version-24.10/migrate/poller-display-to-remote-server.md index 17c2e70d4655..539152e1cb93 100644 --- a/versioned_docs/version-24.10/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-24.10/migrate/poller-display-to-remote-server.md @@ -47,7 +47,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -56,12 +56,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the Centreon server seen by the Remote Server. +> Replace **\** with the IP of the Centreon server seen by the Remote Server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -138,19 +138,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed to connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 46015124a51b..c36801d47755 100644 --- a/versioned_docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-24.10/monitoring/monitoring-servers/communications.md b/versioned_docs/version-24.10/monitoring/monitoring-servers/communications.md index e1ba4b5cba69..67a29d2c1191 100644 --- a/versioned_docs/version-24.10/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-24.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc., and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow retrieval of the remote's thumbprint, therefore it is > not possible to display the poller's Gorgone configuration from the Centreon UI. diff --git a/versioned_docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 45254a509b20..c140688115e1 100644 --- a/versioned_docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go to **Configuration > SNMP traps > SNMP traps** and click **Add** > It is possible to construct the output message yourself. To do this, use the MIB to find out the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by an OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked, the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-24.10/reporting/report-development.md b/versioned_docs/version-24.10/reporting/report-development.md index 74fe6b3a0f91..0daf02963849 100644 --- a/versioned_docs/version-24.10/reporting/report-development.md +++ b/versioned_docs/version-24.10/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-24.10/reporting/reports-publication-rule.md b/versioned_docs/version-24.10/reporting/reports-publication-rule.md index c1d6ec23a15c..b11b0d76daab 100644 --- a/versioned_docs/version-24.10/reporting/reports-publication-rule.md +++ b/versioned_docs/version-24.10/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Report publication rules {#publication_rules} +Report publication rules \{#publication_rules\} ========================= The \"Reporting \> Business Intelligence \> Publication rules\” menu @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_docs/version-25.10/administration/logging-configuration-changes.md b/versioned_docs/version-25.10/administration/logging-configuration-changes.md index 2e13b45e3076..32ed0c77f04f 100644 --- a/versioned_docs/version-25.10/administration/logging-configuration-changes.md +++ b/versioned_docs/version-25.10/administration/logging-configuration-changes.md @@ -42,7 +42,8 @@ The table below defines the columns in the results table: Modification type -

                                                    Contains the type of action applied. There are several possible types of action:

                                                    + +

                                                    Contains the type of action applied. There are several possible types of action:

                                                    • Added: Indicates that the object has been added
                                                    • Changed: Indicates that the object has been changed
                                                      • @@ -100,7 +101,8 @@ The table below defines the columns of the changes table: -

                                                      The last column describes the change itself :

                                                      + +

                                                      The last column describes the change itself :

                                                      • Field name: Describes the field that has been changed
                                                      • Before: Indicates the previous value
                                                        • diff --git a/versioned_docs/version-25.10/administration/parameters/ldap.md b/versioned_docs/version-25.10/administration/parameters/ldap.md index 769c7622b8df..9b75c0fa6a90 100644 --- a/versioned_docs/version-25.10/administration/parameters/ldap.md +++ b/versioned_docs/version-25.10/administration/parameters/ldap.md @@ -98,6 +98,6 @@ on the MS Active Directory, Okta, or Posix-type directories. > plugin](https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm). > Please define: > -> - **uid=,dc=,dc=okta,dc=com** for the **Bind DN** field -> - **ou=,dc=,dc=okta,dc=com** \*\* for the **Search group +> - **uid=\,dc=\,dc=okta,dc=com** for the **Bind DN** field +> - **ou=\,dc=\,dc=okta,dc=com** \*\* for the **Search group > base DN** field. \ No newline at end of file diff --git a/versioned_docs/version-25.10/administration/secure-platform.md b/versioned_docs/version-25.10/administration/secure-platform.md index ed2de50d58a6..5b316b5431d6 100644 --- a/versioned_docs/version-25.10/administration/secure-platform.md +++ b/versioned_docs/version-25.10/administration/secure-platform.md @@ -784,17 +784,17 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **** section. +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **** section. +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. diff --git a/versioned_docs/version-25.10/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-25.10/alerts-notifications/notif-config-for-teams.md index 59233be7bf79..7b9ac4c6d4c4 100644 --- a/versioned_docs/version-25.10/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-25.10/alerts-notifications/notif-config-for-teams.md @@ -66,9 +66,9 @@ To benefit from the plugin's capabilities, you need to create the following Cent 1. To facilitate the creation of these objects, you can copy the following content from a CLAPI file, and paste it into a file on your Central server’s /tmp directory (for instance /tmp/clapi-teams.import). > Before loading the file, replace these values with yours: - - **** with the URL you use to access Centreon web UI. - - **** with the Teams workflow URL obtained previously. - - **** with the password you want for the new contact. + - **\** with the URL you use to access Centreon web UI. + - **\** with the Teams workflow URL obtained previously. + - **\** with the password you want for the new contact. ``` shell CMD;ADD;bam-notify-by-microsoft-teams;1;$CENTREONPLUGINS$/centreon_notification_teams.pl --plugin=notification::microsoft::office365::teams::plugin --mode=alert --custommode=workflowapi --teams-workflow='$CONTACTPAGER$' --bam --service-description='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --date='$DATE$ $TIME$' --centreonurl='$CONTACTADDRESS1$' diff --git a/versioned_docs/version-25.10/alerts-notifications/resources-status.md b/versioned_docs/version-25.10/alerts-notifications/resources-status.md index 4311d9fa8bae..e3facb4454f8 100644 --- a/versioned_docs/version-25.10/alerts-notifications/resources-status.md +++ b/versioned_docs/version-25.10/alerts-notifications/resources-status.md @@ -293,7 +293,7 @@ Graphs display metric evolution over a given period. This can be defined in the - A selection of preconfigured periods is available in the graph header: Last Day, Last 7 Days, Last 31 Days - Datetime pickers are available for Start and End points in time. Whenever the displayed period changes, this element is updated accordingly -- Using the side [<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) +- Using the side [\<] and [>] buttons that appear upon hovering the graph's border, you can translate in time by half your current timespan (backward and forward in time, respectively) - Selecting a period of time within the graph will zoom in on this period ![image](../assets/alerts/resources-status/resources-status-graph-time-selection.gif) diff --git a/versioned_docs/version-25.10/alerts-notifications/ticketing.md b/versioned_docs/version-25.10/alerts-notifications/ticketing.md index b4afb8c150a2..d49aec8d1a7e 100644 --- a/versioned_docs/version-25.10/alerts-notifications/ticketing.md +++ b/versioned_docs/version-25.10/alerts-notifications/ticketing.md @@ -146,9 +146,9 @@ The module stores the user list selection in an array (can be used in a smart section like **body** or **mapping ticket arguments**). There are 3 fields (**LIST\_ID** must be replaced): -- {$select.LIST\_ID.id} -- {$select.LIST\_ID.value} -- {$select.LIST\_ID.label} +- \{$select.LIST\_ID.id\} +- \{$select.LIST\_ID.value\} +- \{$select.LIST\_ID.label\} ### Chaining rules diff --git a/versioned_docs/version-25.10/api/clapi.md b/versioned_docs/version-25.10/api/clapi.md index 6ac33a300fe9..a82a2ad0ec53 100644 --- a/versioned_docs/version-25.10/api/clapi.md +++ b/versioned_docs/version-25.10/api/clapi.md @@ -573,13 +573,13 @@ Let's assume that you would like to grant full access to the \[Monitoring\] menu centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Monitoring" ``` -Then you would like to grant access to the \[Home\] \> \[Poller statistics\] menu: +Then you would like to grant access to the \[Home\] > \[Poller statistics\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantrw -v "ACL Menu test;1;Home;Poller statistics" ``` -Then you would like to grant read-only access to the \[Configuration\] \> \[Hosts\] menu: +Then you would like to grant read-only access to the \[Configuration\] > \[Hosts\] menu: ``` shell centreon -u admin -p 'centreon' -o ACLMENU -a grantro -v "ACL Menu test;1;Configuration;Hosts" @@ -994,23 +994,35 @@ ipv4: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1018,71 +1030,121 @@ ipv4:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        category

                                                        -

                                                        Filter category

                                                        -

                                                        Category filter for flux in input

                                                        + +

                                                        category

                                                        + + +

                                                        Filter category

                                                        + + +

                                                        Category filter for flux in input

                                                        +
                                                        -

                                                        ca_certificate

                                                        -

                                                        host

                                                        -

                                                        Trusted CA's certificate

                                                        -

                                                        Host to connect to

                                                        -

                                                        Trusted CA's certificate.

                                                        -

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        + +

                                                        ca_certificate

                                                        +

                                                        host

                                                        + + +

                                                        Trusted CA's certificate

                                                        +

                                                        Host to connect to

                                                        + + +

                                                        Trusted CA's certificate.

                                                        +

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        +
                                                        -

                                                        one_peer_retention_mode

                                                        -

                                                        port

                                                        -

                                                        One peer retention

                                                        -

                                                        Connection port

                                                        -

                                                        This allows the retention to work even if the socket is listening

                                                        -

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        + +

                                                        one_peer_retention_mode

                                                        +

                                                        port

                                                        + + +

                                                        One peer retention

                                                        +

                                                        Connection port

                                                        + + +

                                                        This allows the retention to work even if the socket is listening

                                                        +

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        +
                                                        -

                                                        private_key

                                                        -

                                                        Private key file.

                                                        -

                                                        Private key file path when TLS encryption is used.

                                                        + +

                                                        private_key

                                                        + + +

                                                        Private key file.

                                                        + + +

                                                        Private key file path when TLS encryption is used.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + -

                                                        public_cert

                                                        -

                                                        Public certificate

                                                        -

                                                        Public certificate file path when TLS encryption is used.

                                                        + +

                                                        public_cert

                                                        + + +

                                                        Public certificate

                                                        + + +

                                                        Public certificate file path when TLS encryption is used.

                                                        +
                                                        -

                                                        tls

                                                        -

                                                        Enable TLS encryption

                                                        -

                                                        Enable TLS encryption.

                                                        + +

                                                        tls

                                                        + + +

                                                        Enable TLS encryption

                                                        + + +

                                                        Enable TLS encryption.

                                                        +
                                                        @@ -1103,23 +1165,35 @@ ipv6: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1127,71 +1201,121 @@ ipv6:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        category

                                                        -

                                                        Filter category

                                                        -

                                                        Category filter for flux in input

                                                        + +

                                                        category

                                                        + + +

                                                        Filter category

                                                        + + +

                                                        Category filter for flux in input

                                                        +
                                                        -

                                                        ca_certificate

                                                        -

                                                        host

                                                        -

                                                        Trusted CA's certificate

                                                        -

                                                        Host to connect to

                                                        -

                                                        Trusted CA's certificate.

                                                        -

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        + +

                                                        ca_certificate

                                                        +

                                                        host

                                                        + + +

                                                        Trusted CA's certificate

                                                        +

                                                        Host to connect to

                                                        + + +

                                                        Trusted CA's certificate.

                                                        +

                                                        IP address or hostname of the host to connect to (leave blank for listening mode).

                                                        +
                                                        -

                                                        one_peer_retention_mode

                                                        -

                                                        port

                                                        -

                                                        One peer retention

                                                        -

                                                        Connection port

                                                        -

                                                        This allows the retention to work even if the socket is listening

                                                        -

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        + +

                                                        one_peer_retention_mode

                                                        +

                                                        port

                                                        + + +

                                                        One peer retention

                                                        +

                                                        Connection port

                                                        + + +

                                                        This allows the retention to work even if the socket is listening

                                                        +

                                                        Port to listen on (empty host) or to connect to (with host filled).

                                                        +
                                                        -

                                                        private_key

                                                        -

                                                        Private key file.

                                                        -

                                                        Private key file path when TLS encryption is used.

                                                        + +

                                                        private_key

                                                        + + +

                                                        Private key file.

                                                        + + +

                                                        Private key file path when TLS encryption is used.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + -

                                                        public_cert

                                                        -

                                                        Public certificate

                                                        -

                                                        Public certificate file path when TLS encryption is used.

                                                        + +

                                                        public_cert

                                                        + + +

                                                        Public certificate

                                                        + + +

                                                        Public certificate file path when TLS encryption is used.

                                                        +
                                                        -

                                                        tls

                                                        -

                                                        Enable TLS encryption

                                                        -

                                                        Enable TLS encryption.

                                                        + +

                                                        tls

                                                        + + +

                                                        Enable TLS encryption

                                                        + + +

                                                        Enable TLS encryption.

                                                        +
                                                        @@ -1212,23 +1336,35 @@ file: -

                                                        buffering_timeout

                                                        -

                                                        Buffering timeout

                                                        -

                                                        Time in seconds to wait before launching failover.

                                                        + +

                                                        buffering_timeout

                                                        + + +

                                                        Buffering timeout

                                                        + + +

                                                        Time in seconds to wait before launching failover.

                                                        +
                                                        -

                                                        compression

                                                        + +

                                                        compression

                                                        compression_buffer

                                                        -

                                                        compression_level

                                                        -

                                                        Compression (zlib)

                                                        +

                                                        compression_level

                                                        + + +

                                                        Compression (zlib)

                                                        Compression buffer size

                                                        -

                                                        Compression level

                                                        -

                                                        Enable or not data stream compression.

                                                        +

                                                        Compression level

                                                        + + +

                                                        Enable or not data stream compression.

                                                        The higher the buffer size is, the best compression. This however increase data streaming latency. Use with caution.

                                                        -

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +

                                                        Ranges from 0 (no compression) to 9 (best compression). Default is -1 (zlib compression)

                                                        +
                                                        • @@ -1236,34 +1372,60 @@ file:
                                                        -

                                                        retry_interval

                                                        -

                                                        Retry interval

                                                        -

                                                        Time in seconds to wait between each connection attempt.

                                                        + +

                                                        retry_interval

                                                        + + +

                                                        Retry interval

                                                        + + +

                                                        Time in seconds to wait between each connection attempt.

                                                        +
                                                        -

                                                        max_size

                                                        -

                                                        Maximum size of file

                                                        -

                                                        Maximum size in bytes.

                                                        + +

                                                        max_size

                                                        + + +

                                                        Maximum size of file

                                                        + + +

                                                        Maximum size in bytes.

                                                        +
                                                        -

                                                        path

                                                        -

                                                        File path

                                                        -

                                                        Path to the file.

                                                        + +

                                                        path

                                                        + + +

                                                        File path

                                                        + + +

                                                        Path to the file.

                                                        +
                                                        -

                                                        protocol

                                                        -

                                                        Serialization protocol

                                                        -

                                                        Serialization protocol.

                                                        -

                                                        ndo

                                                        + +

                                                        protocol

                                                        + + +

                                                        Serialization protocol

                                                        + + +

                                                        Serialization protocol.

                                                        + + +

                                                        ndo

                                                        + @@ -1283,50 +1445,88 @@ file: -

                                                        config

                                                        -

                                                        Configuration messages

                                                        -

                                                        Enable or not configuration messages logging.

                                                        + +

                                                        config

                                                        + + +

                                                        Configuration messages

                                                        + + +

                                                        Enable or not configuration messages logging.

                                                        +
                                                        -

                                                        debug

                                                        -

                                                        Debug messages

                                                        -

                                                        Enable or not debug messages logging.

                                                        + +

                                                        debug

                                                        + + +

                                                        Debug messages

                                                        + + +

                                                        Enable or not debug messages logging.

                                                        +
                                                        -

                                                        error

                                                        -

                                                        Error messages

                                                        -

                                                        Enable or not error messages logging.

                                                        + +

                                                        error

                                                        + + +

                                                        Error messages

                                                        + + +

                                                        Enable or not error messages logging.

                                                        +
                                                        -

                                                        info

                                                        -

                                                        Informational messages

                                                        -

                                                        Enable or not informational messages logging.

                                                        + +

                                                        info

                                                        + + +

                                                        Informational messages

                                                        + + +

                                                        Enable or not informational messages logging.

                                                        +
                                                        -

                                                        level

                                                        -

                                                        Logging level

                                                        -

                                                        How much messages must be logged.

                                                        -

                                                        high,low,medium

                                                        + +

                                                        level

                                                        + + +

                                                        Logging level

                                                        + + +

                                                        How much messages must be logged.

                                                        + + +

                                                        high,low,medium

                                                        + -

                                                        max_size

                                                        -

                                                        name

                                                        -

                                                        Max file size in bytes

                                                        -

                                                        Name of the logger

                                                        -

                                                        The maximum size of log file.

                                                        -

                                                        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                        + +

                                                        max_size

                                                        +

                                                        name

                                                        + + +

                                                        Max file size in bytes

                                                        +

                                                        Name of the logger

                                                        + + +

                                                        The maximum size of log file.

                                                        +

                                                        For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                        +
                                                        • @@ -1348,45 +1548,76 @@ standard: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          name

                                                          -

                                                          Logging level

                                                          -

                                                          Name of the logger

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          +

                                                          name

                                                          + + +

                                                          Logging level

                                                          +

                                                          Name of the logger

                                                          + + +

                                                          How much messages must be logged.

                                                          +

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          + + +

                                                          high,low,medium

                                                          @@ -1407,42 +1638,74 @@ syslog: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          Logging level

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          + + +

                                                          Logging level

                                                          + + +

                                                          How much messages must be logged.

                                                          + + +

                                                          high,low,medium

                                                          + @@ -1460,45 +1723,76 @@ monitoring: -

                                                          config

                                                          -

                                                          Configuration messages

                                                          -

                                                          Enable or not configuration messages logging.

                                                          + +

                                                          config

                                                          + + +

                                                          Configuration messages

                                                          + + +

                                                          Enable or not configuration messages logging.

                                                          +
                                                          -

                                                          debug

                                                          -

                                                          Debug messages

                                                          -

                                                          Enable or not debug messages logging.

                                                          + +

                                                          debug

                                                          + + +

                                                          Debug messages

                                                          + + +

                                                          Enable or not debug messages logging.

                                                          +
                                                          -

                                                          error

                                                          -

                                                          Error messages

                                                          -

                                                          Enable or not error messages logging.

                                                          + +

                                                          error

                                                          + + +

                                                          Error messages

                                                          + + +

                                                          Enable or not error messages logging.

                                                          +
                                                          -

                                                          info

                                                          -

                                                          Informational messages

                                                          -

                                                          Enable or not informational messages logging.

                                                          + +

                                                          info

                                                          + + +

                                                          Informational messages

                                                          + + +

                                                          Enable or not informational messages logging.

                                                          +
                                                          -

                                                          level

                                                          -

                                                          name

                                                          -

                                                          Logging level

                                                          -

                                                          Name of the logger

                                                          -

                                                          How much messages must be logged.

                                                          -

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          -

                                                          high,low,medium

                                                          + +

                                                          level

                                                          +

                                                          name

                                                          + + +

                                                          Logging level

                                                          +

                                                          Name of the logger

                                                          + + +

                                                          How much messages must be logged.

                                                          +

                                                          For a file logger this is the path to the file. For a standard logger, one of 'stdout' or 'stderr'.

                                                          + + +

                                                          high,low,medium

                                                          @@ -1574,33 +1868,57 @@ rrd: -

                                                          buffering_timeout

                                                          -

                                                          Buffering timeout

                                                          -

                                                          Time in seconds to wait before launching failover.

                                                          + +

                                                          buffering_timeout

                                                          + + +

                                                          Buffering timeout

                                                          + + +

                                                          Time in seconds to wait before launching failover.

                                                          +
                                                          -

                                                          failover

                                                          -

                                                          Failover name

                                                          -

                                                          Name of the output which will act as failover

                                                          + +

                                                          failover

                                                          + + +

                                                          Failover name

                                                          + + +

                                                          Name of the output which will act as failover

                                                          +
                                                          -

                                                          retry_interval

                                                          -

                                                          Retry interval

                                                          -

                                                          Time in seconds to wait between each connection attempt.

                                                          + +

                                                          retry_interval

                                                          + + +

                                                          Retry interval

                                                          + + +

                                                          Time in seconds to wait between each connection attempt.

                                                          +
                                                          -

                                                          category

                                                          -

                                                          Filter category

                                                          -

                                                          Category filter for flux in output.

                                                          + +

                                                          category

                                                          + + +

                                                          Filter category

                                                          + + +

                                                          Category filter for flux in output.

                                                          +
                                                          • @@ -1608,15 +1926,21 @@ rrd:
                                                          -

                                                          metrics_path

                                                          + +

                                                          metrics_path

                                                          path

                                                          -

                                                          port

                                                          -

                                                          RRD file directory for metrics

                                                          +

                                                          port

                                                          + + +

                                                          RRD file directory for metrics

                                                          Unix socket

                                                          -

                                                          TCP port

                                                          -

                                                          RRD file directory, for example /var/lib/centreon/metrics

                                                          +

                                                          TCP port

                                                          + + +

                                                          RRD file directory, for example /var/lib/centreon/metrics

                                                          The Unix socket used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          -

                                                          The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          +

                                                          The TCP port used to communicate with rrdcached. This is a global option, go to Administration > Options > RRDTool to modify it.

                                                          +
                                                          • @@ -1624,33 +1948,57 @@ rrd:
                                                          -

                                                          status_path

                                                          -

                                                          RRD file directory for statuses

                                                          -

                                                          RRD file directory, for example /var/lib/centreon/status

                                                          + +

                                                          status_path

                                                          + + +

                                                          RRD file directory for statuses

                                                          + + +

                                                          RRD file directory, for example /var/lib/centreon/status

                                                          +
                                                          -

                                                          write_metrics

                                                          -

                                                          Enable write_metrics

                                                          -

                                                          Enable or not write_metrics.

                                                          + +

                                                          write_metrics

                                                          + + +

                                                          Enable write_metrics

                                                          + + +

                                                          Enable or not write_metrics.

                                                          +
                                                          -

                                                          write_status

                                                          -

                                                          Enable write_status

                                                          -

                                                          Enable or not write_status.

                                                          + +

                                                          write_status

                                                          + + +

                                                          Enable write_status

                                                          + + +

                                                          Enable or not write_status.

                                                          +
                                                          -

                                                          store_in_data_bin

                                                          -

                                                          Enable store_in_data_bin

                                                          -

                                                          Enable or not the storage of performance data in 'data_bin'

                                                          + +

                                                          store_in_data_bin

                                                          + + +

                                                          Enable store_in_data_bin

                                                          + + +

                                                          Enable or not the storage of performance data in 'data_bin'

                                                          +
                                                          • @@ -1673,36 +2021,60 @@ storage: -

                                                            buffering_timeout

                                                            -

                                                            Buffering timeout

                                                            -

                                                            Time in seconds to wait before launching failover.

                                                            + +

                                                            buffering_timeout

                                                            + + +

                                                            Buffering timeout

                                                            + + +

                                                            Time in seconds to wait before launching failover.

                                                            +
                                                            -

                                                            failover

                                                            -

                                                            Failover name

                                                            -

                                                            Name of the output which will act as failover

                                                            + +

                                                            failover

                                                            + + +

                                                            Failover name

                                                            + + +

                                                            Name of the output which will act as failover

                                                            +
                                                            -

                                                            retry_interval

                                                            -

                                                            Retry interval

                                                            -

                                                            Time in seconds to wait between each connection attempt.

                                                            + +

                                                            retry_interval

                                                            + + +

                                                            Retry interval

                                                            + + +

                                                            Time in seconds to wait between each connection attempt.

                                                            +
                                                            -

                                                            category

                                                            -

                                                            check_replication

                                                            -

                                                            Filter category

                                                            -

                                                            Replication enabled

                                                            -

                                                            Category filter for flux in output.

                                                            -

                                                            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                            + +

                                                            category

                                                            +

                                                            check_replication

                                                            + + +

                                                            Filter category

                                                            +

                                                            Replication enabled

                                                            + + +

                                                            Category filter for flux in output.

                                                            +

                                                            When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                            +
                                                            • @@ -1713,91 +2085,159 @@ storage:
                                                            -

                                                            db_host

                                                            -

                                                            DB host

                                                            -

                                                            IP address or hostname of the database server.

                                                            + +

                                                            db_host

                                                            + + +

                                                            DB host

                                                            + + +

                                                            IP address or hostname of the database server.

                                                            +
                                                            -

                                                            db_name

                                                            -

                                                            DB name

                                                            -

                                                            Database name.

                                                            + +

                                                            db_name

                                                            + + +

                                                            DB name

                                                            + + +

                                                            Database name.

                                                            +
                                                            -

                                                            db_password

                                                            -

                                                            DB password

                                                            -

                                                            Password of database user.

                                                            + +

                                                            db_password

                                                            + + +

                                                            DB password

                                                            + + +

                                                            Password of database user.

                                                            +
                                                            -

                                                            db_port

                                                            -

                                                            DB port

                                                            -

                                                            Port on which the DB server listens

                                                            + +

                                                            db_port

                                                            + + +

                                                            DB port

                                                            + + +

                                                            Port on which the DB server listens

                                                            +
                                                            -

                                                            db_type

                                                            -

                                                            DB type

                                                            -

                                                            Target DBMS.

                                                            -

                                                            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                            + +

                                                            db_type

                                                            + + +

                                                            DB type

                                                            + + +

                                                            Target DBMS.

                                                            + + +

                                                            db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                            + -

                                                            db_user

                                                            -

                                                            DB user

                                                            -

                                                            Database user.

                                                            + +

                                                            db_user

                                                            + + +

                                                            DB user

                                                            + + +

                                                            Database user.

                                                            +
                                                            -

                                                            interval

                                                            -

                                                            Interval length

                                                            -

                                                            Interval length in seconds.

                                                            + +

                                                            interval

                                                            + + +

                                                            Interval length

                                                            + + +

                                                            Interval length in seconds.

                                                            +
                                                            -

                                                            length

                                                            -

                                                            RRD length

                                                            -

                                                            RRD storage duration in seconds.

                                                            + +

                                                            length

                                                            + + +

                                                            RRD length

                                                            + + +

                                                            RRD storage duration in seconds.

                                                            +
                                                            -

                                                            queries_per_transaction

                                                            -

                                                            Maximum queries per transaction

                                                            -

                                                            The maximum queries per transaction before commit.

                                                            + +

                                                            queries_per_transaction

                                                            + + +

                                                            Maximum queries per transaction

                                                            + + +

                                                            The maximum queries per transaction before commit.

                                                            +
                                                            -

                                                            read_timeout

                                                            -

                                                            rebuild_check_interval

                                                            -

                                                            Transaction commit timeout

                                                            -

                                                            Rebuild check interval in seconds

                                                            -

                                                            The transaction timeout before running commit.

                                                            -

                                                            The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                                            + +

                                                            read_timeout

                                                            +

                                                            rebuild_check_interval

                                                            + + +

                                                            Transaction commit timeout

                                                            +

                                                            Rebuild check interval in seconds

                                                            + + +

                                                            The transaction timeout before running commit.

                                                            +

                                                            The interval between checks if some metrics must be rebuilt. The default value is 300s.

                                                            +
                                                            -

                                                            store_in_data_bin

                                                            -

                                                            Enable store_in_data_bin

                                                            -

                                                            Enable or not the storage of performance data in 'data_bin.

                                                            + +

                                                            store_in_data_bin

                                                            + + +

                                                            Enable store_in_data_bin

                                                            + + +

                                                            Enable or not the storage of performance data in 'data_bin.

                                                            +
                                                            • @@ -1820,36 +2260,60 @@ sql: -

                                                              buffering_timeout

                                                              -

                                                              Buffering timeout

                                                              -

                                                              Time in seconds to wait before launching failover.

                                                              + +

                                                              buffering_timeout

                                                              + + +

                                                              Buffering timeout

                                                              + + +

                                                              Time in seconds to wait before launching failover.

                                                              +
                                                              -

                                                              failover

                                                              -

                                                              Failover name

                                                              -

                                                              Name of the output which will act as failover

                                                              + +

                                                              failover

                                                              + + +

                                                              Failover name

                                                              + + +

                                                              Name of the output which will act as failover

                                                              +
                                                              -

                                                              retry_interval

                                                              -

                                                              Retry interval

                                                              -

                                                              Time in seconds to wait between each connection attempt.

                                                              + +

                                                              retry_interval

                                                              + + +

                                                              Retry interval

                                                              + + +

                                                              Time in seconds to wait between each connection attempt.

                                                              +
                                                              -

                                                              category

                                                              -

                                                              check_replication

                                                              -

                                                              Filter category

                                                              -

                                                              Replication enabled

                                                              -

                                                              Category filter for flux in output.

                                                              -

                                                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                              + +

                                                              category

                                                              +

                                                              check_replication

                                                              + + +

                                                              Filter category

                                                              +

                                                              Replication enabled

                                                              + + +

                                                              Category filter for flux in output.

                                                              +

                                                              When enabled, the broker engine will check whether or not the replication is up to date before attempting to update data.

                                                              +
                                                              • @@ -1860,63 +2324,113 @@ sql:
                                                              -

                                                              db_host

                                                              -

                                                              DB host

                                                              -

                                                              IP address or hostname of the database server.

                                                              + +

                                                              db_host

                                                              + + +

                                                              DB host

                                                              + + +

                                                              IP address or hostname of the database server.

                                                              +
                                                              -

                                                              db_name

                                                              -

                                                              DB name

                                                              -

                                                              Database name.

                                                              + +

                                                              db_name

                                                              + + +

                                                              DB name

                                                              + + +

                                                              Database name.

                                                              +
                                                              -

                                                              db_password

                                                              -

                                                              DB password

                                                              -

                                                              Password of database user.

                                                              + +

                                                              db_password

                                                              + + +

                                                              DB password

                                                              + + +

                                                              Password of database user.

                                                              +
                                                              -

                                                              db_port

                                                              -

                                                              DB port

                                                              -

                                                              Port on which the DB server listens.

                                                              + +

                                                              db_port

                                                              + + +

                                                              DB port

                                                              + + +

                                                              Port on which the DB server listens.

                                                              +
                                                              -

                                                              db_type

                                                              -

                                                              DB type

                                                              -

                                                              Target DBMS.

                                                              -

                                                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                              + +

                                                              db_type

                                                              + + +

                                                              DB type

                                                              + + +

                                                              Target DBMS.

                                                              + + +

                                                              db2,ibase,mysql,oci,odbc,postgresql,sqlite,tds

                                                              + -

                                                              db_user

                                                              -

                                                              DB user

                                                              -

                                                              Database user.

                                                              + +

                                                              db_user

                                                              + + +

                                                              DB user

                                                              + + +

                                                              Database user.

                                                              +
                                                              -

                                                              queries_per_transaction

                                                              -

                                                              Maximum queries per transaction

                                                              -

                                                              The maximum queries per transaction.

                                                              + +

                                                              queries_per_transaction

                                                              + + +

                                                              Maximum queries per transaction

                                                              + + +

                                                              The maximum queries per transaction.

                                                              +
                                                              -

                                                              read_timeout

                                                              -

                                                              Transaction commit timeout

                                                              -

                                                              Timeout delay for a transaction.

                                                              + +

                                                              read_timeout

                                                              + + +

                                                              Transaction commit timeout

                                                              + + +

                                                              Timeout delay for a transaction.

                                                              +
                                                              diff --git a/versioned_docs/version-25.10/api/graph-views-map-api.md b/versioned_docs/version-25.10/api/graph-views-map-api.md index 0b6ca7460d7c..d4fe495bfc2e 100644 --- a/versioned_docs/version-25.10/api/graph-views-map-api.md +++ b/versioned_docs/version-25.10/api/graph-views-map-api.md @@ -35,13 +35,13 @@ Body { } ``` -- In the result, retrieve the {jwtToken}. You will need to use it for all your API calls. The headers will look like this: +- In the result, retrieve the \{jwtToken\}. You will need to use it for all your API calls. The headers will look like this: ``` Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } ``` @@ -55,7 +55,7 @@ POST http://{{serverURL}}:8081/centreon-map/api/beta/maps Headers { Content-Type = application/json X-client-version = 24.10.0 - Authorization = Bearer {jwtToken} + Authorization = Bearer \{jwtToken\} } Body { @@ -63,7 +63,7 @@ Body { } ``` -- Retrieve the ID of the map {mapId} and the view {viewId} returned. +- Retrieve the ID of the map \{mapId\} and the view \{viewId\} returned. ### Open the map @@ -81,7 +81,7 @@ PUT http://{{serverURL}}:8081/centreon-map/api/beta/maps/{mapId}/views ``` Body: { - "id": {viewId}, + "id": \{viewId\}, "shapes": [ { "type": "RECTANGLE", diff --git a/versioned_docs/version-25.10/api/rest-api-v1.md b/versioned_docs/version-25.10/api/rest-api-v1.md index bbaf0b027723..1b4290a6096e 100644 --- a/versioned_docs/version-25.10/api/rest-api-v1.md +++ b/versioned_docs/version-25.10/api/rest-api-v1.md @@ -2628,8 +2628,8 @@ Use the GET method and URL below: : Additional information: - kpi\_type: 0 = service, 1 = metaservice, 2 = BA, 3 = boolean rule -- kpi\_name: name of the kpi ( / or - or or ) +- kpi\_name: name of the kpi (\ / \ or + \ or \ or \) - kpi\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - ba\_current\_status: 0 = OK, 1 = Warning, 2 = Critical, 3 = Unknown - current\_impact: impact on linked BA in % diff --git a/versioned_docs/version-25.10/api/rest-api-v2.md b/versioned_docs/version-25.10/api/rest-api-v2.md index dee197e2fd99..faf306da80ba 100644 --- a/versioned_docs/version-25.10/api/rest-api-v2.md +++ b/versioned_docs/version-25.10/api/rest-api-v2.md @@ -66,12 +66,12 @@ Then click **Add**, and select it in the environments list. > > Here is an example of output for this command: > -> { +> \{ > "version": "24.10.1", > "major": "24", > "minor": "10", > "fix": "1" -> } +> \} > > ![image](../assets/api/postman-collection-variables.png) > diff --git a/versioned_docs/version-25.10/connect/openid.md b/versioned_docs/version-25.10/connect/openid.md index da5d81f851d9..154b67c59e9d 100644 --- a/versioned_docs/version-25.10/connect/openid.md +++ b/versioned_docs/version-25.10/connect/openid.md @@ -213,8 +213,8 @@ Here is an example configuration for Microsoft Azure Active Directory: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${tenantId}`, `${clientId}` and `${clientSecret}` with your own values. @@ -225,7 +225,7 @@ Here is an example configuration for Okta: | Fields | Values | |------------------------------|------------------------------------------| -| Base Url | https://${theIdPdomain}/oauth2/v1 | +| Base Url | https://$\{theIdPdomain\}/oauth2/v1 | | Authorization Endpoint | /authorize | | Token Endpoint | /token | | Introspection Token Endpoint | /introspect | @@ -233,8 +233,8 @@ Here is an example configuration for Okta: | End Session Endpoint | /logout | | Scope | profile openid | | Login claim value | username | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -245,7 +245,7 @@ Here is an example configuration for Keycloak: | Fields | Values | |------------------------------|-------------------------------------------------------------------------| -| Base Url | https://${theIdPdomain}:8080/auth/realms/master/protocol/openid-connect | +| Base Url | https://$\{theIdPdomain\}:8080/auth/realms/master/protocol/openid-connect | | Authorization Endpoint | /auth | | Token Endpoint | /token | | Introspection Token Endpoint | /token/introspect | @@ -253,8 +253,8 @@ Here is an example configuration for Keycloak: | End Session Endpoint | /logout | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `${theIdPdomain}`, `${clientId}` and `${clientSecret}` with your own values. @@ -273,8 +273,8 @@ Here is an example configuration for LemonLDAP::NG: | End Session Endpoint | | | Scope | openid | | Login claim value | email | -| Client ID | ${clientId} | -| Client Secret | ${clientSecret} | +| Client ID | $\{clientId\} | +| Client Secret | $\{clientSecret\} | > Please replace `auth.example.com`, `${clientId}` and `${clientSecret}` with your own values. diff --git a/versioned_docs/version-25.10/connect/saml.md b/versioned_docs/version-25.10/connect/saml.md index 58c8d09d9239..ea855ff01bb3 100644 --- a/versioned_docs/version-25.10/connect/saml.md +++ b/versioned_docs/version-25.10/connect/saml.md @@ -127,6 +127,6 @@ users. Here is an example of fields you may have to fill in: | IdP option | Centreon value | |--------------------------------------|----------------------------------------------------------------| -| Client ID | https:// | -| Assertion Consumer Service (ACS) URL | https:///centreon/api/latest/saml/acs | -| Redirect Binding URLs for SLO | https:///centreon/api/latest/saml/sls | +| Client ID | https:/\ | +| Assertion Consumer Service (ACS) URL | https:/\/centreon/api/latest/saml/acs | +| Redirect Binding URLs for SLO | https:/\/centreon/api/latest/saml/sls | diff --git a/versioned_docs/version-25.10/developer/developer-gorgone-client-server-communication.md b/versioned_docs/version-25.10/developer/developer-gorgone-client-server-communication.md index 084ede67e0cf..f670faf9efeb 100644 --- a/versioned_docs/version-25.10/developer/developer-gorgone-client-server-communication.md +++ b/versioned_docs/version-25.10/developer/developer-gorgone-client-server-communication.md @@ -35,7 +35,7 @@ $ chmod 644 /var/spool/centreon/.gorgone/pubkey.pem $ chmod 600 /var/spool/centreon/.gorgone/privkey.pem ``` -Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone/**). +Copy the server's public key onto the client in a specific directory (for example **/var/spool/centreon/.gorgone\**). ## Get the string-formatted JWK thumbprint diff --git a/versioned_docs/version-25.10/developer/developer-translate-centreon.md b/versioned_docs/version-25.10/developer/developer-translate-centreon.md index a8de0b9eb110..7c14c667d6bc 100644 --- a/versioned_docs/version-25.10/developer/developer-translate-centreon.md +++ b/versioned_docs/version-25.10/developer/developer-translate-centreon.md @@ -143,7 +143,7 @@ will allow all users of Centreon to have access to your translation on their Cen * Create an account on GitHub * Fork centreon/centreon project on GitHub -* Add your translated \*.mo and \*.po files to lang//LC_MESSAGES directory +* Add your translated \*.mo and \*.po files to lang\/LC_MESSAGES directory * Commit your change on your project * Create a pull request on centreon/centreon project * We will add your translation to Centreon. diff --git a/versioned_docs/version-25.10/developer/developer-widget.md b/versioned_docs/version-25.10/developer/developer-widget.md index 3823b9fa8130..f433352049e7 100644 --- a/versioned_docs/version-25.10/developer/developer-widget.md +++ b/versioned_docs/version-25.10/developer/developer-widget.md @@ -20,7 +20,7 @@ Of course, you could make a widget that would only work with a certain module. Widgets work pretty much like Modules. They must be placed in the following directory: ```Shell -centreon/www/widgets/name-of-your-widget/ +centreon/www/widgets/name-of-your-widget\/ ``` Your widget must contain one mandatory file named **configs.xml** at its root. @@ -106,7 +106,7 @@ Parameter type | | > : greater than | | < : less than | | >= : greater or equal -| | <= : less or equal +| | \<= : less or equal | | = : equal | | != : not equal | | LIKE : can be used with the wildcard %% diff --git a/versioned_docs/version-25.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-25.10/installation/installation-of-a-poller/using-packages.md index a3b5c9c9544d..39220c071ecd 100644 --- a/versioned_docs/version-25.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-25.10/installation/installation-of-a-poller/using-packages.md @@ -392,9 +392,9 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) +> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` @@ -445,19 +445,19 @@ You will receive the validation of the Centreon central or the Remote Server ser 2023-05-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2023-05-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2023-05-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md index 7ff6ee7f5a65..bbcec779477e 100644 --- a/versioned_docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-25.10/installation/installation-of-a-remote-server/using-packages.md @@ -524,7 +524,7 @@ To transform the server into a Remote Server and to register it to the Central s ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -533,12 +533,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the central server, as seen by the remote server. +> Replace **\** with the IP of the central server, as seen by the remote server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> `HTTPS://:PORT` +> `HTTPS:/:PORT` Then follow instructions by 1. Entering your password: @@ -615,19 +615,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Couldn't connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-25.10/installation/prerequisites.md b/versioned_docs/version-25.10/installation/prerequisites.md index 461c4c1efa83..6197026208dd 100644 --- a/versioned_docs/version-25.10/installation/prerequisites.md +++ b/versioned_docs/version-25.10/installation/prerequisites.md @@ -54,7 +54,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -88,7 +88,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -157,7 +157,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -226,7 +226,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | **Database server** @@ -313,7 +313,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | | vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB

                                                              If you perform backups, use the following characteristics:

                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually

                                                              | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
                                                              If you perform backups, use the following characteristics:
                                                              • size of the /var/lib/mysql partition * 0,6
                                                              • this size is meant for 1 full backup and 6 partial ones
                                                              • this is only an estimate, size should be checked manually
                                                              | **Database server** diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-clickhouse.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-clickhouse.md index aac3d08e51ba..4a932a103a0b 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-clickhouse.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-clickhouse.md @@ -265,7 +265,7 @@ If you want to test that events are sent to Clickhouse correctly: 2. Run the following command: ```shell -curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' '' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' +curl -X POST -H 'X-ClickHouse-User: ' -H 'X-ClickHouse-Key: ' ' -d 'INSERT INTO . (host, timestamp, metric_name, metric_value, service, hostgroups, metric_id, metric_unit, metric_min, metric_max) VALUES ('central_2',1702910872,'rtmin',0.0,'Ping',['hg'],'11-9-rtmin','ms',,),('central_2',1702910872,'rta',0.0,'Ping',['hg'],'11-9-rta','ms',0.0,),('central_2',1702910872,'pl',100.0,'Ping',['hg'],'11-9-pl','%',0.0,100.0)' ``` > You must replace all the *``* inside the below commands with their appropriate value. For example, *``* may become *centreon_stream*. diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-events.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-events.md index ed970f8a81e2..c2a98f4f1439 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-events.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-events.md @@ -147,7 +147,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"title":"CRITICAL my_host my_service","text":"my service is not working","aggregation_key":"service_27_12","alert_type":"error","host":"my_host","date_happened":1630590530}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. \ No newline at end of file +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. \ No newline at end of file diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md index fb2ed1078669..4307063c3acf 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-datadog-metrics.md @@ -150,7 +150,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " '' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' +curl -X POST -H "content-type: application/json" -H "DD-API-KEY: " ' -d '{"host":"my_host","metric":"database.used.percent","points":[[1630590530,80]],"tags":["service:my_service","instance:my_instance","subinstance:sub_1","subinstance:sub_2"]}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *https://api.datadoghq.com*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *https://api.datadoghq.com*. diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md index 6749c1157ae0..79133045d879 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-influxdb2-metrics.md @@ -173,9 +173,9 @@ If you want to test that events are sent to InfluxDB 2 correctly: 2. Run the following command: ```shell - curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http:///api/v2/write?bucket=&org=&precision=s' -d + curl -X POST -H 'content-type: text/plain; charset=utf-8' -H 'accept: application/json' -H 'Authorization: Token ' 'http://api/v2/write?bucket&org=&precision=s' -d ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become something like *65f5f748e28c92f0*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become something like *65f5f748e28c92f0*. 3. Check that the event has been received by InfluxDB 2. diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-logstash-events.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-logstash-events.md index 5593aee1701b..dc4f208531be 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-logstash-events.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-logstash-events.md @@ -148,7 +148,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X PUT -H "accept: application/json" curl -X PUT 'http://:' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' +curl -X PUT -H "accept: application/json" curl -X PUT 'http://' -d '{"event_timestamp": 1653434348,"hostname": "my-host","output": "[DOWN] server is down","state": "DOWN","title": "DOWN: my-host"}' ``` -You must replace all the *``* inside the above command with their appropriate value. ** may become *8080*. +You must replace all the *``* inside the above command with their appropriate value. \* may become *8080*. diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-events.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-events.md index 4f8521f576a9..f5accc14db18 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-events.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-events.md @@ -196,9 +196,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell -curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' +curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","output": "Critical: it is on fire"}}' ``` - > You must replace all the *``* inside the above command with their appropriate value. ** may become *_json*. + > You must replace all the *``* inside the above command with their appropriate value. \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md b/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md index 1696a2a2c5b8..5359ca70e6c6 100644 --- a/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md +++ b/versioned_docs/version-25.10/integrations/data-analytics/sc-splunk-metrics.md @@ -191,9 +191,9 @@ If you want to test that events are sent to Splunk correctly: 2. Run the following command: ```shell - curl -X POST -H "content-type: application/json" -H "authorization: Splunk " '' -d '{"sourcetype": "","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' + curl -X POST -H "content-type: application/json" -H "authorization: Splunk " ' -d '{"sourcetype": ","source": "","index": "","host": "","time": ,"event": {"event_type": "host","state": 1,"state_type": 1,"hostname":"my_host","ctime": 1675865364,"metric: pl": 0,"metric: rta": 10,"metric: rtmin": 5,"metric: rtmax": 15}}' ``` - > Replace all the *``* inside the above command with the correct value. For instance, ** may become *_json*. + > Replace all the *``* inside the above command with the correct value. For instance, \* may become *_json*. 3. Check that the event has been received by Splunk. diff --git a/versioned_docs/version-25.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md b/versioned_docs/version-25.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md index 60d22c97a534..6b78c581f3f5 100644 --- a/versioned_docs/version-25.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md +++ b/versioned_docs/version-25.10/integrations/digital-experience-monitoring/pack-skylight-pvx.md @@ -20,13 +20,13 @@ The connector has been tested with the following versions: \* PVX version 5.1.1 To query PVX API, you need to generate an access key. This key will never expire and the procedure below is an extract from the official documentation -. +\. Follow these steps to get your API key. In each step replace the value of the macros enclosed by '\< \>' with yours. Command: `curl -k -'https://****/api/login?user=****&password=****'` +'https://**\**/api/login?user=****&password=****'` Result: @@ -40,7 +40,7 @@ Result: Thanks to the obtained session ID, execute the command below get a secret key Command: `curl -k -'https:///api/create-api-key?name=****&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` +'https:///api/create-api-key?name=**\**&_session=session:91554086-842b-4b73-9028-c51d20d91b94'` Result: diff --git a/versioned_docs/version-25.10/integrations/event-management/sc-opsgenie.md b/versioned_docs/version-25.10/integrations/event-management/sc-opsgenie.md index 90f21529eabe..ef124f24ee02 100644 --- a/versioned_docs/version-25.10/integrations/event-management/sc-opsgenie.md +++ b/versioned_docs/version-25.10/integrations/event-management/sc-opsgenie.md @@ -139,10 +139,10 @@ To make sure that everything goes fine, you should have a look at `central-broke | `skip_nil_id` | Number | `1` | Do not send events from objects that do not have an ID (meta services most of the time) | | `accepted_hostgroups` | String | | List of hostgroups in which the host must be (coma separeted eg: grp1,grp2,grp3) | | `date_format` | String | `%Y-%m-%d %H:%M:%S` | The default date format for converted timestamps (https://www.lua.org/pil/22.1) | -| `host_alert_message` | String | `{last_update_date} {hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | +| `host_alert_message` | String | `{last_update_date}{hostname} is {state}` | The default message for host alerts. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_description` | String | | The default description of a host alert. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | | `host_alert_alias` | String | `{hostname}_{state}` | The default alias for a host alert, useful for alert deduplication. See [host event macros](sc-opsgenie.md#host-event-macros) for more details about macros | -| `service_alert_message` | String | `{last_update_date} {hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | +| `service_alert_message` | String | `{last_update_date}{hostname} // {serviceDescription} is {state}` | The default message for service alerts. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_description` | String | | The default description of a service alert. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `service_alert_alias` | String | `{hostname}_{serviceDescription}_{state}` | The default alias for a service alert, useful for alert deduplication. See [service event macros](sc-opsgenie.md#service-event-macros) for more details about macros | | `ba_incident_message` | String | `{baName} is {state}, health level reached {level_nominal}` | The default message for a ba incident. See [BA event macros](sc-opsgenie.md#ba-event-macros) for more details about macros | @@ -186,7 +186,7 @@ rm -f /usr/share/centreon-broker/lua/opsgenie.lua ## Macros -Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: {hostname}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: {last_update} is a timestamp macro. You can use {last_update_date} to have it converted) +Macros are a tool to create dynamic messages depending on the event you want to send. They must be enclosed by {} (eg: \{hostname\}). If a macro is a time type macro then you will be able to use **\_date suffix** to convert it to a human readable format. You can Change this format using the string parameter `date_format` (eg: \{last_update\} is a timestamp macro. You can use \{last_update_date\} to have it converted) #### Host event macros diff --git a/versioned_docs/version-25.10/integrations/event-management/sc-pagerduty-events.md b/versioned_docs/version-25.10/integrations/event-management/sc-pagerduty-events.md index 9c4a2b35e234..183f0d8df036 100644 --- a/versioned_docs/version-25.10/integrations/event-management/sc-pagerduty-events.md +++ b/versioned_docs/version-25.10/integrations/event-management/sc-pagerduty-events.md @@ -196,7 +196,7 @@ Here is the list of all the curl commands that are used by the stream connector. ### Send events ```shell -curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":"_H","payload":{"component":"","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":""},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' +curl -X POST -H 'content-type: application/json' 'https://events.pagerduty.com/v2/enqueue' -d '{"dedup_key":_H","payload":{"component":","group":"","summary":"winter is coming","class":"host","severity":"info","timestamp":"2021-09-24T14:37:22.000","custom_details":{"Hostgroups":"","Hostseverity":2},"source":"},"event_action":"trigger","client":"Centreon Stream Connector","routing_key":"dzada32193dzbe1fz51xz","links":[{"href":"","text":"Link to Centreon host summary"}]}' ``` - You must replace all the *``* inside the above command with their appropriate value. ** may become *linuxServerA*. + You must replace all the *``* inside the above command with their appropriate value. \* may become *linuxServerA*. diff --git a/versioned_docs/version-25.10/integrations/itsm/ot-bmc-remedy.md b/versioned_docs/version-25.10/integrations/itsm/ot-bmc-remedy.md index 5f3575f52783..2fdd808fbf8b 100644 --- a/versioned_docs/version-25.10/integrations/itsm/ot-bmc-remedy.md +++ b/versioned_docs/version-25.10/integrations/itsm/ot-bmc-remedy.md @@ -27,7 +27,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------------------------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | IncidentInterface\_Create\_WS | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-25.10/integrations/itsm/ot-mail.md b/versioned_docs/version-25.10/integrations/itsm/ot-mail.md index c1cebed25eb4..b9f1e8aa53eb 100644 --- a/versioned_docs/version-25.10/integrations/itsm/ot-mail.md +++ b/versioned_docs/version-25.10/integrations/itsm/ot-mail.md @@ -25,7 +25,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ---------------- | -| From | {$user.email} | +| From | \{$user.email\} | | To | | ## Possibilities diff --git a/versioned_docs/version-25.10/integrations/itsm/ot-serena.md b/versioned_docs/version-25.10/integrations/itsm/ot-serena.md index c8baea432be2..1d7f5c60419b 100644 --- a/versioned_docs/version-25.10/integrations/itsm/ot-serena.md +++ b/versioned_docs/version-25.10/integrations/itsm/ot-serena.md @@ -26,7 +26,7 @@ Our provider requires the following parameters: | Parameter | Example of value | | --------- | ----------------------------------------------- | -| Endpoint | | +| Endpoint | \ | | Namespace | xxxxxxx | | Username | centreon | | Password | MyPassword | diff --git a/versioned_docs/version-25.10/integrations/notifications/plugin-telegram.md b/versioned_docs/version-25.10/integrations/notifications/plugin-telegram.md index d218e24bd569..4feb052f61e6 100644 --- a/versioned_docs/version-25.10/integrations/notifications/plugin-telegram.md +++ b/versioned_docs/version-25.10/integrations/notifications/plugin-telegram.md @@ -140,8 +140,8 @@ Below are some of the available options: | ----------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | \--centreon-token | an autologin token from centreon | | | \--centreon-url | the centreon url | | -| \--graph-url | graph url. You can use the above options as macro here | **%{centreon\_url}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%{centreon\_token}**&hostname=**%{host\_name}**&service=**%{service\_description}** | -| \--link-url | a link url | **%{centreon\_url}**/main.php?p=20201&o=svc&host\_search=**%{host\_name}**&svc\_search=**%{service\_description}** | +| \--graph-url | graph url. You can use the above options as macro here | **%\{centreon_url\}**/include/views/graphs/generateGraphs/generateImage.php?username=myuser&token=**%\{centreon_token\}**&hostname=**%\{host_name\}**&service=**%\{service_description\}** | +| \--link-url | a link url | **%\{centreon_url\}**/main.php?p=20201&o=svc&host\_search=**%\{host_name\}**&svc\_search=**%\{service_description\}** | | \--proxyurl | the url to your proxy if needed | | All options can be displayed with the following command: diff --git a/versioned_docs/version-25.10/integrations/stream-connectors.md b/versioned_docs/version-25.10/integrations/stream-connectors.md index dbdcb134d250..ca15497c96d1 100644 --- a/versioned_docs/version-25.10/integrations/stream-connectors.md +++ b/versioned_docs/version-25.10/integrations/stream-connectors.md @@ -2,6 +2,8 @@ id: stream-connectors title: Stream connectors --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; Stream connectors transfer in real time the flow of monitoring data coming from the Centreon platform to a third-party tool. This flow can contain events or metrics. diff --git a/versioned_docs/version-25.10/metrology/grafana.md b/versioned_docs/version-25.10/metrology/grafana.md index d50dc5bdb5c6..8f36593eee09 100644 --- a/versioned_docs/version-25.10/metrology/grafana.md +++ b/versioned_docs/version-25.10/metrology/grafana.md @@ -86,5 +86,5 @@ Use [variables](https://grafana.com/docs/grafana/latest/variables/) to select a You can customize how the labels for the curves are displayed: go to **Time Series > Standard options**, then use [the **Display name** field](https://grafana.com/docs/grafana/latest/panels-visualizations/configure-standard-options/#display-name). -* For instance, if you enter **${__field.labels}**, the label includes all possible label customizations (host, service, metric_name). -* If you enter **${__field.labels.host}: ${__field.labels.metric_name}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. +* For instance, if you enter **$\{__field.labels\}**, the label includes all possible label customizations (host, service, metric_name). +* If you enter **$\{__field.labels.host\}: $\{__field.labels.metric_name\}**, the label for a curve will be displayed like this: **10.11.12.13: total_cpu_avg**. diff --git a/versioned_docs/version-25.10/migrate/migrate-from-3-4.md b/versioned_docs/version-25.10/migrate/migrate-from-3-4.md index 473fa8423127..e319f0d8ff11 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-3-4.md @@ -2,6 +2,8 @@ id: migrate-from-3-4 title: Migrate from a Centreon 3.4 platform --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Prerequisites @@ -77,7 +79,7 @@ rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Retrieve databases @@ -147,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** with the IP of the new Centreon server. +> Replace **\** with the IP of the new Centreon server. ### Synchronize the plugins diff --git a/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md index f22e319b86d4..b391f52bd715 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md @@ -65,7 +65,7 @@ complete the installation process by connecting to the Centreon web interface. rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. 5. On the new server, change the following user rights: @@ -149,7 +149,7 @@ create them again:: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md index f3a9160d8c1d..986f4d345103 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md @@ -78,7 +78,7 @@ dnf update rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" ``` - > Replace **** by the IP address of the new Centreon server. + > Replace **\** by the IP address of the new Centreon server. ### Step 3: Retrieve the databases @@ -149,7 +149,7 @@ create them again: systemctl start mariadb ``` -> Replace **** by the IP address of the new Centreon server. +> Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-25.10/migrate/nagios-to-centreon.md b/versioned_docs/version-25.10/migrate/nagios-to-centreon.md index 64238133e10b..b0f9576de2c1 100644 --- a/versioned_docs/version-25.10/migrate/nagios-to-centreon.md +++ b/versioned_docs/version-25.10/migrate/nagios-to-centreon.md @@ -105,4 +105,4 @@ server: /usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt ``` -Replace **** with the password of the **admin** Centreon web user. +Replace **\** with the password of the **admin** Centreon web user. diff --git a/versioned_docs/version-25.10/migrate/poller-display-to-remote-server.md b/versioned_docs/version-25.10/migrate/poller-display-to-remote-server.md index 17c2e70d4655..539152e1cb93 100644 --- a/versioned_docs/version-25.10/migrate/poller-display-to-remote-server.md +++ b/versioned_docs/version-25.10/migrate/poller-display-to-remote-server.md @@ -47,7 +47,7 @@ To transform the server into a Remote Server and register it to the Centreon Cen ``` shell /usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n +-t remote -h -n ``` Example: @@ -56,12 +56,12 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 ``` -> Replace **** with the IP of the Centreon server seen by the Remote Server. +> Replace **\** with the IP of the Centreon server seen by the Remote Server. -> The **** must have access to the configuration API. You can use the default **admin** account. +> The **\** must have access to the configuration API. You can use the default **admin** account. > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS://:PORT +> HTTPS:/\:PORT Then follow instructions by 1. Entering your password: @@ -138,19 +138,19 @@ You will receive the validation of the Centreon central server: 2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials ``` -> Your credentials are incorrect for the ****. +> Your credentials are incorrect for the **\**. ``` shell 2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. ``` -> The **** doesn't have access to configuration API. +> The **\** doesn't have access to configuration API. ``` shell Failed to connect to 192.168.0.1:444; Connection refused ``` -> Unable to access the API. Please check ****, scheme and port. +> Unable to access the API. Please check **\**, scheme and port. ``` shell 2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login diff --git a/versioned_docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md b/versioned_docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md index 46015124a51b..c36801d47755 100644 --- a/versioned_docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md +++ b/versioned_docs/version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration.md @@ -75,7 +75,7 @@ Remote Server on the Centreon platform. systemctl restart cbd ``` - If needed, check **/var/log/centreon-broker/.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) + If needed, check **/var/log/centreon-broker/\.log** for issues/errors. (In the example above, the file would be **/var/log/centreon-broker/remote-server.log**.) ## Step 2: Enable communication diff --git a/versioned_docs/version-25.10/monitoring/monitoring-servers/communications.md b/versioned_docs/version-25.10/monitoring/monitoring-servers/communications.md index e1ba4b5cba69..67a29d2c1191 100644 --- a/versioned_docs/version-25.10/monitoring/monitoring-servers/communications.md +++ b/versioned_docs/version-25.10/monitoring/monitoring-servers/communications.md @@ -29,14 +29,14 @@ Communication modes are listed below: | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | -------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | @@ -51,28 +51,28 @@ acknowledgements, etc., and configuration export. | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | -| **Central** <-- *ZMQ* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | +| **Central** \<-- *ZMQ* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection, Host Discovery | | Communications | Allowed actions | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | +| **Central** \<-- *SSH* --\> **Remote** \<-- *SSH* --\> **Poller** | Monitoring actions\*, Engine/Broker statistics collection (Remote only), Host Discovery (Remote only) | | Communications | Allowed actions | | ----------------------------------------------------------------- | -------------------- | -| **Central** <-- *SSH* --\> **Remote** <-- *ZMQ* --\> **Poller** | Monitoring actions\* | +| **Central** \<-- *SSH* --\> **Remote** \<-- *ZMQ* --\> **Poller** | Monitoring actions\* | > This mode does not allow retrieval of the remote's thumbprint, therefore it is > not possible to display the poller's Gorgone configuration from the Centreon UI. diff --git a/versioned_docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md b/versioned_docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md index 45254a509b20..abfc7715d152 100644 --- a/versioned_docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md +++ b/versioned_docs/version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions.md @@ -62,7 +62,7 @@ Go to **Configuration > SNMP traps > SNMP traps** and click **Add** > It is possible to construct the output message yourself. To do this, use the MIB to find out the arguments that will be > present in the body of the event and retrieve the arguments with the variables **$n**. As each argument is identified > by an OID, it is possible to use this OID directly to place it in the output message without knowing its position via -> the variable **@{OID}**. +> the variable **@\{OID\}**. * The **Default status** field defines the “monitoring” status of the service in case of reception of the trap. * If the **Submit result** box is checked, the result is submitted to the Network supervisor engine. @@ -119,7 +119,7 @@ The following command can be used to retrieve this value: snmpget -v 2c -Ovq -c ifAlias.$1 ``` -To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p{n} where ‘n’ +To use the result of the PREEXEC command in the **Output message**, it is necessary to use the variable $p\{n\} where ‘n’ corresponds to the order of definition of the command. Example: @@ -175,7 +175,7 @@ or **Special command** fields. These arguments are listed in the table below: | Macro name | Description | |--------------------------|---------------------------------------------------------------------------------------------------------------------------| -| @{NUMERIC_OID} | Retrieval of the value of an argument via its OID, e.g.: @{.1.3.6.1.4.1.9.9.43.1.1.1} | +| @\{NUMERIC_OID\} | Retrieval of the value of an argument via its OID, e.g.: @\{.1.3.6.1.4.1.9.9.43.1.1.1\} | | $1, $2... | Retrieval of the value of an argument via its order of appearance | | $p1, $p2,... | Value of the command: PREEXEC ($p1 = at the first command, $p2 at the second, ...) | | $* | All the arguments separated by a space | diff --git a/versioned_docs/version-25.10/reporting/report-development.md b/versioned_docs/version-25.10/reporting/report-development.md index 74fe6b3a0f91..0daf02963849 100644 --- a/versioned_docs/version-25.10/reporting/report-development.md +++ b/versioned_docs/version-25.10/reporting/report-development.md @@ -70,8 +70,7 @@ The different data sets defined in a report will contain all the available data to build the visuals in the report (e.g., tables and charts). -![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png){width="18.401cm" -height="5.117cm"} +![100000000000053D00000175C278E199_png](../assets/reporting/dev-guide/100000000000053D00000175C278E199.png)\{width="18.401cm" height="5.117cm"\} ### Data binding diff --git a/versioned_docs/version-25.10/reporting/reports-publication-rule.md b/versioned_docs/version-25.10/reporting/reports-publication-rule.md index c1d6ec23a15c..b11b0d76daab 100644 --- a/versioned_docs/version-25.10/reporting/reports-publication-rule.md +++ b/versioned_docs/version-25.10/reporting/reports-publication-rule.md @@ -1,4 +1,4 @@ -Report publication rules {#publication_rules} +Report publication rules \{#publication_rules\} ========================= The \"Reporting \> Business Intelligence \> Publication rules\” menu @@ -31,8 +31,8 @@ monitoring server.: > Enter same passphrase again: > Your identification has been saved in /home/centreonBI/.ssh/id_rsa. -::: {.note} -::: {.title} +::: \{.note\} +::: \{.title\} Note ::: @@ -43,11 +43,11 @@ passphrase. Transfer the key to the **Centreon** server. The **centreonBI** user must be configured with a password on the monitoring server): - ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@{MONITORING_IP_ADDRESS} + ssh-copy-id -i ~/.ssh/id_rsa.pub centreonBI@\{MONITORING_IP_ADDRESS\} Test the SSH connection from the reporting server: - ssh centreonBI@{MONITORING_IP_ADDRESS} + ssh centreonBI@\{MONITORING_IP_ADDRESS\} You should be able to connect without entering any password. diff --git a/versioned_sidebars/version-22.10-sidebars.json b/versioned_sidebars/version-22.10-sidebars.json index e43ccf5458b5..658fbdd82f16 100644 --- a/versioned_sidebars/version-22.10-sidebars.json +++ b/versioned_sidebars/version-22.10-sidebars.json @@ -1,5 +1,5 @@ { - "version-22.10/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,27 +91,27 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-22.10/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-22.10/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-22.10/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-22.10/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-22.10/installation/download" + "id": "installation/download" }, { "type": "category", @@ -122,21 +122,21 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-22.10/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -147,11 +147,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -164,11 +164,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -181,29 +181,29 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-22.10/installation/offline" + "id": "installation/offline" }, { "type": "category", @@ -214,19 +214,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha/installation-2-nodes" + "id": "installation/installation-of-centreon-ha/installation-2-nodes" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha/installation-4-nodes" + "id": "installation/installation-of-centreon-ha/installation-4-nodes" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha/integrating-pollers" + "id": "installation/installation-of-centreon-ha/integrating-pollers" } ] }, @@ -239,15 +239,15 @@ "items": [ { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-22.10/installation/installation-of-centreon-ha-manual/integrating-pollers" + "id": "installation/installation-of-centreon-ha-manual/integrating-pollers" } ] } @@ -262,11 +262,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-22.10/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -286,19 +286,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-22.10/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-22.10/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-22.10/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -311,23 +311,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -340,23 +340,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -369,27 +369,27 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-22.10/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-22.10/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-22.10/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-22.10/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-22.10/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -402,11 +402,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-22.10/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -419,19 +419,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-22.10/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -444,7 +444,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -457,33 +457,33 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-22.10/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-22.10/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-22.10/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-22.10/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-22.10/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-22.10/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -503,23 +503,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" } ] }, @@ -532,19 +532,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -557,31 +557,31 @@ "items": [ { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -594,11 +594,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-22.10/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -613,27 +613,27 @@ "items": [ { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-22.10/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-22.10/administration/access-control-lists" + "id": "administration/access-control-lists" } ] }, @@ -646,23 +646,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-22.10/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-22.10/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-22.10/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-22.10/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -675,7 +675,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -686,23 +686,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-22.10/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-22.10/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-22.10/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-22.10/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -715,23 +715,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-22.10/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-22.10/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-22.10/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-22.10/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -755,63 +755,59 @@ "items": [ { "type": "doc", - "id": "version-22.10/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-migrate" + "id": "graph-views/import-into-map-web" }, { "type": "doc", - "id": "version-22.10/graph-views/import-into-map-web" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-access" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-manage" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-advanced" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-known-issues" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-22.10/graph-views/map-web-troubleshooting" - }, - { - "type": "doc", - "id": "version-22.10/api/map-api" + "id": "api/map-api" } ] } @@ -822,63 +818,63 @@ "items": [ { "type": "doc", - "id": "version-22.10/graph-views/introduction" + "id": "graph-views/introduction" }, { "type": "doc", - "id": "version-22.10/graph-views/install" + "id": "graph-views/install" }, { "type": "doc", - "id": "version-22.10/graph-views/remote-server" + "id": "graph-views/remote-server" }, { "type": "doc", - "id": "version-22.10/graph-views/update" + "id": "graph-views/update" }, { "type": "doc", - "id": "version-22.10/graph-views/upgrade" + "id": "graph-views/upgrade" }, { "type": "doc", - "id": "version-22.10/graph-views/migrate" + "id": "graph-views/migrate" }, { "type": "doc", - "id": "version-22.10/graph-views/configuration" + "id": "graph-views/configuration" }, { "type": "doc", - "id": "version-22.10/graph-views/advanced-configuration" + "id": "graph-views/advanced-configuration" }, { "type": "doc", - "id": "version-22.10/graph-views/create-standard-view" + "id": "graph-views/create-standard-view" }, { "type": "doc", - "id": "version-22.10/graph-views/create-geo-view" + "id": "graph-views/create-geo-view" }, { "type": "doc", - "id": "version-22.10/graph-views/display-view" + "id": "graph-views/display-view" }, { "type": "doc", - "id": "version-22.10/graph-views/share-view" + "id": "graph-views/share-view" }, { "type": "doc", - "id": "version-22.10/graph-views/known-issues" + "id": "graph-views/known-issues" }, { "type": "doc", - "id": "version-22.10/graph-views/troubleshooter" + "id": "graph-views/troubleshooter" }, { "type": "doc", - "id": "version-22.10/api/graph-views-api" + "id": "api/graph-views-api" } ] } @@ -893,7 +889,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -904,27 +900,27 @@ "items": [ { "type": "doc", - "id": "version-22.10/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-22.10/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-22.10/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-22.10/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-22.10/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-22.10/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -937,23 +933,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-22.10/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-22.10/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-22.10/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-22.10/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -975,31 +971,31 @@ "items": [ { "type": "doc", - "id": "version-22.10/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-22.10/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-22.10/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-22.10/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-22.10/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-22.10/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-22.10/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, @@ -1012,23 +1008,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-22.10/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-22.10/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-22.10/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-22.10/connect/autologin" + "id": "connect/autologin" } ] }, @@ -1041,57 +1037,57 @@ "items": [ { "type": "doc", - "id": "version-22.10/administration/centreon-ha/acceptance-guide" + "id": "administration/centreon-ha/acceptance-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/monitoring-guide" + "id": "administration/centreon-ha/monitoring-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/operating-guide" + "id": "administration/centreon-ha/operating-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/troubleshooting-guide" + "id": "administration/centreon-ha/troubleshooting-guide" } ] }, { "type": "doc", - "id": "version-22.10/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-22.10/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-22.10/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "doc", - "id": "version-22.10/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-22.10/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-22.10/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-22.10/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-22.10/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-22.10/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1111,11 +1107,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/update/update-centreon-platform" + "id": "update/update-centreon-platform" }, { "type": "doc", - "id": "version-22.10/update/update-centreon-ha" + "id": "update/update-centreon-ha" } ] }, @@ -1128,71 +1124,71 @@ "items": [ { "type": "doc", - "id": "version-22.10/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-20-04" + "id": "upgrade/upgrade-from-20-04" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-19-10" + "id": "upgrade/upgrade-from-19-10" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-19-04" + "id": "upgrade/upgrade-from-19-04" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-18-10" + "id": "upgrade/upgrade-from-18-10" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-from-3-4" + "id": "upgrade/upgrade-from-3-4" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-centreon-ha-from-20-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-20-04" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-centreon-ha-from-20-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-20-10" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" }, { "type": "doc", - "id": "version-22.10/upgrade/centreon-ha/upgrade-from-centreon-failover" + "id": "upgrade/centreon-ha/upgrade-from-centreon-failover" }, { "type": "doc", - "id": "version-22.10/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1205,31 +1201,31 @@ "items": [ { "type": "doc", - "id": "version-22.10/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-22.10/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-22.10/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-22.10/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-22.10/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-22.10/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-22.10/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1245,7 +1241,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-22.10/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1253,84 +1249,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-22.10/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-22.10/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-22.10/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1339,60 +1335,60 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-22.10/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-iws-isilog" + "id": "integrations/itsm/ot-iws-isilog" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-22.10/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1401,12 +1397,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-22.10/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-22.10/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1419,7 +1415,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1434,7 +1430,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1447,15 +1443,15 @@ "items": [ { "type": "doc", - "id": "version-22.10/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-22.10/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-22.10/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1464,15 +1460,15 @@ }, { "type": "doc", - "id": "version-22.10/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-22.10/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-22.10/api/graph-views-api" + "id": "api/graph-views-api" } ] }, @@ -1485,23 +1481,23 @@ "items": [ { "type": "doc", - "id": "version-22.10/developer/about-developer-resources" + "id": "developer/about-developer-resources" }, { "type": "doc", - "id": "version-22.10/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-22.10/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-22.10/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-22.10/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1512,15 +1508,15 @@ "items": [ { "type": "doc", - "id": "version-22.10/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-22.10/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-22.10/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1533,15 +1529,15 @@ "items": [ { "type": "doc", - "id": "version-22.10/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-22.10/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-22.10/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1556,7 +1552,7 @@ "items": [ { "type": "doc", - "id": "version-22.10/health/helios" + "id": "health/helios" }, { "type": "category", @@ -1567,19 +1563,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/administration/centreon-ha/acceptance-guide" + "id": "administration/centreon-ha/acceptance-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/monitoring-guide" + "id": "administration/centreon-ha/monitoring-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/operating-guide" + "id": "administration/centreon-ha/operating-guide" }, { "type": "doc", - "id": "version-22.10/administration/centreon-ha/troubleshooting-guide" + "id": "administration/centreon-ha/troubleshooting-guide" } ] } @@ -1594,11 +1590,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-22.10/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1609,11 +1605,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-22.10/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1628,11 +1624,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-22.10/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1643,11 +1639,11 @@ "items": [ { "type": "doc", - "id": "version-22.10/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-22.10/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1662,19 +1658,19 @@ "items": [ { "type": "doc", - "id": "version-22.10/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-22.10/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-22.10/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-22.10/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/versioned_sidebars/version-23.04-sidebars.json b/versioned_sidebars/version-23.04-sidebars.json index 3cd2ce70aedb..60c54ebcdbfb 100644 --- a/versioned_sidebars/version-23.04-sidebars.json +++ b/versioned_sidebars/version-23.04-sidebars.json @@ -1,5 +1,5 @@ { - "version-23.04/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,27 +91,27 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-23.04/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-23.04/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-23.04/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-23.04/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-23.04/installation/download" + "id": "installation/download" }, { "type": "category", @@ -122,21 +122,21 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-23.04/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -147,11 +147,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -164,11 +164,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -181,29 +181,29 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-23.04/installation/offline" + "id": "installation/offline" } ] }, @@ -216,11 +216,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-23.04/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -240,19 +240,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-23.04/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-23.04/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-23.04/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -265,23 +265,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -294,23 +294,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -323,27 +323,27 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-23.04/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-23.04/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-23.04/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-23.04/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-23.04/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -356,11 +356,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-23.04/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -373,19 +373,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-23.04/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -398,7 +398,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -411,33 +411,33 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-23.04/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-23.04/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-23.04/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-23.04/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-23.04/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-23.04/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -457,23 +457,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" } ] }, @@ -486,19 +486,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -511,31 +511,31 @@ "items": [ { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -548,11 +548,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-23.04/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -567,27 +567,27 @@ "items": [ { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-23.04/administration/access-control-lists" + "id": "administration/access-control-lists" }, { "type": "doc", - "id": "version-23.04/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" } ] }, @@ -600,23 +600,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-23.04/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-23.04/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-23.04/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-23.04/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -629,7 +629,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -640,23 +640,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-23.04/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-23.04/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-23.04/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-23.04/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -669,23 +669,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-23.04/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-23.04/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-23.04/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-23.04/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -709,63 +709,63 @@ "items": [ { "type": "doc", - "id": "version-23.04/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-migrate" + "id": "graph-views/map-web-migrate" }, { "type": "doc", - "id": "version-23.04/graph-views/import-into-map-web" + "id": "graph-views/import-into-map-web" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-access" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-manage" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-advanced" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-known-issues" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-23.04/graph-views/map-web-troubleshooting" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-23.04/api/map-api" + "id": "api/map-api" } ] } @@ -776,63 +776,63 @@ "items": [ { "type": "doc", - "id": "version-23.04/graph-views/introduction" + "id": "graph-views/introduction" }, { "type": "doc", - "id": "version-23.04/graph-views/install" + "id": "graph-views/install" }, { "type": "doc", - "id": "version-23.04/graph-views/remote-server" + "id": "graph-views/remote-server" }, { "type": "doc", - "id": "version-23.04/graph-views/update" + "id": "graph-views/update" }, { "type": "doc", - "id": "version-23.04/graph-views/upgrade" + "id": "graph-views/upgrade" }, { "type": "doc", - "id": "version-23.04/graph-views/migrate" + "id": "graph-views/migrate" }, { "type": "doc", - "id": "version-23.04/graph-views/configuration" + "id": "graph-views/configuration" }, { "type": "doc", - "id": "version-23.04/graph-views/advanced-configuration" + "id": "graph-views/advanced-configuration" }, { "type": "doc", - "id": "version-23.04/graph-views/create-standard-view" + "id": "graph-views/create-standard-view" }, { "type": "doc", - "id": "version-23.04/graph-views/create-geo-view" + "id": "graph-views/create-geo-view" }, { "type": "doc", - "id": "version-23.04/graph-views/display-view" + "id": "graph-views/display-view" }, { "type": "doc", - "id": "version-23.04/graph-views/share-view" + "id": "graph-views/share-view" }, { "type": "doc", - "id": "version-23.04/graph-views/known-issues" + "id": "graph-views/known-issues" }, { "type": "doc", - "id": "version-23.04/graph-views/troubleshooter" + "id": "graph-views/troubleshooter" }, { "type": "doc", - "id": "version-23.04/api/graph-views-api" + "id": "api/graph-views-api" } ] } @@ -847,7 +847,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -858,27 +858,27 @@ "items": [ { "type": "doc", - "id": "version-23.04/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-23.04/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-23.04/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-23.04/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-23.04/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-23.04/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -891,23 +891,23 @@ "items": [ { "type": "doc", - "id": "version-23.04/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-23.04/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-23.04/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-23.04/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-23.04/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -929,37 +929,37 @@ "items": [ { "type": "doc", - "id": "version-23.04/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-23.04/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-23.04/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-23.04/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-23.04/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-23.04/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-23.04/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, { "type": "doc", - "id": "version-23.04/administration/customize-centreon" + "id": "administration/customize-centreon" }, { "type": "category", @@ -970,41 +970,41 @@ "items": [ { "type": "doc", - "id": "version-23.04/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-23.04/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-23.04/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-23.04/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-23.04/connect/saml" + "id": "connect/saml" }, { "type": "doc", - "id": "version-23.04/connect/autologin" + "id": "connect/autologin" } ] }, { "type": "doc", - "id": "version-23.04/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-23.04/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-23.04/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "category", @@ -1016,33 +1016,33 @@ "items": [ { "type": "doc", - "id": "version-23.04/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-23.04/administration/backup-poller" + "id": "administration/backup-poller" } ] }, { "type": "doc", - "id": "version-23.04/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-23.04/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-23.04/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-23.04/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-23.04/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1062,7 +1062,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/update/update-centreon-platform" + "id": "update/update-centreon-platform" } ] }, @@ -1075,31 +1075,31 @@ "items": [ { "type": "doc", - "id": "version-23.04/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-from-22-10" + "id": "upgrade/upgrade-from-22-10" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-23.04/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1112,31 +1112,31 @@ "items": [ { "type": "doc", - "id": "version-23.04/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-23.04/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-23.04/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-23.04/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-23.04/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-23.04/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-23.04/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1152,7 +1152,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-23.04/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1160,84 +1160,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-23.04/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-23.04/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-23.04/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1246,56 +1246,56 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-23.04/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-23.04/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1304,12 +1304,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-23.04/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-23.04/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1322,7 +1322,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1337,7 +1337,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1350,15 +1350,15 @@ "items": [ { "type": "doc", - "id": "version-23.04/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-23.04/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-23.04/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1367,15 +1367,15 @@ }, { "type": "doc", - "id": "version-23.04/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-23.04/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-23.04/api/graph-views-api" + "id": "api/graph-views-api" } ] }, @@ -1388,19 +1388,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-23.04/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-23.04/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-23.04/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1411,15 +1411,15 @@ "items": [ { "type": "doc", - "id": "version-23.04/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-23.04/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-23.04/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1432,15 +1432,15 @@ "items": [ { "type": "doc", - "id": "version-23.04/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-23.04/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-23.04/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1451,7 +1451,7 @@ "label": "Centreon HA", "link": { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, "items": [ { @@ -1463,15 +1463,15 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha/installation-2-nodes" + "id": "installation/installation-of-centreon-ha/installation-2-nodes" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha/installation-4-nodes" + "id": "installation/installation-of-centreon-ha/installation-4-nodes" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha/integrating-pollers" + "id": "installation/installation-of-centreon-ha/integrating-pollers" } ] }, @@ -1484,15 +1484,15 @@ "items": [ { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-23.04/installation/installation-of-centreon-ha-manual/integrating-pollers" + "id": "installation/installation-of-centreon-ha-manual/integrating-pollers" } ] }, @@ -1505,19 +1505,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/administration/centreon-ha/acceptance-guide" + "id": "administration/centreon-ha/acceptance-guide" }, { "type": "doc", - "id": "version-23.04/administration/centreon-ha/monitoring-guide" + "id": "administration/centreon-ha/monitoring-guide" }, { "type": "doc", - "id": "version-23.04/administration/centreon-ha/operating-guide" + "id": "administration/centreon-ha/operating-guide" }, { "type": "doc", - "id": "version-23.04/administration/centreon-ha/troubleshooting-guide" + "id": "administration/centreon-ha/troubleshooting-guide" } ] }, @@ -1530,7 +1530,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/update/update-centreon-ha" + "id": "update/update-centreon-ha" } ] }, @@ -1543,19 +1543,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" }, { "type": "doc", - "id": "version-23.04/upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" }, { "type": "doc", - "id": "version-23.04/upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" }, { "type": "doc", - "id": "version-23.04/upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" } ] } @@ -1570,7 +1570,7 @@ "items": [ { "type": "doc", - "id": "version-23.04/health/helios" + "id": "health/helios" } ] }, @@ -1583,11 +1583,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-23.04/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1598,11 +1598,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-23.04/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1617,11 +1617,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-23.04/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1632,11 +1632,11 @@ "items": [ { "type": "doc", - "id": "version-23.04/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-23.04/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1651,19 +1651,19 @@ "items": [ { "type": "doc", - "id": "version-23.04/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-23.04/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-23.04/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-23.04/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/versioned_sidebars/version-23.10-sidebars.json b/versioned_sidebars/version-23.10-sidebars.json index 098ee90adefb..64c782c5ec4e 100644 --- a/versioned_sidebars/version-23.10-sidebars.json +++ b/versioned_sidebars/version-23.10-sidebars.json @@ -1,5 +1,5 @@ { - "version-23.10/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,27 +91,27 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-23.10/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-23.10/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-23.10/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-23.10/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-23.10/installation/download" + "id": "installation/download" }, { "type": "category", @@ -122,21 +122,21 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-23.10/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -147,11 +147,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -164,11 +164,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -181,29 +181,29 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-23.10/installation/offline" + "id": "installation/offline" } ] }, @@ -216,11 +216,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-23.10/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -240,19 +240,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-23.10/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-23.10/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-23.10/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -265,23 +265,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -294,23 +294,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -323,27 +323,27 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-23.10/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-23.10/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-23.10/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-23.10/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-23.10/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -356,11 +356,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-23.10/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -373,19 +373,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-23.10/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -398,7 +398,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -411,33 +411,33 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-23.10/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-23.10/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-23.10/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-23.10/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-23.10/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-23.10/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -457,27 +457,27 @@ "items": [ { "type": "doc", - "id": "version-23.10/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/dashboards" + "id": "alerts-notifications/dashboards" } ] }, @@ -490,19 +490,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -515,31 +515,31 @@ "items": [ { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -552,11 +552,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-23.10/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -571,27 +571,27 @@ "items": [ { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-23.10/administration/access-control-lists" + "id": "administration/access-control-lists" }, { "type": "doc", - "id": "version-23.10/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" } ] }, @@ -604,23 +604,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-23.10/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-23.10/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-23.10/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-23.10/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -633,7 +633,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -644,23 +644,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-23.10/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-23.10/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-23.10/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-23.10/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -673,23 +673,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-23.10/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-23.10/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-23.10/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-23.10/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -713,63 +713,63 @@ "items": [ { "type": "doc", - "id": "version-23.10/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-migrate" + "id": "graph-views/map-web-migrate" }, { "type": "doc", - "id": "version-23.10/graph-views/import-into-map-web" + "id": "graph-views/import-into-map-web" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-access" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-manage" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-advanced" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-known-issues" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-23.10/graph-views/map-web-troubleshooting" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-23.10/api/map-api" + "id": "api/map-api" } ] } @@ -780,63 +780,63 @@ "items": [ { "type": "doc", - "id": "version-23.10/graph-views/introduction" + "id": "graph-views/introduction" }, { "type": "doc", - "id": "version-23.10/graph-views/install" + "id": "graph-views/install" }, { "type": "doc", - "id": "version-23.10/graph-views/remote-server" + "id": "graph-views/remote-server" }, { "type": "doc", - "id": "version-23.10/graph-views/update" + "id": "graph-views/update" }, { "type": "doc", - "id": "version-23.10/graph-views/upgrade" + "id": "graph-views/upgrade" }, { "type": "doc", - "id": "version-23.10/graph-views/migrate" + "id": "graph-views/migrate" }, { "type": "doc", - "id": "version-23.10/graph-views/configuration" + "id": "graph-views/configuration" }, { "type": "doc", - "id": "version-23.10/graph-views/advanced-configuration" + "id": "graph-views/advanced-configuration" }, { "type": "doc", - "id": "version-23.10/graph-views/create-standard-view" + "id": "graph-views/create-standard-view" }, { "type": "doc", - "id": "version-23.10/graph-views/create-geo-view" + "id": "graph-views/create-geo-view" }, { "type": "doc", - "id": "version-23.10/graph-views/display-view" + "id": "graph-views/display-view" }, { "type": "doc", - "id": "version-23.10/graph-views/share-view" + "id": "graph-views/share-view" }, { "type": "doc", - "id": "version-23.10/graph-views/known-issues" + "id": "graph-views/known-issues" }, { "type": "doc", - "id": "version-23.10/graph-views/troubleshooter" + "id": "graph-views/troubleshooter" }, { "type": "doc", - "id": "version-23.10/api/graph-views-api" + "id": "api/graph-views-api" } ] } @@ -851,7 +851,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -862,27 +862,27 @@ "items": [ { "type": "doc", - "id": "version-23.10/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-23.10/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-23.10/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-23.10/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-23.10/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-23.10/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -895,23 +895,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-23.10/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-23.10/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-23.10/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-23.10/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -933,37 +933,37 @@ "items": [ { "type": "doc", - "id": "version-23.10/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-23.10/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-23.10/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-23.10/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-23.10/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-23.10/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-23.10/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, { "type": "doc", - "id": "version-23.10/administration/customize-centreon" + "id": "administration/customize-centreon" }, { "type": "category", @@ -974,41 +974,41 @@ "items": [ { "type": "doc", - "id": "version-23.10/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-23.10/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-23.10/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-23.10/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-23.10/connect/saml" + "id": "connect/saml" }, { "type": "doc", - "id": "version-23.10/connect/autologin" + "id": "connect/autologin" } ] }, { "type": "doc", - "id": "version-23.10/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-23.10/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-23.10/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "category", @@ -1020,33 +1020,33 @@ "items": [ { "type": "doc", - "id": "version-23.10/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-23.10/administration/backup-poller" + "id": "administration/backup-poller" } ] }, { "type": "doc", - "id": "version-23.10/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-23.10/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-23.10/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-23.10/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-23.10/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1066,7 +1066,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/update/update-centreon-platform" + "id": "update/update-centreon-platform" } ] }, @@ -1079,35 +1079,35 @@ "items": [ { "type": "doc", - "id": "version-23.10/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-23-04" + "id": "upgrade/upgrade-from-23-04" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-22-10" + "id": "upgrade/upgrade-from-22-10" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-23.10/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1120,31 +1120,31 @@ "items": [ { "type": "doc", - "id": "version-23.10/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-23.10/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-23.10/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-23.10/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-23.10/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-23.10/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-23.10/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1160,7 +1160,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-23.10/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1168,84 +1168,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-23.10/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-23.10/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-23.10/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1254,60 +1254,60 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-23.10/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-easyvista-rest-api" + "id": "integrations/itsm/ot-easyvista-rest-api" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-23.10/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1316,12 +1316,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-23.10/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-23.10/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1334,7 +1334,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1349,7 +1349,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1362,15 +1362,15 @@ "items": [ { "type": "doc", - "id": "version-23.10/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-23.10/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-23.10/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1379,15 +1379,15 @@ }, { "type": "doc", - "id": "version-23.10/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-23.10/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-23.10/api/graph-views-api" + "id": "api/graph-views-api" } ] }, @@ -1400,19 +1400,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-23.10/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-23.10/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-23.10/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1423,15 +1423,15 @@ "items": [ { "type": "doc", - "id": "version-23.10/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-23.10/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-23.10/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1444,15 +1444,15 @@ "items": [ { "type": "doc", - "id": "version-23.10/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-23.10/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-23.10/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1463,7 +1463,7 @@ "label": "Centreon HA", "link": { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, "items": [ { @@ -1475,15 +1475,15 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha/installation-2-nodes" + "id": "installation/installation-of-centreon-ha/installation-2-nodes" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha/installation-4-nodes" + "id": "installation/installation-of-centreon-ha/installation-4-nodes" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha/integrating-pollers" + "id": "installation/installation-of-centreon-ha/integrating-pollers" } ] }, @@ -1496,15 +1496,15 @@ "items": [ { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-2-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" + "id": "installation/installation-of-centreon-ha-manual/centreon-ha-4-nodes-installation-manual-failover" }, { "type": "doc", - "id": "version-23.10/installation/installation-of-centreon-ha-manual/integrating-pollers" + "id": "installation/installation-of-centreon-ha-manual/integrating-pollers" } ] }, @@ -1517,19 +1517,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/administration/centreon-ha/acceptance-guide" + "id": "administration/centreon-ha/acceptance-guide" }, { "type": "doc", - "id": "version-23.10/administration/centreon-ha/monitoring-guide" + "id": "administration/centreon-ha/monitoring-guide" }, { "type": "doc", - "id": "version-23.10/administration/centreon-ha/operating-guide" + "id": "administration/centreon-ha/operating-guide" }, { "type": "doc", - "id": "version-23.10/administration/centreon-ha/troubleshooting-guide" + "id": "administration/centreon-ha/troubleshooting-guide" } ] }, @@ -1542,7 +1542,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/update/update-centreon-ha" + "id": "update/update-centreon-ha" } ] }, @@ -1555,23 +1555,23 @@ "items": [ { "type": "doc", - "id": "version-23.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" }, { "type": "doc", - "id": "version-23.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" }, { "type": "doc", - "id": "version-23.10/upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" }, { "type": "doc", - "id": "version-23.10/upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" }, { "type": "doc", - "id": "version-23.10/upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" } ] } @@ -1586,7 +1586,7 @@ "items": [ { "type": "doc", - "id": "version-23.10/health/helios" + "id": "health/helios" } ] }, @@ -1599,11 +1599,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-23.10/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1614,11 +1614,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-23.10/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1633,11 +1633,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-23.10/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1648,11 +1648,11 @@ "items": [ { "type": "doc", - "id": "version-23.10/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-23.10/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1667,19 +1667,19 @@ "items": [ { "type": "doc", - "id": "version-23.10/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-23.10/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-23.10/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-23.10/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/versioned_sidebars/version-24.04-sidebars.json b/versioned_sidebars/version-24.04-sidebars.json index b684346e746e..455b301345b9 100644 --- a/versioned_sidebars/version-24.04-sidebars.json +++ b/versioned_sidebars/version-24.04-sidebars.json @@ -1,5 +1,5 @@ { - "version-24.04/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,31 +91,31 @@ "items": [ { "type": "doc", - "id": "version-24.04/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-24.04/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-24.04/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-24.04/installation/inside-centreon" + "id": "installation/inside-centreon" }, { "type": "doc", - "id": "version-24.04/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-24.04/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-24.04/installation/download" + "id": "installation/download" }, { "type": "category", @@ -126,21 +126,21 @@ "items": [ { "type": "doc", - "id": "version-24.04/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-24.04/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-24.04/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-24.04/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -151,11 +151,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-24.04/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -168,11 +168,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-24.04/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -185,29 +185,29 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-24.04/installation/offline" + "id": "installation/offline" } ] }, @@ -220,11 +220,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-24.04/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -244,19 +244,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-24.04/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-24.04/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-24.04/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -269,23 +269,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -298,23 +298,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -327,27 +327,27 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-24.04/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-24.04/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-24.04/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-24.04/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-24.04/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -360,11 +360,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-24.04/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -377,19 +377,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-24.04/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -402,7 +402,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -415,33 +415,33 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-24.04/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-24.04/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-24.04/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-24.04/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-24.04/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-24.04/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -461,19 +461,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" } ] }, @@ -486,19 +486,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -511,31 +511,31 @@ "items": [ { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -548,11 +548,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-24.04/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -567,27 +567,27 @@ "items": [ { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-24.04/administration/access-control-lists" + "id": "administration/access-control-lists" }, { "type": "doc", - "id": "version-24.04/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" } ] }, @@ -600,7 +600,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -611,23 +611,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-24.04/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-24.04/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-24.04/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-24.04/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -640,23 +640,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-24.04/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-24.04/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-24.04/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-24.04/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -671,7 +671,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/alerts-notifications/dashboards" + "id": "alerts-notifications/dashboards" }, { "type": "category", @@ -682,23 +682,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-24.04/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-24.04/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-24.04/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-24.04/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -720,63 +720,63 @@ "items": [ { "type": "doc", - "id": "version-24.04/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-migrate" + "id": "graph-views/map-web-migrate" }, { "type": "doc", - "id": "version-24.04/graph-views/import-into-map-web" + "id": "graph-views/import-into-map-web" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-access" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-manage" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-advanced" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-known-issues" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-24.04/graph-views/map-web-troubleshooting" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-24.04/api/map-api" + "id": "api/map-api" } ] }, @@ -786,63 +786,63 @@ "items": [ { "type": "doc", - "id": "version-24.04/graph-views/introduction" + "id": "graph-views/introduction" }, { "type": "doc", - "id": "version-24.04/graph-views/install" + "id": "graph-views/install" }, { "type": "doc", - "id": "version-24.04/graph-views/remote-server" + "id": "graph-views/remote-server" }, { "type": "doc", - "id": "version-24.04/graph-views/update" + "id": "graph-views/update" }, { "type": "doc", - "id": "version-24.04/graph-views/upgrade" + "id": "graph-views/upgrade" }, { "type": "doc", - "id": "version-24.04/graph-views/migrate" + "id": "graph-views/migrate" }, { "type": "doc", - "id": "version-24.04/graph-views/configuration" + "id": "graph-views/configuration" }, { "type": "doc", - "id": "version-24.04/graph-views/advanced-configuration" + "id": "graph-views/advanced-configuration" }, { "type": "doc", - "id": "version-24.04/graph-views/create-standard-view" + "id": "graph-views/create-standard-view" }, { "type": "doc", - "id": "version-24.04/graph-views/create-geo-view" + "id": "graph-views/create-geo-view" }, { "type": "doc", - "id": "version-24.04/graph-views/display-view" + "id": "graph-views/display-view" }, { "type": "doc", - "id": "version-24.04/graph-views/share-view" + "id": "graph-views/share-view" }, { "type": "doc", - "id": "version-24.04/graph-views/known-issues" + "id": "graph-views/known-issues" }, { "type": "doc", - "id": "version-24.04/graph-views/troubleshooter" + "id": "graph-views/troubleshooter" }, { "type": "doc", - "id": "version-24.04/api/graph-views-api" + "id": "api/graph-views-api" } ] } @@ -850,7 +850,7 @@ }, { "type": "doc", - "id": "version-24.04/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" } ] }, @@ -863,7 +863,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -874,27 +874,27 @@ "items": [ { "type": "doc", - "id": "version-24.04/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-24.04/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-24.04/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-24.04/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-24.04/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-24.04/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -907,23 +907,23 @@ "items": [ { "type": "doc", - "id": "version-24.04/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-24.04/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-24.04/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-24.04/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-24.04/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -945,37 +945,37 @@ "items": [ { "type": "doc", - "id": "version-24.04/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-24.04/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-24.04/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-24.04/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-24.04/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-24.04/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-24.04/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, { "type": "doc", - "id": "version-24.04/administration/customize-centreon" + "id": "administration/customize-centreon" }, { "type": "category", @@ -986,41 +986,41 @@ "items": [ { "type": "doc", - "id": "version-24.04/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-24.04/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-24.04/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-24.04/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-24.04/connect/saml" + "id": "connect/saml" }, { "type": "doc", - "id": "version-24.04/connect/autologin" + "id": "connect/autologin" } ] }, { "type": "doc", - "id": "version-24.04/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-24.04/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-24.04/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "category", @@ -1032,33 +1032,33 @@ "items": [ { "type": "doc", - "id": "version-24.04/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-24.04/administration/backup-poller" + "id": "administration/backup-poller" } ] }, { "type": "doc", - "id": "version-24.04/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-24.04/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-24.04/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-24.04/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-24.04/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1078,7 +1078,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/update/update-centreon-platform" + "id": "update/update-centreon-platform" } ] }, @@ -1091,39 +1091,39 @@ "items": [ { "type": "doc", - "id": "version-24.04/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-23-10" + "id": "upgrade/upgrade-from-23-10" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-23-04" + "id": "upgrade/upgrade-from-23-04" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-22-10" + "id": "upgrade/upgrade-from-22-10" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-24.04/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1136,31 +1136,31 @@ "items": [ { "type": "doc", - "id": "version-24.04/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-24.04/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-24.04/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-24.04/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-24.04/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-24.04/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-24.04/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1176,7 +1176,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-24.04/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1184,84 +1184,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-24.04/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-24.04/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-24.04/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1270,60 +1270,60 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-24.04/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-easyvista-rest-api" + "id": "integrations/itsm/ot-easyvista-rest-api" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-24.04/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1332,12 +1332,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-24.04/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-24.04/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1350,7 +1350,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1365,7 +1365,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1378,15 +1378,15 @@ "items": [ { "type": "doc", - "id": "version-24.04/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-24.04/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-24.04/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1395,19 +1395,19 @@ }, { "type": "doc", - "id": "version-24.04/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-24.04/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-24.04/api/graph-views-api" + "id": "api/graph-views-api" }, { "type": "doc", - "id": "version-24.04/api/api-tokens" + "id": "api/api-tokens" } ] }, @@ -1420,19 +1420,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-24.04/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-24.04/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-24.04/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1444,15 +1444,15 @@ "items": [ { "type": "doc", - "id": "version-24.04/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-24.04/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-24.04/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1466,15 +1466,15 @@ "items": [ { "type": "doc", - "id": "version-24.04/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-24.04/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-24.04/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1485,7 +1485,7 @@ "label": "Centreon HA", "link": { "type": "doc", - "id": "version-24.04/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, "items": [ { @@ -1497,27 +1497,27 @@ "items": [ { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-23-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-10" }, { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" }, { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" }, { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" }, { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" }, { "type": "doc", - "id": "version-24.04/upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" } ] } @@ -1532,7 +1532,7 @@ "items": [ { "type": "doc", - "id": "version-24.04/health/helios" + "id": "health/helios" } ] }, @@ -1545,11 +1545,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-24.04/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1560,11 +1560,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-24.04/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1579,11 +1579,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-24.04/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1594,11 +1594,11 @@ "items": [ { "type": "doc", - "id": "version-24.04/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-24.04/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1613,19 +1613,19 @@ "items": [ { "type": "doc", - "id": "version-24.04/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-24.04/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-24.04/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-24.04/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/versioned_sidebars/version-24.10-sidebars.json b/versioned_sidebars/version-24.10-sidebars.json index 624250c09ff4..1f5f75621c35 100644 --- a/versioned_sidebars/version-24.10-sidebars.json +++ b/versioned_sidebars/version-24.10-sidebars.json @@ -1,5 +1,5 @@ { - "version-24.10/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,31 +91,31 @@ "items": [ { "type": "doc", - "id": "version-24.10/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-24.10/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-24.10/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-24.10/installation/inside-centreon" + "id": "installation/inside-centreon" }, { "type": "doc", - "id": "version-24.10/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-24.10/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-24.10/installation/download" + "id": "installation/download" }, { "type": "category", @@ -126,21 +126,21 @@ "items": [ { "type": "doc", - "id": "version-24.10/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-24.10/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-24.10/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-24.10/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -151,11 +151,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-24.10/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -168,11 +168,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-24.10/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -185,29 +185,29 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-24.10/installation/offline" + "id": "installation/offline" } ] }, @@ -220,11 +220,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-24.10/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -244,19 +244,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-24.10/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-24.10/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-24.10/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -269,23 +269,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -298,23 +298,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -327,27 +327,27 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-24.10/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-24.10/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-24.10/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-24.10/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-24.10/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -360,11 +360,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-24.10/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -377,19 +377,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-24.10/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -402,7 +402,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -415,33 +415,33 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-24.10/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-24.10/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-24.10/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-24.10/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-24.10/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-24.10/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -461,19 +461,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" } ] @@ -487,19 +487,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -512,31 +512,31 @@ "items": [ { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -549,11 +549,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-24.10/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -568,27 +568,27 @@ "items": [ { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-24.10/administration/access-control-lists" + "id": "administration/access-control-lists" }, { "type": "doc", - "id": "version-24.10/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" } ] }, @@ -601,7 +601,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -612,23 +612,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-24.10/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-24.10/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-24.10/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-24.10/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -641,23 +641,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-24.10/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-24.10/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-24.10/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-24.10/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -672,7 +672,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/alerts-notifications/dashboards" + "id": "alerts-notifications/dashboards" }, { "type": "category", @@ -683,23 +683,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-24.10/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-24.10/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-24.10/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-24.10/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -713,7 +713,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "category", @@ -724,81 +724,81 @@ "items":[ { "type": "doc", - "id": "version-24.10/graph-views/map-legacy-eol" + "id": "graph-views/map-legacy-eol" }, { "type": "doc", - "id": "version-24.10/graph-views/upgrading-map-legacy" + "id": "graph-views/upgrading-map-legacy" }, { "type": "doc", - "id": "version-24.10/graph-views/import-into-map-web" + "id": "graph-views/import-into-map-web" } ] }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-access" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-manage" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-migrate" + "id": "graph-views/map-web-migrate" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-advanced-configuration" + "id": "graph-views/map-web-advanced-configuration" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-advanced" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-known-issues" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-24.10/graph-views/map-web-troubleshooting" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-24.10/api/map-api" + "id": "api/map-api" } ] } , { "type": "doc", - "id": "version-24.10/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" } ] }, @@ -811,7 +811,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -822,27 +822,27 @@ "items": [ { "type": "doc", - "id": "version-24.10/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-24.10/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-24.10/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-24.10/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-24.10/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-24.10/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -855,23 +855,23 @@ "items": [ { "type": "doc", - "id": "version-24.10/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-24.10/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-24.10/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-24.10/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-24.10/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -893,37 +893,37 @@ "items": [ { "type": "doc", - "id": "version-24.10/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-24.10/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-24.10/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-24.10/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-24.10/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-24.10/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-24.10/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, { "type": "doc", - "id": "version-24.10/administration/customize-centreon" + "id": "administration/customize-centreon" }, { "type": "category", @@ -934,41 +934,41 @@ "items": [ { "type": "doc", - "id": "version-24.10/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-24.10/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-24.10/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-24.10/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-24.10/connect/saml" + "id": "connect/saml" }, { "type": "doc", - "id": "version-24.10/connect/autologin" + "id": "connect/autologin" } ] }, { "type": "doc", - "id": "version-24.10/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-24.10/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-24.10/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "category", @@ -980,33 +980,33 @@ "items": [ { "type": "doc", - "id": "version-24.10/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-24.10/administration/backup-poller" + "id": "administration/backup-poller" } ] }, { "type": "doc", - "id": "version-24.10/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-24.10/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-24.10/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-24.10/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-24.10/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1026,7 +1026,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/update/update-centreon-platform" + "id": "update/update-centreon-platform" } ] }, @@ -1039,43 +1039,43 @@ "items": [ { "type": "doc", - "id": "version-24.10/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-24-04" + "id": "upgrade/upgrade-from-24-04" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-23-10" + "id": "upgrade/upgrade-from-23-10" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-23-04" + "id": "upgrade/upgrade-from-23-04" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-22-10" + "id": "upgrade/upgrade-from-22-10" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-24.10/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1088,35 +1088,35 @@ "items": [ { "type": "doc", - "id": "version-24.10/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-24.10/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-24.10/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-24.10/migrate/migrate-from-debian-to-debian" + "id": "migrate/migrate-from-debian-to-debian" }, { "type": "doc", - "id": "version-24.10/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-24.10/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-24.10/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-24.10/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1132,7 +1132,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-24.10/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1140,84 +1140,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-24.10/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-24.10/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-24.10/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1226,60 +1226,60 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-24.10/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-easyvista-rest-api" + "id": "integrations/itsm/ot-easyvista-rest-api" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-24.10/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1288,12 +1288,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-24.10/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-24.10/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1306,7 +1306,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1321,7 +1321,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1334,15 +1334,15 @@ "items": [ { "type": "doc", - "id": "version-24.10/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-24.10/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-24.10/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1351,15 +1351,15 @@ }, { "type": "doc", - "id": "version-24.10/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-24.10/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-24.10/api/api-tokens" + "id": "api/api-tokens" } ] }, @@ -1372,19 +1372,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-24.10/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-24.10/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-24.10/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1396,15 +1396,15 @@ "items": [ { "type": "doc", - "id": "version-24.10/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-24.10/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-24.10/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1418,15 +1418,15 @@ "items": [ { "type": "doc", - "id": "version-24.10/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-24.10/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-24.10/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1434,7 +1434,7 @@ }, { "type": "doc", - "id": "version-24.10/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, { "type": "category", @@ -1445,7 +1445,7 @@ "items": [ { "type": "doc", - "id": "version-24.10/health/helios" + "id": "health/helios" } ] }, @@ -1458,11 +1458,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-24.10/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1473,11 +1473,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-24.10/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1492,11 +1492,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-24.10/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1507,11 +1507,11 @@ "items": [ { "type": "doc", - "id": "version-24.10/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-24.10/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1526,19 +1526,19 @@ "items": [ { "type": "doc", - "id": "version-24.10/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-24.10/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-24.10/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-24.10/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/versioned_sidebars/version-25.10-sidebars.json b/versioned_sidebars/version-25.10-sidebars.json index 9a4354cda32d..fdeac5e641b5 100644 --- a/versioned_sidebars/version-25.10-sidebars.json +++ b/versioned_sidebars/version-25.10-sidebars.json @@ -1,5 +1,5 @@ { - "version-25.10/docs": [ + "docs": [ { "collapsed": true, "type": "category", @@ -91,31 +91,31 @@ "items": [ { "type": "doc", - "id": "version-25.10/installation/introduction" + "id": "installation/introduction" }, { "type": "doc", - "id": "version-25.10/installation/compatibility" + "id": "installation/compatibility" }, { "type": "doc", - "id": "version-25.10/installation/architectures" + "id": "installation/architectures" }, { "type": "doc", - "id": "version-25.10/installation/inside-centreon" + "id": "installation/inside-centreon" }, { "type": "doc", - "id": "version-25.10/installation/prerequisites" + "id": "installation/prerequisites" }, { "type": "doc", - "id": "version-25.10/installation/technical" + "id": "installation/technical" }, { "type": "doc", - "id": "version-25.10/installation/download" + "id": "installation/download" }, { "type": "category", @@ -126,21 +126,21 @@ "items": [ { "type": "doc", - "id": "version-25.10/installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", - "id": "version-25.10/installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "version-25.10/installation/installation-of-a-central-server/using-virtual-machines" + "id": "installation/installation-of-a-central-server/using-virtual-machines" } ] }, { "type": "doc", - "id": "version-25.10/installation/web-and-post-installation" + "id": "installation/web-and-post-installation" }, { "type": "category", @@ -151,11 +151,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "version-25.10/installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/unattended-install-poller" } ] }, @@ -168,11 +168,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/installation/installation-of-a-remote-server/using-packages" + "id": "installation/installation-of-a-remote-server/using-packages" }, { "type": "doc", - "id": "version-25.10/installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/unattended-install-remote" } ] }, @@ -185,29 +185,29 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/add-a-poller-to-configuration" + "id": "monitoring/monitoring-servers/add-a-poller-to-configuration" }, { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/add-a-remote-server-to-configuration" + "id": "monitoring/monitoring-servers/add-a-remote-server-to-configuration" }, { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/communications" + "id": "monitoring/monitoring-servers/communications" }, { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/move-poller" + "id": "monitoring/monitoring-servers/move-poller" }, { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/advanced-configuration" + "id": "monitoring/monitoring-servers/advanced-configuration" } ] }, { "type": "doc", - "id": "version-25.10/installation/offline" + "id": "installation/offline" } ] }, @@ -220,11 +220,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/administration/secure-platform" + "id": "administration/secure-platform" }, { "type": "doc", - "id": "version-25.10/graph-views/secure-your-map-platform" + "id": "graph-views/secure-your-map-platform" } ] }, @@ -244,19 +244,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/about" + "id": "monitoring/about" }, { "type": "doc", - "id": "version-25.10/monitoring/metrics" + "id": "monitoring/metrics" }, { "type": "doc", - "id": "version-25.10/monitoring/pluginpacks" + "id": "monitoring/pluginpacks" }, { "type": "doc", - "id": "version-25.10/monitoring/monitoring-servers/deploying-a-configuration" + "id": "monitoring/monitoring-servers/deploying-a-configuration" } ] }, @@ -269,23 +269,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/hosts-create" + "id": "monitoring/basic-objects/hosts-create" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/hosts" + "id": "monitoring/basic-objects/hosts" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/hosts-create-disco" + "id": "monitoring/basic-objects/hosts-create-disco" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/hosts-templates" + "id": "monitoring/basic-objects/hosts-templates" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/hosts-switch-poller" + "id": "monitoring/basic-objects/hosts-switch-poller" } ] }, @@ -298,23 +298,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/services-create" + "id": "monitoring/basic-objects/services-create" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/services" + "id": "monitoring/basic-objects/services" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/services-create-disco" + "id": "monitoring/basic-objects/services-create-disco" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/services-templates" + "id": "monitoring/basic-objects/services-templates" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/meta-services" + "id": "monitoring/basic-objects/meta-services" } ] }, @@ -327,27 +327,27 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/discovery/introduction" + "id": "monitoring/discovery/introduction" }, { "type": "doc", - "id": "version-25.10/monitoring/discovery/installation" + "id": "monitoring/discovery/installation" }, { "type": "doc", - "id": "version-25.10/monitoring/discovery/hosts-discovery" + "id": "monitoring/discovery/hosts-discovery" }, { "type": "doc", - "id": "version-25.10/monitoring/discovery/services-discovery" + "id": "monitoring/discovery/services-discovery" }, { "type": "doc", - "id": "version-25.10/monitoring/discovery/administration" + "id": "monitoring/discovery/administration" }, { "type": "doc", - "id": "version-25.10/monitoring/discovery/troubleshooting-hosts-discovery" + "id": "monitoring/discovery/troubleshooting-hosts-discovery" } ] }, @@ -360,11 +360,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/groups" + "id": "monitoring/groups" }, { "type": "doc", - "id": "version-25.10/monitoring/categories" + "id": "monitoring/categories" } ] }, @@ -377,19 +377,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/timeperiods" + "id": "monitoring/basic-objects/timeperiods" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/macros" + "id": "monitoring/basic-objects/macros" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/commands" + "id": "monitoring/basic-objects/commands" }, { "type": "doc", - "id": "version-25.10/monitoring/generic-actions" + "id": "monitoring/generic-actions" } ] }, @@ -402,7 +402,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/anomaly-detection" + "id": "monitoring/anomaly-detection" } ] }, @@ -415,33 +415,33 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/passive-monitoring/enable-snmp-traps" + "id": "monitoring/passive-monitoring/enable-snmp-traps" }, { "type": "doc", - "id": "version-25.10/monitoring/passive-monitoring/create-snmp-traps-definitions" + "id": "monitoring/passive-monitoring/create-snmp-traps-definitions" }, { "type": "doc", - "id": "version-25.10/monitoring/passive-monitoring/monitoring-with-snmp-traps" + "id": "monitoring/passive-monitoring/monitoring-with-snmp-traps" }, { "type": "doc", - "id": "version-25.10/monitoring/passive-monitoring/debug-snmp-traps-management" + "id": "monitoring/passive-monitoring/debug-snmp-traps-management" }, { "type": "doc", - "id": "version-25.10/monitoring/passive-monitoring/dsm" + "id": "monitoring/passive-monitoring/dsm" } ] }, { "type": "doc", - "id": "version-25.10/monitoring/event-handler" + "id": "monitoring/event-handler" }, { "type": "doc", - "id": "version-25.10/monitoring/web-import-export" + "id": "monitoring/web-import-export" } ] }, @@ -461,19 +461,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/alerts-notifications/concepts" + "id": "alerts-notifications/concepts" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/resources-status" + "id": "alerts-notifications/resources-status" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/event-console" + "id": "alerts-notifications/event-console" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/event-log" + "id": "alerts-notifications/event-log" } ] @@ -487,19 +487,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/alerts-notifications/acknowledge" + "id": "alerts-notifications/acknowledge" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/downtimes" + "id": "alerts-notifications/downtimes" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/submit" + "id": "alerts-notifications/submit" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/other" + "id": "alerts-notifications/other" } ] }, @@ -512,31 +512,31 @@ "items": [ { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-concept" + "id": "alerts-notifications/notif-concept" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-configuration" + "id": "alerts-notifications/notif-configuration" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-config-for-teams" + "id": "alerts-notifications/notif-config-for-teams" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-dependencies" + "id": "alerts-notifications/notif-dependencies" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-escalation" + "id": "alerts-notifications/notif-escalation" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-flapping" + "id": "alerts-notifications/notif-flapping" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/notif-advanced" + "id": "alerts-notifications/notif-advanced" } ] }, @@ -549,11 +549,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/alerts-notifications/ticketing-install" + "id": "alerts-notifications/ticketing-install" }, { "type": "doc", - "id": "version-25.10/alerts-notifications/ticketing" + "id": "alerts-notifications/ticketing" } ] } @@ -568,27 +568,27 @@ "items": [ { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/contacts" + "id": "monitoring/basic-objects/contacts" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/contacts-create" + "id": "monitoring/basic-objects/contacts-create" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/contacts-templates" + "id": "monitoring/basic-objects/contacts-templates" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/contacts-groups" + "id": "monitoring/basic-objects/contacts-groups" }, { "type": "doc", - "id": "version-25.10/administration/access-control-lists" + "id": "administration/access-control-lists" }, { "type": "doc", - "id": "version-25.10/monitoring/basic-objects/customization" + "id": "monitoring/basic-objects/customization" } ] }, @@ -601,7 +601,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/service-mapping/introduction" + "id": "service-mapping/introduction" }, { "type": "category", @@ -612,23 +612,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/service-mapping/ba-management" + "id": "service-mapping/ba-management" }, { "type": "doc", - "id": "version-25.10/service-mapping/ba-monitoring" + "id": "service-mapping/ba-monitoring" }, { "type": "doc", - "id": "version-25.10/service-mapping/ba-reporting" + "id": "service-mapping/ba-reporting" }, { "type": "doc", - "id": "version-25.10/service-mapping/ba-settings" + "id": "service-mapping/ba-settings" }, { "type": "doc", - "id": "version-25.10/service-mapping/widgets" + "id": "service-mapping/widgets" } ] }, @@ -641,23 +641,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/service-mapping/install" + "id": "service-mapping/install" }, { "type": "doc", - "id": "version-25.10/service-mapping/update" + "id": "service-mapping/update" }, { "type": "doc", - "id": "version-25.10/service-mapping/upgrade" + "id": "service-mapping/upgrade" }, { "type": "doc", - "id": "version-25.10/service-mapping/migrate" + "id": "service-mapping/migrate" }, { "type": "doc", - "id": "version-25.10/service-mapping/remote-server" + "id": "service-mapping/remote-server" } ] } @@ -672,7 +672,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/alerts-notifications/dashboards" + "id": "alerts-notifications/dashboards" }, { "type": "category", @@ -683,23 +683,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/metrology/chart-management" + "id": "metrology/chart-management" }, { "type": "doc", - "id": "version-25.10/metrology/chart-template" + "id": "metrology/chart-template" }, { "type": "doc", - "id": "version-25.10/metrology/chart-curves" + "id": "metrology/chart-curves" }, { "type": "doc", - "id": "version-25.10/metrology/chart-virtual-metrics" + "id": "metrology/chart-virtual-metrics" }, { "type": "doc", - "id": "version-25.10/metrology/grafana" + "id": "metrology/grafana" } ] }, @@ -713,7 +713,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/graph-views/introduction-map" + "id": "graph-views/introduction-map" }, { "type": "category", @@ -724,81 +724,81 @@ "items":[ { "type": "doc", - "id": "version-25.10/graph-views/map-legacy-eol" + "id": "graph-views/map-legacy-eol" }, { "type": "doc", - "id": "version-25.10/graph-views/upgrading-map-legacy" + "id": "graph-views/upgrading-map-legacy" }, { "type": "doc", - "id": "version-25.10/graph-views/import-into-map-web" + "id": "graph-views/import-into-map-web" } ] }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-install" + "id": "graph-views/map-web-install" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-install-remote" + "id": "graph-views/map-web-install-remote" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-update" + "id": "graph-views/map-web-update" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-upgrade" + "id": "graph-views/map-web-upgrade" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-access" + "id": "graph-views/map-web-access" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-manage" + "id": "graph-views/map-web-manage" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-create-standard-map" + "id": "graph-views/map-web-create-standard-map" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-create-geoview" + "id": "graph-views/map-web-create-geoview" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-migrate" + "id": "graph-views/map-web-migrate" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-advanced-configuration" + "id": "graph-views/map-web-advanced-configuration" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-advanced" + "id": "graph-views/map-web-advanced" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-known-issues" + "id": "graph-views/map-web-known-issues" }, { "type": "doc", - "id": "version-25.10/graph-views/map-web-troubleshooting" + "id": "graph-views/map-web-troubleshooting" }, { "type": "doc", - "id": "version-25.10/api/map-api" + "id": "api/map-api" } ] } , { "type": "doc", - "id": "version-25.10/alerts-notifications/custom-views" + "id": "alerts-notifications/custom-views" } ] }, @@ -811,7 +811,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/reporting/introduction" + "id": "reporting/introduction" }, { "type": "category", @@ -822,27 +822,27 @@ "items": [ { "type": "doc", - "id": "version-25.10/reporting/manage-reports" + "id": "reporting/manage-reports" }, { "type": "doc", - "id": "version-25.10/reporting/reports" + "id": "reporting/reports" }, { "type": "doc", - "id": "version-25.10/reporting/widgets" + "id": "reporting/widgets" }, { "type": "doc", - "id": "version-25.10/reporting/configure" + "id": "reporting/configure" }, { "type": "doc", - "id": "version-25.10/reporting/concepts" + "id": "reporting/concepts" }, { "type": "doc", - "id": "version-25.10/reporting/report-development" + "id": "reporting/report-development" } ] }, @@ -855,23 +855,23 @@ "items": [ { "type": "doc", - "id": "version-25.10/reporting/installation" + "id": "reporting/installation" }, { "type": "doc", - "id": "version-25.10/reporting/update" + "id": "reporting/update" }, { "type": "doc", - "id": "version-25.10/reporting/upgrade" + "id": "reporting/upgrade" }, { "type": "doc", - "id": "version-25.10/reporting/migrate" + "id": "reporting/migrate" }, { "type": "doc", - "id": "version-25.10/reporting/backup-restore" + "id": "reporting/backup-restore" } ] } @@ -893,37 +893,37 @@ "items": [ { "type": "doc", - "id": "version-25.10/administration/parameters/centreon-ui" + "id": "administration/parameters/centreon-ui" }, { "type": "doc", - "id": "version-25.10/administration/parameters/monitoring" + "id": "administration/parameters/monitoring" }, { "type": "doc", - "id": "version-25.10/administration/parameters/gorgone" + "id": "administration/parameters/gorgone" }, { "type": "doc", - "id": "version-25.10/administration/parameters/rrdtool" + "id": "administration/parameters/rrdtool" }, { "type": "doc", - "id": "version-25.10/administration/parameters/debug" + "id": "administration/parameters/debug" }, { "type": "doc", - "id": "version-25.10/administration/parameters/data-management" + "id": "administration/parameters/data-management" }, { "type": "doc", - "id": "version-25.10/administration/parameters/medias" + "id": "administration/parameters/medias" } ] }, { "type": "doc", - "id": "version-25.10/administration/customize-centreon" + "id": "administration/customize-centreon" }, { "type": "category", @@ -934,41 +934,41 @@ "items": [ { "type": "doc", - "id": "version-25.10/connect/loginpwd" + "id": "connect/loginpwd" }, { "type": "doc", - "id": "version-25.10/administration/parameters/ldap" + "id": "administration/parameters/ldap" }, { "type": "doc", - "id": "version-25.10/connect/sso" + "id": "connect/sso" }, { "type": "doc", - "id": "version-25.10/connect/openid" + "id": "connect/openid" }, { "type": "doc", - "id": "version-25.10/connect/saml" + "id": "connect/saml" }, { "type": "doc", - "id": "version-25.10/connect/autologin" + "id": "connect/autologin" } ] }, { "type": "doc", - "id": "version-25.10/administration/extensions" + "id": "administration/extensions" }, { "type": "doc", - "id": "version-25.10/administration/licenses" + "id": "administration/licenses" }, { "type": "doc", - "id": "version-25.10/administration/database-partitioning" + "id": "administration/database-partitioning" }, { "type": "category", @@ -980,33 +980,33 @@ "items": [ { "type": "doc", - "id": "version-25.10/administration/backup" + "id": "administration/backup" }, { "type": "doc", - "id": "version-25.10/administration/backup-poller" + "id": "administration/backup-poller" } ] }, { "type": "doc", - "id": "version-25.10/administration/knowledge-base" + "id": "administration/knowledge-base" }, { "type": "doc", - "id": "version-25.10/administration/logging-configuration-changes" + "id": "administration/logging-configuration-changes" }, { "type": "doc", - "id": "version-25.10/administration/platform-statistics" + "id": "administration/platform-statistics" }, { "type": "doc", - "id": "version-25.10/administration/postfix" + "id": "administration/postfix" }, { "type": "doc", - "id": "version-25.10/administration/sql-proxy" + "id": "administration/sql-proxy" } ] }, @@ -1026,7 +1026,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/update/update-centreon-platform" + "id": "update/update-centreon-platform" } ] }, @@ -1039,43 +1039,43 @@ "items": [ { "type": "doc", - "id": "version-25.10/upgrade/introduction" + "id": "upgrade/introduction" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-24-04" + "id": "upgrade/upgrade-from-24-04" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-23-10" + "id": "upgrade/upgrade-from-23-10" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-23-04" + "id": "upgrade/upgrade-from-23-04" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-22-10" + "id": "upgrade/upgrade-from-22-10" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-22-04" + "id": "upgrade/upgrade-from-22-04" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-21-10" + "id": "upgrade/upgrade-from-21-10" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-21-04" + "id": "upgrade/upgrade-from-21-04" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-from-20-10" + "id": "upgrade/upgrade-from-20-10" }, { "type": "doc", - "id": "version-25.10/upgrade/upgrade-mariadb" + "id": "upgrade/upgrade-mariadb" } ] }, @@ -1088,31 +1088,31 @@ "items": [ { "type": "doc", - "id": "version-25.10/migrate/introduction" + "id": "migrate/introduction" }, { "type": "doc", - "id": "version-25.10/migrate/migrate-from-el-to-el" + "id": "migrate/migrate-from-el-to-el" }, { "type": "doc", - "id": "version-25.10/migrate/migrate-from-el-to-debian" + "id": "migrate/migrate-from-el-to-debian" }, { "type": "doc", - "id": "version-25.10/migrate/migrate-from-3-4" + "id": "migrate/migrate-from-3-4" }, { "type": "doc", - "id": "version-25.10/migrate/nagios-to-centreon" + "id": "migrate/nagios-to-centreon" }, { "type": "doc", - "id": "version-25.10/migrate/poller-display-to-remote-server" + "id": "migrate/poller-display-to-remote-server" }, { "type": "doc", - "id": "version-25.10/developer/developer-gorgone-migrate-from-centcore" + "id": "developer/developer-gorgone-migrate-from-centcore" } ] } @@ -1128,7 +1128,7 @@ "label": "Integrations", "link": { "type": "doc", - "id": "version-25.10/integrations/introduction-integrations" + "id": "integrations/introduction-integrations" }, "items": [ { @@ -1136,84 +1136,84 @@ "label": "Stream connectors", "link": { "type": "doc", - "id": "version-25.10/integrations/stream-connectors" + "id": "integrations/stream-connectors" }, "items": [ { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-hp-bsm" + "id": "integrations/event-management/sc-hp-bsm" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-canopsis-events" + "id": "integrations/data-analytics/sc-canopsis-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-clickhouse" + "id": "integrations/data-analytics/sc-clickhouse" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-datadog-events" + "id": "integrations/data-analytics/sc-datadog-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-datadog-metrics" + "id": "integrations/data-analytics/sc-datadog-metrics" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-elastic-events" + "id": "integrations/data-analytics/sc-elastic-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-elastic-metrics" + "id": "integrations/data-analytics/sc-elastic-metrics" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-hp-omi" + "id": "integrations/event-management/sc-hp-omi" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-influxdb2-metrics" + "id": "integrations/data-analytics/sc-influxdb2-metrics" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-kafka-events" + "id": "integrations/data-analytics/sc-kafka-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-logstash-events" + "id": "integrations/data-analytics/sc-logstash-events" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-opsgenie" + "id": "integrations/event-management/sc-opsgenie" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-pagerduty-events" + "id": "integrations/event-management/sc-pagerduty-events" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-service-now-em-events" + "id": "integrations/event-management/sc-service-now-em-events" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-service-now-incident-events" + "id": "integrations/event-management/sc-service-now-incident-events" }, { "type": "doc", - "id": "version-25.10/integrations/event-management/sc-signl4-events" + "id": "integrations/event-management/sc-signl4-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-splunk-events" + "id": "integrations/data-analytics/sc-splunk-events" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-splunk-metrics" + "id": "integrations/data-analytics/sc-splunk-metrics" }, { "type": "doc", - "id": "version-25.10/integrations/data-analytics/sc-warp10" + "id": "integrations/data-analytics/sc-warp10" } ] }, @@ -1222,60 +1222,60 @@ "label": "ITSM", "link": { "type": "doc", - "id": "version-25.10/integrations/itsm/itsm-overview" + "id": "integrations/itsm/itsm-overview" }, "items": [ { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-bmc-footprints" + "id": "integrations/itsm/ot-bmc-footprints" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-bmc-remedy" + "id": "integrations/itsm/ot-bmc-remedy" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-easyvista" + "id": "integrations/itsm/ot-easyvista" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-easyvista-rest-api" + "id": "integrations/itsm/ot-easyvista-rest-api" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-glpi" + "id": "integrations/itsm/ot-glpi" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-glpi-restapi" + "id": "integrations/itsm/ot-glpi-restapi" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-itop" + "id": "integrations/itsm/ot-itop" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-jira" + "id": "integrations/itsm/ot-jira" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-mail" + "id": "integrations/itsm/ot-mail" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-otrs-restapi" + "id": "integrations/itsm/ot-otrs-restapi" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-request-tracker-restapi" + "id": "integrations/itsm/ot-request-tracker-restapi" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-serena" + "id": "integrations/itsm/ot-serena" }, { "type": "doc", - "id": "version-25.10/integrations/itsm/ot-servicenow" + "id": "integrations/itsm/ot-servicenow" } ] }, @@ -1284,12 +1284,12 @@ "label": "Notifications", "link": { "type": "doc", - "id": "version-25.10/integrations/notifications/notifications-overview" + "id": "integrations/notifications/notifications-overview" }, "items": [ { "type": "doc", - "id": "version-25.10/integrations/notifications/plugin-telegram" + "id": "integrations/notifications/plugin-telegram" } ] }, @@ -1302,7 +1302,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/integrations/npm/ntopng" + "id": "integrations/npm/ntopng" } ] } @@ -1317,7 +1317,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/mobile/introduction" + "id": "mobile/introduction" } ] }, @@ -1330,15 +1330,15 @@ "items": [ { "type": "doc", - "id": "version-25.10/api/introduction" + "id": "api/introduction" }, { "type": "doc", - "id": "version-25.10/api/clapi" + "id": "api/clapi" }, { "type": "doc", - "id": "version-25.10/api/rest-api-v1" + "id": "api/rest-api-v1" }, { "type": "link", @@ -1347,15 +1347,15 @@ }, { "type": "doc", - "id": "version-25.10/api/rest-api-v2" + "id": "api/rest-api-v2" }, { "type": "doc", - "id": "version-25.10/api/map-api" + "id": "api/map-api" }, { "type": "doc", - "id": "version-25.10/api/api-tokens" + "id": "api/api-tokens" } ] }, @@ -1368,19 +1368,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/developer/developer-stream-connector" + "id": "developer/developer-stream-connector" }, { "type": "doc", - "id": "version-25.10/developer/developer-broker-stream-connector-migration" + "id": "developer/developer-broker-stream-connector-migration" }, { "type": "doc", - "id": "version-25.10/developer/developer-translate-centreon" + "id": "developer/developer-translate-centreon" }, { "type": "doc", - "id": "version-25.10/developer/developer-widget" + "id": "developer/developer-widget" }, { "type": "category", @@ -1392,15 +1392,15 @@ "items": [ { "type": "doc", - "id": "version-25.10/developer/developer-broker-stream-connector" + "id": "developer/developer-broker-stream-connector" }, { "type": "doc", - "id": "version-25.10/developer/developer-broker-bbdo" + "id": "developer/developer-broker-bbdo" }, { "type": "doc", - "id": "version-25.10/developer/developer-broker-mapping" + "id": "developer/developer-broker-mapping" } ] }, @@ -1414,15 +1414,15 @@ "items": [ { "type": "doc", - "id": "version-25.10/developer/developer-gorgone-client-server-communication" + "id": "developer/developer-gorgone-client-server-communication" }, { "type": "doc", - "id": "version-25.10/developer/developer-gorgone-pull-mode" + "id": "developer/developer-gorgone-pull-mode" }, { "type": "doc", - "id": "version-25.10/developer/developer-gorgone-rebound-mode" + "id": "developer/developer-gorgone-rebound-mode" } ] } @@ -1433,7 +1433,7 @@ "label": "Centreon HA", "link": { "type": "doc", - "id": "version-25.10/installation/installation-of-centreon-ha/overview" + "id": "installation/installation-of-centreon-ha/overview" }, "items": [ { @@ -1445,27 +1445,27 @@ "items": [ { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-23-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-10" }, { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" }, { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" }, { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" }, { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" }, { "type": "doc", - "id": "version-25.10/upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" } ] } @@ -1480,7 +1480,7 @@ "items": [ { "type": "doc", - "id": "version-25.10/health/helios" + "id": "health/helios" } ] }, @@ -1493,11 +1493,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/releases/introduction" + "id": "releases/introduction" }, { "type": "doc", - "id": "version-25.10/releases/lifecycle" + "id": "releases/lifecycle" }, { "type": "category", @@ -1508,11 +1508,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/releases/centreon-os" + "id": "releases/centreon-os" }, { "type": "doc", - "id": "version-25.10/releases/centreon-commercial-extensions" + "id": "releases/centreon-commercial-extensions" } ] } @@ -1527,11 +1527,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/security/security" + "id": "security/security" }, { "type": "doc", - "id": "version-25.10/security/key-rotation" + "id": "security/key-rotation" }, { "type": "category", @@ -1542,11 +1542,11 @@ "items": [ { "type": "doc", - "id": "version-25.10/security/user-data-storage/gdpr-compliance" + "id": "security/user-data-storage/gdpr-compliance" }, { "type": "doc", - "id": "version-25.10/security/user-data-storage/what-is-centreon-ceip" + "id": "security/user-data-storage/what-is-centreon-ceip" } ] } @@ -1561,19 +1561,19 @@ "items": [ { "type": "doc", - "id": "version-25.10/resources/known-issues" + "id": "resources/known-issues" }, { "type": "doc", - "id": "version-25.10/resources/troubleshooting" + "id": "resources/troubleshooting" }, { "type": "doc", - "id": "version-25.10/resources/glossary" + "id": "resources/glossary" }, { "type": "doc", - "id": "version-25.10/resources/contribute" + "id": "resources/contribute" } ] } diff --git a/yarn.lock b/yarn.lock deleted file mode 100644 index 4cb0db060268..000000000000 --- a/yarn.lock +++ /dev/null @@ -1,8235 +0,0 @@ -# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY. -# yarn lockfile v1 - - -"@algolia/autocomplete-core@1.17.6": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-core/-/autocomplete-core-1.17.6.tgz#63f4c2f21a215cb9968611f51a82d6017cd690df" - integrity sha512-lkDoW4I7h2kKlIgf3pUt1LqvxyYKkVyiypoGLlUnhPSnCpmeOwudM6rNq6YYsCmdQtnDQoW5lUNNuj6ASg3qeg== - dependencies: - "@algolia/autocomplete-plugin-algolia-insights" "1.17.6" - "@algolia/autocomplete-shared" "1.17.6" - -"@algolia/autocomplete-core@1.9.3": - version "1.9.3" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-core/-/autocomplete-core-1.9.3.tgz#1d56482a768c33aae0868c8533049e02e8961be7" - integrity sha512-009HdfugtGCdC4JdXUbVJClA0q0zh24yyePn+KUGk3rP7j8FEe/m5Yo/z65gn6nP/cM39PxpzqKrL7A6fP6PPw== - dependencies: - "@algolia/autocomplete-plugin-algolia-insights" "1.9.3" - "@algolia/autocomplete-shared" "1.9.3" - -"@algolia/autocomplete-js@^1.8.2": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-js/-/autocomplete-js-1.17.6.tgz#92cd8eff6097263fd18be58662a9145df9e997ef" - integrity sha512-V1OWF6ilykKBWy390s2RYU8E5gutHL3BBPHkeOZ5rZAaMlo0CxF/khl7sbjZ4aoZ8pGNGj4Ac+9VHM7Vc47SOQ== - dependencies: - "@algolia/autocomplete-core" "1.17.6" - "@algolia/autocomplete-preset-algolia" "1.17.6" - "@algolia/autocomplete-shared" "1.17.6" - htm "^3.1.1" - preact "^10.13.2" - -"@algolia/autocomplete-plugin-algolia-insights@1.17.6": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-plugin-algolia-insights/-/autocomplete-plugin-algolia-insights-1.17.6.tgz#ff760852769e9f27a70f48f2c4e111fc93fd64e5" - integrity sha512-17NnaacuFzSWVuZu4NKzVeaFIe9Abpw8w+/gjc7xhZFtqj+GadufzodIdchwiB2eM2cDdiR3icW7gbNTB3K2YA== - dependencies: - "@algolia/autocomplete-shared" "1.17.6" - -"@algolia/autocomplete-plugin-algolia-insights@1.9.3": - version "1.9.3" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-plugin-algolia-insights/-/autocomplete-plugin-algolia-insights-1.9.3.tgz#9b7f8641052c8ead6d66c1623d444cbe19dde587" - integrity sha512-a/yTUkcO/Vyy+JffmAnTWbr4/90cLzw+CC3bRbhnULr/EM0fGNvM13oQQ14f2moLMcVDyAx/leczLlAOovhSZg== - dependencies: - "@algolia/autocomplete-shared" "1.9.3" - -"@algolia/autocomplete-preset-algolia@1.17.6": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-preset-algolia/-/autocomplete-preset-algolia-1.17.6.tgz#465b652bff5c262aad4da2488d78629cfa906be6" - integrity sha512-Cvg5JENdSCMuClwhJ1ON1/jSuojaYMiUW2KePm18IkdCzPJj/NXojaOxw58RFtQFpJgfVW8h2E8mEoDtLlMdeA== - dependencies: - "@algolia/autocomplete-shared" "1.17.6" - -"@algolia/autocomplete-preset-algolia@1.9.3": - version "1.9.3" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-preset-algolia/-/autocomplete-preset-algolia-1.9.3.tgz#64cca4a4304cfcad2cf730e83067e0c1b2f485da" - integrity sha512-d4qlt6YmrLMYy95n5TB52wtNDr6EgAIPH81dvvvW8UmuWRgxEtY0NJiPwl/h95JtG2vmRM804M0DSwMCNZlzRA== - dependencies: - "@algolia/autocomplete-shared" "1.9.3" - -"@algolia/autocomplete-shared@1.17.6": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-shared/-/autocomplete-shared-1.17.6.tgz#ad951632b6d477d4ba9a68a347e1702d26009d58" - integrity sha512-aq/3V9E00Tw2GC/PqgyPGXtqJUlVc17v4cn1EUhSc+O/4zd04Uwb3UmPm8KDaYQQOrkt1lwvCj2vG2wRE5IKhw== - -"@algolia/autocomplete-shared@1.9.3": - version "1.9.3" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-shared/-/autocomplete-shared-1.9.3.tgz#2e22e830d36f0a9cf2c0ccd3c7f6d59435b77dfa" - integrity sha512-Wnm9E4Ye6Rl6sTTqjoymD+l8DjSTHsHboVRYrKgEt8Q7UHm9nYbqhN/i0fhUYA3OAEH7WA8x3jfpnmJm3rKvaQ== - -"@algolia/autocomplete-theme-classic@^1.8.2": - version "1.17.6" - resolved "https://registry.yarnpkg.com/@algolia/autocomplete-theme-classic/-/autocomplete-theme-classic-1.17.6.tgz#a0a9825eeaa8a95dc34c7adb38686595107eed41" - integrity sha512-A1nOHqoL91G3arHU0cnzIFOw2nnVGoK/fMMndB5jSLMcLbJBjDbgdwGrT2FcAct83tAobvLmWTe0etQnktotgw== - -"@algolia/cache-browser-local-storage@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.24.0.tgz#97bc6d067a9fd932b9c922faa6b7fd6e546e1348" - integrity sha512-t63W9BnoXVrGy9iYHBgObNXqYXM3tYXCjDSHeNwnsc324r4o5UiVKUiAB4THQ5z9U5hTj6qUvwg/Ez43ZD85ww== - dependencies: - "@algolia/cache-common" "4.24.0" - -"@algolia/cache-common@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/cache-common/-/cache-common-4.24.0.tgz#81a8d3a82ceb75302abb9b150a52eba9960c9744" - integrity sha512-emi+v+DmVLpMGhp0V9q9h5CdkURsNmFC+cOS6uK9ndeJm9J4TiqSvPYVu+THUP8P/S08rxf5x2P+p3CfID0Y4g== - -"@algolia/cache-in-memory@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/cache-in-memory/-/cache-in-memory-4.24.0.tgz#ffcf8872f3a10cb85c4f4641bdffd307933a6e44" - integrity sha512-gDrt2so19jW26jY3/MkFg5mEypFIPbPoXsQGQWAi6TrCPsNOSEYepBMPlucqWigsmEy/prp5ug2jy/N3PVG/8w== - dependencies: - "@algolia/cache-common" "4.24.0" - -"@algolia/client-account@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/client-account/-/client-account-4.24.0.tgz#eba7a921d828e7c8c40a32d4add21206c7fe12f1" - integrity sha512-adcvyJ3KjPZFDybxlqnf+5KgxJtBjwTPTeyG2aOyoJvx0Y8dUQAEOEVOJ/GBxX0WWNbmaSrhDURMhc+QeevDsA== - dependencies: - "@algolia/client-common" "4.24.0" - "@algolia/client-search" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/client-analytics@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/client-analytics/-/client-analytics-4.24.0.tgz#9d2576c46a9093a14e668833c505ea697a1a3e30" - integrity sha512-y8jOZt1OjwWU4N2qr8G4AxXAzaa8DBvyHTWlHzX/7Me1LX8OayfgHexqrsL4vSBcoMmVw2XnVW9MhL+Y2ZDJXg== - dependencies: - "@algolia/client-common" "4.24.0" - "@algolia/client-search" "4.24.0" - "@algolia/requester-common" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/client-common@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/client-common/-/client-common-4.24.0.tgz#77c46eee42b9444a1d1c1583a83f7df4398a649d" - integrity sha512-bc2ROsNL6w6rqpl5jj/UywlIYC21TwSSoFHKl01lYirGMW+9Eek6r02Tocg4gZ8HAw3iBvu6XQiM3BEbmEMoiA== - dependencies: - "@algolia/requester-common" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/client-personalization@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/client-personalization/-/client-personalization-4.24.0.tgz#8b47789fb1cb0f8efbea0f79295b7c5a3850f6ae" - integrity sha512-l5FRFm/yngztweU0HdUzz1rC4yoWCFo3IF+dVIVTfEPg906eZg5BOd1k0K6rZx5JzyyoP4LdmOikfkfGsKVE9w== - dependencies: - "@algolia/client-common" "4.24.0" - "@algolia/requester-common" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/client-search@4.24.0", "@algolia/client-search@^4.12.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/client-search/-/client-search-4.24.0.tgz#75e6c02d33ef3e0f34afd9962c085b856fc4a55f" - integrity sha512-uRW6EpNapmLAD0mW47OXqTP8eiIx5F6qN9/x/7HHO6owL3N1IXqydGwW5nhDFBrV+ldouro2W1VX3XlcUXEFCA== - dependencies: - "@algolia/client-common" "4.24.0" - "@algolia/requester-common" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/events@^4.0.1": - version "4.0.1" - resolved "https://registry.yarnpkg.com/@algolia/events/-/events-4.0.1.tgz#fd39e7477e7bc703d7f893b556f676c032af3950" - integrity sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ== - -"@algolia/logger-common@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/logger-common/-/logger-common-4.24.0.tgz#28d439976019ec0a46ba7a1a739ef493d4ef8123" - integrity sha512-LLUNjkahj9KtKYrQhFKCzMx0BY3RnNP4FEtO+sBybCjJ73E8jNdaKJ/Dd8A/VA4imVHP5tADZ8pn5B8Ga/wTMA== - -"@algolia/logger-console@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/logger-console/-/logger-console-4.24.0.tgz#c6ff486036cd90b81d07a95aaba04461da7e1c65" - integrity sha512-X4C8IoHgHfiUROfoRCV+lzSy+LHMgkoEEU1BbKcsfnV0i0S20zyy0NLww9dwVHUWNfPPxdMU+/wKmLGYf96yTg== - dependencies: - "@algolia/logger-common" "4.24.0" - -"@algolia/recommend@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/recommend/-/recommend-4.24.0.tgz#8a3f78aea471ee0a4836b78fd2aad4e9abcaaf34" - integrity sha512-P9kcgerfVBpfYHDfVZDvvdJv0lEoCvzNlOy2nykyt5bK8TyieYyiD0lguIJdRZZYGre03WIAFf14pgE+V+IBlw== - dependencies: - "@algolia/cache-browser-local-storage" "4.24.0" - "@algolia/cache-common" "4.24.0" - "@algolia/cache-in-memory" "4.24.0" - "@algolia/client-common" "4.24.0" - "@algolia/client-search" "4.24.0" - "@algolia/logger-common" "4.24.0" - "@algolia/logger-console" "4.24.0" - "@algolia/requester-browser-xhr" "4.24.0" - "@algolia/requester-common" "4.24.0" - "@algolia/requester-node-http" "4.24.0" - "@algolia/transporter" "4.24.0" - -"@algolia/requester-browser-xhr@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.24.0.tgz#313c5edab4ed73a052e75803855833b62dd19c16" - integrity sha512-Z2NxZMb6+nVXSjF13YpjYTdvV3032YTBSGm2vnYvYPA6mMxzM3v5rsCiSspndn9rzIW4Qp1lPHBvuoKJV6jnAA== - dependencies: - "@algolia/requester-common" "4.24.0" - -"@algolia/requester-common@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/requester-common/-/requester-common-4.24.0.tgz#1c60c198031f48fcdb9e34c4057a3ea987b9a436" - integrity sha512-k3CXJ2OVnvgE3HMwcojpvY6d9kgKMPRxs/kVohrwF5WMr2fnqojnycZkxPoEg+bXm8fi5BBfFmOqgYztRtHsQA== - -"@algolia/requester-node-http@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/requester-node-http/-/requester-node-http-4.24.0.tgz#4461593714031d02aa7da221c49df675212f482f" - integrity sha512-JF18yTjNOVYvU/L3UosRcvbPMGT9B+/GQWNWnenIImglzNVGpyzChkXLnrSf6uxwVNO6ESGu6oN8MqcGQcjQJw== - dependencies: - "@algolia/requester-common" "4.24.0" - -"@algolia/transporter@4.24.0": - version "4.24.0" - resolved "https://registry.yarnpkg.com/@algolia/transporter/-/transporter-4.24.0.tgz#226bb1f8af62430374c1972b2e5c8580ab275102" - integrity sha512-86nI7w6NzWxd1Zp9q3413dRshDqAzSbsQjhcDhPIatEFiZrL1/TjnHL8S7jVKFePlIMzDsZWXAXwXzcok9c5oA== - dependencies: - "@algolia/cache-common" "4.24.0" - "@algolia/logger-common" "4.24.0" - "@algolia/requester-common" "4.24.0" - -"@ampproject/remapping@^2.2.0": - version "2.3.0" - resolved "https://registry.yarnpkg.com/@ampproject/remapping/-/remapping-2.3.0.tgz#ed441b6fa600072520ce18b43d2c8cc8caecc7f4" - integrity sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw== - dependencies: - "@jridgewell/gen-mapping" "^0.3.5" - "@jridgewell/trace-mapping" "^0.3.24" - -"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.10.4", "@babel/code-frame@^7.16.0", "@babel/code-frame@^7.25.7", "@babel/code-frame@^7.8.3": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.25.7.tgz#438f2c524071531d643c6f0188e1e28f130cebc7" - integrity sha512-0xZJFNE5XMpENsgfHYTw8FbX4kv53mFLn2i3XPoq69LyhYSCBJtitaHx9QnsVTrsogI4Z3+HtEfZ2/GFPOtf5g== - dependencies: - "@babel/highlight" "^7.25.7" - picocolors "^1.0.0" - -"@babel/compat-data@^7.22.6", "@babel/compat-data@^7.25.7", "@babel/compat-data@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.25.8.tgz#0376e83df5ab0eb0da18885c0140041f0747a402" - integrity sha512-ZsysZyXY4Tlx+Q53XdnOFmqwfB9QDTHYxaZYajWRoBLuLEAwI2UIbtxOjWh/cFaa9IKUlcB+DDuoskLuKu56JA== - -"@babel/core@7.12.9": - version "7.12.9" - resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.12.9.tgz#fd450c4ec10cdbb980e2928b7aa7a28484593fc8" - integrity sha512-gTXYh3M5wb7FRXQy+FErKFAv90BnlOuNn1QkCK2lREoPAjrQCO49+HVSrFoe5uakFAF5eenS75KbO2vQiLrTMQ== - dependencies: - "@babel/code-frame" "^7.10.4" - "@babel/generator" "^7.12.5" - "@babel/helper-module-transforms" "^7.12.1" - "@babel/helpers" "^7.12.5" - "@babel/parser" "^7.12.7" - "@babel/template" "^7.12.7" - "@babel/traverse" "^7.12.9" - "@babel/types" "^7.12.7" - convert-source-map "^1.7.0" - debug "^4.1.0" - gensync "^1.0.0-beta.1" - json5 "^2.1.2" - lodash "^4.17.19" - resolve "^1.3.2" - semver "^5.4.1" - source-map "^0.5.0" - -"@babel/core@^7.18.6", "@babel/core@^7.19.6", "@babel/core@^7.21.3": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.25.8.tgz#a57137d2a51bbcffcfaeba43cb4dd33ae3e0e1c6" - integrity sha512-Oixnb+DzmRT30qu9d3tJSQkxuygWm32DFykT4bRoORPa9hZ/L4KhVB/XiRm6KG+roIEM7DBQlmg27kw2HZkdZg== - dependencies: - "@ampproject/remapping" "^2.2.0" - "@babel/code-frame" "^7.25.7" - "@babel/generator" "^7.25.7" - "@babel/helper-compilation-targets" "^7.25.7" - "@babel/helper-module-transforms" "^7.25.7" - "@babel/helpers" "^7.25.7" - "@babel/parser" "^7.25.8" - "@babel/template" "^7.25.7" - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.8" - convert-source-map "^2.0.0" - debug "^4.1.0" - gensync "^1.0.0-beta.2" - json5 "^2.2.3" - semver "^6.3.1" - -"@babel/generator@^7.12.5", "@babel/generator@^7.18.7", "@babel/generator@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.25.7.tgz#de86acbeb975a3e11ee92dd52223e6b03b479c56" - integrity sha512-5Dqpl5fyV9pIAD62yK9P7fcA768uVPUyrQmqpqstHWgMma4feF1x/oFysBCVZLY5wJ2GkMUCdsNDnGZrPoR6rA== - dependencies: - "@babel/types" "^7.25.7" - "@jridgewell/gen-mapping" "^0.3.5" - "@jridgewell/trace-mapping" "^0.3.25" - jsesc "^3.0.2" - -"@babel/helper-annotate-as-pure@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.25.7.tgz#63f02dbfa1f7cb75a9bdb832f300582f30bb8972" - integrity sha512-4xwU8StnqnlIhhioZf1tqnVWeQ9pvH/ujS8hRfw/WOza+/a+1qv69BWNy+oY231maTCWgKWhfBU7kDpsds6zAA== - dependencies: - "@babel/types" "^7.25.7" - -"@babel/helper-builder-binary-assignment-operator-visitor@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.25.7.tgz#d721650c1f595371e0a23ee816f1c3c488c0d622" - integrity sha512-12xfNeKNH7jubQNm7PAkzlLwEmCs1tfuX3UjIw6vP6QXi+leKh6+LyC/+Ed4EIQermwd58wsyh070yjDHFlNGg== - dependencies: - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helper-compilation-targets@^7.22.6", "@babel/helper-compilation-targets@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.25.7.tgz#11260ac3322dda0ef53edfae6e97b961449f5fa4" - integrity sha512-DniTEax0sv6isaw6qSQSfV4gVRNtw2rte8HHM45t9ZR0xILaufBRNkpMifCRiAPyvL4ACD6v0gfCwCmtOQaV4A== - dependencies: - "@babel/compat-data" "^7.25.7" - "@babel/helper-validator-option" "^7.25.7" - browserslist "^4.24.0" - lru-cache "^5.1.1" - semver "^6.3.1" - -"@babel/helper-create-class-features-plugin@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.25.7.tgz#5d65074c76cae75607421c00d6bd517fe1892d6b" - integrity sha512-bD4WQhbkx80mAyj/WCm4ZHcF4rDxkoLFO6ph8/5/mQ3z4vAzltQXAmbc7GvVJx5H+lk5Mi5EmbTeox5nMGCsbw== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-member-expression-to-functions" "^7.25.7" - "@babel/helper-optimise-call-expression" "^7.25.7" - "@babel/helper-replace-supers" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - "@babel/traverse" "^7.25.7" - semver "^6.3.1" - -"@babel/helper-create-regexp-features-plugin@^7.18.6", "@babel/helper-create-regexp-features-plugin@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.25.7.tgz#dcb464f0e2cdfe0c25cc2a0a59c37ab940ce894e" - integrity sha512-byHhumTj/X47wJ6C6eLpK7wW/WBEcnUeb7D0FNc/jFQnQVw7DOso3Zz5u9x/zLrFVkHa89ZGDbkAa1D54NdrCQ== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - regexpu-core "^6.1.1" - semver "^6.3.1" - -"@babel/helper-define-polyfill-provider@^0.6.2": - version "0.6.2" - resolved "https://registry.yarnpkg.com/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.6.2.tgz#18594f789c3594acb24cfdb4a7f7b7d2e8bd912d" - integrity sha512-LV76g+C502biUK6AyZ3LK10vDpDyCzZnhZFXkH1L75zHPj68+qc8Zfpx2th+gzwA2MzyK+1g/3EPl62yFnVttQ== - dependencies: - "@babel/helper-compilation-targets" "^7.22.6" - "@babel/helper-plugin-utils" "^7.22.5" - debug "^4.1.1" - lodash.debounce "^4.0.8" - resolve "^1.14.2" - -"@babel/helper-member-expression-to-functions@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.25.7.tgz#541a33b071f0355a63a0fa4bdf9ac360116b8574" - integrity sha512-O31Ssjd5K6lPbTX9AAYpSKrZmLeagt9uwschJd+Ixo6QiRyfpvgtVQp8qrDR9UNFjZ8+DO34ZkdrN+BnPXemeA== - dependencies: - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helper-module-imports@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.25.7.tgz#dba00d9523539152906ba49263e36d7261040472" - integrity sha512-o0xCgpNmRohmnoWKQ0Ij8IdddjyBFE4T2kagL/x6M3+4zUgc+4qTOUBoNe4XxDskt1HPKO007ZPiMgLDq2s7Kw== - dependencies: - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helper-module-transforms@^7.12.1", "@babel/helper-module-transforms@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.25.7.tgz#2ac9372c5e001b19bc62f1fe7d96a18cb0901d1a" - integrity sha512-k/6f8dKG3yDz/qCwSM+RKovjMix563SLxQFo0UhRNo239SP6n9u5/eLtKD6EAjwta2JHJ49CsD8pms2HdNiMMQ== - dependencies: - "@babel/helper-module-imports" "^7.25.7" - "@babel/helper-simple-access" "^7.25.7" - "@babel/helper-validator-identifier" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/helper-optimise-call-expression@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.25.7.tgz#1de1b99688e987af723eed44fa7fc0ee7b97d77a" - integrity sha512-VAwcwuYhv/AT+Vfr28c9y6SHzTan1ryqrydSTFGjU0uDJHw3uZ+PduI8plCLkRsDnqK2DMEDmwrOQRsK/Ykjng== - dependencies: - "@babel/types" "^7.25.7" - -"@babel/helper-plugin-utils@7.10.4": - version "7.10.4" - resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.10.4.tgz#2f75a831269d4f677de49986dff59927533cf375" - integrity sha512-O4KCvQA6lLiMU9l2eawBPMf1xPP8xPfB3iEQw150hOVTqj/rfXz0ThTb4HEzqQfs2Bmo5Ay8BzxfzVtBrr9dVg== - -"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.10.4", "@babel/helper-plugin-utils@^7.18.6", "@babel/helper-plugin-utils@^7.22.5", "@babel/helper-plugin-utils@^7.25.7", "@babel/helper-plugin-utils@^7.8.0": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.25.7.tgz#8ec5b21812d992e1ef88a9b068260537b6f0e36c" - integrity sha512-eaPZai0PiqCi09pPs3pAFfl/zYgGaE6IdXtYvmf0qlcDTd3WCtO7JWCcRd64e0EQrcYgiHibEZnOGsSY4QSgaw== - -"@babel/helper-remap-async-to-generator@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.25.7.tgz#9efdc39df5f489bcd15533c912b6c723a0a65021" - integrity sha512-kRGE89hLnPfcz6fTrlNU+uhgcwv0mBE4Gv3P9Ke9kLVJYpi4AMVVEElXvB5CabrPZW4nCM8P8UyyjrzCM0O2sw== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-wrap-function" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/helper-replace-supers@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.25.7.tgz#38cfda3b6e990879c71d08d0fef9236b62bd75f5" - integrity sha512-iy8JhqlUW9PtZkd4pHM96v6BdJ66Ba9yWSE4z0W4TvSZwLBPkyDsiIU3ENe4SmrzRBs76F7rQXTy1lYC49n6Lw== - dependencies: - "@babel/helper-member-expression-to-functions" "^7.25.7" - "@babel/helper-optimise-call-expression" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/helper-simple-access@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.25.7.tgz#5eb9f6a60c5d6b2e0f76057004f8dacbddfae1c0" - integrity sha512-FPGAkJmyoChQeM+ruBGIDyrT2tKfZJO8NcxdC+CWNJi7N8/rZpSxK7yvBJ5O/nF1gfu5KzN7VKG3YVSLFfRSxQ== - dependencies: - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helper-skip-transparent-expression-wrappers@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.25.7.tgz#382831c91038b1a6d32643f5f49505b8442cb87c" - integrity sha512-pPbNbchZBkPMD50K0p3JGcFMNLVUCuU/ABybm/PGNj4JiHrpmNyqqCphBk4i19xXtNV0JhldQJJtbSW5aUvbyA== - dependencies: - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helper-string-parser@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-string-parser/-/helper-string-parser-7.25.7.tgz#d50e8d37b1176207b4fe9acedec386c565a44a54" - integrity sha512-CbkjYdsJNHFk8uqpEkpCvRs3YRp9tY6FmFY7wLMSYuGYkrdUi7r2lc4/wqsvlHoMznX3WJ9IP8giGPq68T/Y6g== - -"@babel/helper-validator-identifier@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.25.7.tgz#77b7f60c40b15c97df735b38a66ba1d7c3e93da5" - integrity sha512-AM6TzwYqGChO45oiuPqwL2t20/HdMC1rTPAesnBCgPCSF1x3oN9MVUwQV2iyz4xqWrctwK5RNC8LV22kaQCNYg== - -"@babel/helper-validator-option@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.25.7.tgz#97d1d684448228b30b506d90cace495d6f492729" - integrity sha512-ytbPLsm+GjArDYXJ8Ydr1c/KJuutjF2besPNbIZnZ6MKUxi/uTA22t2ymmA4WFjZFpjiAMO0xuuJPqK2nvDVfQ== - -"@babel/helper-wrap-function@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.25.7.tgz#9f6021dd1c4fdf4ad515c809967fc4bac9a70fe7" - integrity sha512-MA0roW3JF2bD1ptAaJnvcabsVlNQShUaThyJbCDD4bCp8NEgiFvpoqRI2YS22hHlc2thjO/fTg2ShLMC3jygAg== - dependencies: - "@babel/template" "^7.25.7" - "@babel/traverse" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/helpers@^7.12.5", "@babel/helpers@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.25.7.tgz#091b52cb697a171fe0136ab62e54e407211f09c2" - integrity sha512-Sv6pASx7Esm38KQpF/U/OXLwPPrdGHNKoeblRxgZRLXnAtnkEe4ptJPDtAZM7fBLadbc1Q07kQpSiGQ0Jg6tRA== - dependencies: - "@babel/template" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/highlight@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.25.7.tgz#20383b5f442aa606e7b5e3043b0b1aafe9f37de5" - integrity sha512-iYyACpW3iW8Fw+ZybQK+drQre+ns/tKpXbNESfrhNnPLIklLbXr7MYJ6gPEd0iETGLOK+SxMjVvKb/ffmk+FEw== - dependencies: - "@babel/helper-validator-identifier" "^7.25.7" - chalk "^2.4.2" - js-tokens "^4.0.0" - picocolors "^1.0.0" - -"@babel/parser@^7.12.7", "@babel/parser@^7.18.8", "@babel/parser@^7.25.7", "@babel/parser@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.25.8.tgz#f6aaf38e80c36129460c1657c0762db584c9d5e2" - integrity sha512-HcttkxzdPucv3nNFmfOOMfFf64KgdJVqm1KaCm25dPGMLElo9nsLvXeJECQg8UzPuBGLyTSA0ZzqCtDSzKTEoQ== - dependencies: - "@babel/types" "^7.25.8" - -"@babel/plugin-bugfix-firefox-class-in-computed-class-key@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-firefox-class-in-computed-class-key/-/plugin-bugfix-firefox-class-in-computed-class-key-7.25.7.tgz#93969ac50ef4d68b2504b01b758af714e4cbdd64" - integrity sha512-UV9Lg53zyebzD1DwQoT9mzkEKa922LNUp5YkTJ6Uta0RbyXaQNUgcvSt7qIu1PpPzVb6rd10OVNTzkyBGeVmxQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/plugin-bugfix-safari-class-field-initializer-scope@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-safari-class-field-initializer-scope/-/plugin-bugfix-safari-class-field-initializer-scope-7.25.7.tgz#a338d611adb9dcd599b8b1efa200c88ebeffe046" - integrity sha512-GDDWeVLNxRIkQTnJn2pDOM1pkCgYdSqPeT1a9vh9yIqu2uzzgw1zcqEb+IJOhy+dTBMlNdThrDIksr2o09qrrQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.25.7.tgz#c5f755e911dfac7ef6957300c0f9c4a8c18c06f4" - integrity sha512-wxyWg2RYaSUYgmd9MR0FyRGyeOMQE/Uzr1wzd/g5cf5bwi9A4v6HFdDm7y1MgDtod/fLOSTZY6jDgV0xU9d5bA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.25.7.tgz#3b7ea04492ded990978b6deaa1dfca120ad4455a" - integrity sha512-Xwg6tZpLxc4iQjorYsyGMyfJE7nP5MV8t/Ka58BgiA7Jw0fRqQNcANlLfdJ/yvBt9z9LD2We+BEkT7vLqZRWng== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - "@babel/plugin-transform-optional-chaining" "^7.25.7" - -"@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly/-/plugin-bugfix-v8-static-class-fields-redefine-readonly-7.25.7.tgz#9622b1d597a703aa3a921e6f58c9c2d9a028d2c5" - integrity sha512-UVATLMidXrnH+GMUIuxq55nejlj02HP7F5ETyBONzP6G87fPBogG4CH6kxrSrdIuAjdwNO9VzyaYsrZPscWUrw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/plugin-proposal-object-rest-spread@7.12.1": - version "7.12.1" - resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.12.1.tgz#def9bd03cea0f9b72283dac0ec22d289c7691069" - integrity sha512-s6SowJIjzlhx8o7lsFx5zmY4At6CTtDvgNQDdPzkBQucle58A6b/TTeEBYtyDgmcXjUTM+vE8YOGHZzzbc/ioA== - dependencies: - "@babel/helper-plugin-utils" "^7.10.4" - "@babel/plugin-syntax-object-rest-spread" "^7.8.0" - "@babel/plugin-transform-parameters" "^7.12.1" - -"@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2": - version "7.21.0-placeholder-for-preset-env.2" - resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.21.0-placeholder-for-preset-env.2.tgz#7844f9289546efa9febac2de4cfe358a050bd703" - integrity sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w== - -"@babel/plugin-syntax-dynamic-import@^7.8.3": - version "7.8.3" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz#62bf98b2da3cd21d626154fc96ee5b3cb68eacb3" - integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ== - dependencies: - "@babel/helper-plugin-utils" "^7.8.0" - -"@babel/plugin-syntax-import-assertions@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-import-assertions/-/plugin-syntax-import-assertions-7.25.7.tgz#8ce248f9f4ed4b7ed4cb2e0eb4ed9efd9f52921f" - integrity sha512-ZvZQRmME0zfJnDQnVBKYzHxXT7lYBB3Revz1GuS7oLXWMgqUPX4G+DDbT30ICClht9WKV34QVrZhSw6WdklwZQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-syntax-import-attributes@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-import-attributes/-/plugin-syntax-import-attributes-7.25.7.tgz#d78dd0499d30df19a598e63ab895e21b909bc43f" - integrity sha512-AqVo+dguCgmpi/3mYBdu9lkngOBlQ2w2vnNpa6gfiCxQZLzV4ZbhsXitJ2Yblkoe1VQwtHSaNmIaGll/26YWRw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-syntax-jsx@7.12.1": - version "7.12.1" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.12.1.tgz#9d9d357cc818aa7ae7935917c1257f67677a0926" - integrity sha512-1yRi7yAtB0ETgxdY9ti/p2TivUxJkTdhu/ZbF9MshVGqOx1TdB3b7xCXs49Fupgg50N45KcAsRP/ZqWjs9SRjg== - dependencies: - "@babel/helper-plugin-utils" "^7.10.4" - -"@babel/plugin-syntax-jsx@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.25.7.tgz#5352d398d11ea5e7ef330c854dea1dae0bf18165" - integrity sha512-ruZOnKO+ajVL/MVx+PwNBPOkrnXTXoWMtte1MBpegfCArhqOe3Bj52avVj1huLLxNKYKXYaSxZ2F+woK1ekXfw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-syntax-object-rest-spread@7.8.3", "@babel/plugin-syntax-object-rest-spread@^7.8.0": - version "7.8.3" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz#60e225edcbd98a640332a2e72dd3e66f1af55871" - integrity sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA== - dependencies: - "@babel/helper-plugin-utils" "^7.8.0" - -"@babel/plugin-syntax-typescript@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.25.7.tgz#bfc05b0cc31ebd8af09964650cee723bb228108b" - integrity sha512-rR+5FDjpCHqqZN2bzZm18bVYGaejGq5ZkpVCJLXor/+zlSrSoc4KWcHI0URVWjl/68Dyr1uwZUz/1njycEAv9g== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-syntax-unicode-sets-regex@^7.18.6": - version "7.18.6" - resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-unicode-sets-regex/-/plugin-syntax-unicode-sets-regex-7.18.6.tgz#d49a3b3e6b52e5be6740022317580234a6a47357" - integrity sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/plugin-transform-arrow-functions@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.25.7.tgz#1b9ed22e6890a0e9ff470371c73b8c749bcec386" - integrity sha512-EJN2mKxDwfOUCPxMO6MUI58RN3ganiRAG/MS/S3HfB6QFNjroAMelQo/gybyYq97WerCBAZoyrAoW8Tzdq2jWg== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-async-generator-functions@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-generator-functions/-/plugin-transform-async-generator-functions-7.25.8.tgz#3331de02f52cc1f2c75b396bec52188c85b0b1ec" - integrity sha512-9ypqkozyzpG+HxlH4o4gdctalFGIjjdufzo7I2XPda0iBnZ6a+FO0rIEQcdSPXp02CkvGsII1exJhmROPQd5oA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-remap-async-to-generator" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/plugin-transform-async-to-generator@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.25.7.tgz#a44c7323f8d4285a6c568dd43c5c361d6367ec52" - integrity sha512-ZUCjAavsh5CESCmi/xCpX1qcCaAglzs/7tmuvoFnJgA1dM7gQplsguljoTg+Ru8WENpX89cQyAtWoaE0I3X3Pg== - dependencies: - "@babel/helper-module-imports" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-remap-async-to-generator" "^7.25.7" - -"@babel/plugin-transform-block-scoped-functions@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.25.7.tgz#e0b8843d5571719a2f1bf7e284117a3379fcc17c" - integrity sha512-xHttvIM9fvqW+0a3tZlYcZYSBpSWzGBFIt/sYG3tcdSzBB8ZeVgz2gBP7Df+sM0N1850jrviYSSeUuc+135dmQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-block-scoping@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.25.7.tgz#6dab95e98adf780ceef1b1c3ab0e55cd20dd410a" - integrity sha512-ZEPJSkVZaeTFG/m2PARwLZQ+OG0vFIhPlKHK/JdIMy8DbRJ/htz6LRrTFtdzxi9EHmcwbNPAKDnadpNSIW+Aow== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-class-properties@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-class-properties/-/plugin-transform-class-properties-7.25.7.tgz#a389cfca7a10ac80e3ff4c75fca08bd097ad1523" - integrity sha512-mhyfEW4gufjIqYFo9krXHJ3ElbFLIze5IDp+wQTxoPd+mwFb1NxatNAwmv8Q8Iuxv7Zc+q8EkiMQwc9IhyGf4g== - dependencies: - "@babel/helper-create-class-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-class-static-block@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-class-static-block/-/plugin-transform-class-static-block-7.25.8.tgz#a8af22028920fe404668031eceb4c3aadccb5262" - integrity sha512-e82gl3TCorath6YLf9xUwFehVvjvfqFhdOo4+0iVIVju+6XOi5XHkqB3P2AXnSwoeTX0HBoXq5gJFtvotJzFnQ== - dependencies: - "@babel/helper-create-class-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-classes@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.25.7.tgz#5103206cf80d02283bbbd044509ea3b65d0906bb" - integrity sha512-9j9rnl+YCQY0IGoeipXvnk3niWicIB6kCsWRGLwX241qSXpbA4MKxtp/EdvFxsc4zI5vqfLxzOd0twIJ7I99zg== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-compilation-targets" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-replace-supers" "^7.25.7" - "@babel/traverse" "^7.25.7" - globals "^11.1.0" - -"@babel/plugin-transform-computed-properties@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.25.7.tgz#7f621f0aa1354b5348a935ab12e3903842466f65" - integrity sha512-QIv+imtM+EtNxg/XBKL3hiWjgdLjMOmZ+XzQwSgmBfKbfxUjBzGgVPklUuE55eq5/uVoh8gg3dqlrwR/jw3ZeA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/template" "^7.25.7" - -"@babel/plugin-transform-destructuring@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.25.7.tgz#f6f26a9feefb5aa41fd45b6f5838901b5333d560" - integrity sha512-xKcfLTlJYUczdaM1+epcdh1UGewJqr9zATgrNHcLBcV2QmfvPPEixo/sK/syql9cEmbr7ulu5HMFG5vbbt/sEA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-dotall-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.25.7.tgz#9d775c4a3ff1aea64045300fcd4309b4a610ef02" - integrity sha512-kXzXMMRzAtJdDEgQBLF4oaiT6ZCU3oWHgpARnTKDAqPkDJ+bs3NrZb310YYevR5QlRo3Kn7dzzIdHbZm1VzJdQ== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-duplicate-keys@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.25.7.tgz#fbba7d1155eab76bd4f2a038cbd5d65883bd7a93" - integrity sha512-by+v2CjoL3aMnWDOyCIg+yxU9KXSRa9tN6MbqggH5xvymmr9p4AMjYkNlQy4brMceBnUyHZ9G8RnpvT8wP7Cfg== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-duplicate-named-capturing-groups-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-named-capturing-groups-regex/-/plugin-transform-duplicate-named-capturing-groups-regex-7.25.7.tgz#102b31608dcc22c08fbca1894e104686029dc141" - integrity sha512-HvS6JF66xSS5rNKXLqkk7L9c/jZ/cdIVIcoPVrnl8IsVpLggTjXs8OWekbLHs/VtYDDh5WXnQyeE3PPUGm22MA== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-dynamic-import@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dynamic-import/-/plugin-transform-dynamic-import-7.25.8.tgz#f1edbe75b248cf44c70c8ca8ed3818a668753aaa" - integrity sha512-gznWY+mr4ZQL/EWPcbBQUP3BXS5FwZp8RUOw06BaRn8tQLzN4XLIxXejpHN9Qo8x8jjBmAAKp6FoS51AgkSA/A== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-exponentiation-operator@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.25.7.tgz#5961a3a23a398faccd6cddb34a2182807d75fb5f" - integrity sha512-yjqtpstPfZ0h/y40fAXRv2snciYr0OAoMXY/0ClC7tm4C/nG5NJKmIItlaYlLbIVAWNfrYuy9dq1bE0SbX0PEg== - dependencies: - "@babel/helper-builder-binary-assignment-operator-visitor" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-export-namespace-from@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-export-namespace-from/-/plugin-transform-export-namespace-from-7.25.8.tgz#d1988c3019a380b417e0516418b02804d3858145" - integrity sha512-sPtYrduWINTQTW7FtOy99VCTWp4H23UX7vYcut7S4CIMEXU+54zKX9uCoGkLsWXteyaMXzVHgzWbLfQ1w4GZgw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-for-of@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.25.7.tgz#0acfea0f27aa290818b5b48a5a44b3f03fc13669" - integrity sha512-n/TaiBGJxYFWvpJDfsxSj9lEEE44BFM1EPGz4KEiTipTgkoFVVcCmzAL3qA7fdQU96dpo4gGf5HBx/KnDvqiHw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - -"@babel/plugin-transform-function-name@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.25.7.tgz#7e394ccea3693902a8b50ded8b6ae1fa7b8519fd" - integrity sha512-5MCTNcjCMxQ63Tdu9rxyN6cAWurqfrDZ76qvVPrGYdBxIj+EawuuxTu/+dgJlhK5eRz3v1gLwp6XwS8XaX2NiQ== - dependencies: - "@babel/helper-compilation-targets" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/plugin-transform-json-strings@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-json-strings/-/plugin-transform-json-strings-7.25.8.tgz#6fb3ec383a2ea92652289fdba653e3f9de722694" - integrity sha512-4OMNv7eHTmJ2YXs3tvxAfa/I43di+VcF+M4Wt66c88EAED1RoGaf1D64cL5FkRpNL+Vx9Hds84lksWvd/wMIdA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-literals@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.25.7.tgz#70cbdc742f2cfdb1a63ea2cbd018d12a60b213c3" - integrity sha512-fwzkLrSu2fESR/cm4t6vqd7ebNIopz2QHGtjoU+dswQo/P6lwAG04Q98lliE3jkz/XqnbGFLnUcE0q0CVUf92w== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-logical-assignment-operators@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-logical-assignment-operators/-/plugin-transform-logical-assignment-operators-7.25.8.tgz#01868ff92daa9e525b4c7902aa51979082a05710" - integrity sha512-f5W0AhSbbI+yY6VakT04jmxdxz+WsID0neG7+kQZbCOjuyJNdL5Nn4WIBm4hRpKnUcO9lP0eipUhFN12JpoH8g== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-member-expression-literals@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.25.7.tgz#0a36c3fbd450cc9e6485c507f005fa3d1bc8fca5" - integrity sha512-Std3kXwpXfRV0QtQy5JJcRpkqP8/wG4XL7hSKZmGlxPlDqmpXtEPRmhF7ztnlTCtUN3eXRUJp+sBEZjaIBVYaw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-modules-amd@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.25.7.tgz#bb4e543b5611f6c8c685a2fd485408713a3adf3d" - integrity sha512-CgselSGCGzjQvKzghCvDTxKHP3iooenLpJDO842ehn5D2G5fJB222ptnDwQho0WjEvg7zyoxb9P+wiYxiJX5yA== - dependencies: - "@babel/helper-module-transforms" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-modules-commonjs@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.25.7.tgz#173f0c791bb7407c092ce6d77ee90eb3f2d1d2fd" - integrity sha512-L9Gcahi0kKFYXvweO6n0wc3ZG1ChpSFdgG+eV1WYZ3/dGbJK7vvk91FgGgak8YwRgrCuihF8tE/Xg07EkL5COg== - dependencies: - "@babel/helper-module-transforms" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-simple-access" "^7.25.7" - -"@babel/plugin-transform-modules-systemjs@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.25.7.tgz#8b14d319a177cc9c85ef8b0512afd429d9e2e60b" - integrity sha512-t9jZIvBmOXJsiuyOwhrIGs8dVcD6jDyg2icw1VL4A/g+FnWyJKwUfSSU2nwJuMV2Zqui856El9u+ElB+j9fV1g== - dependencies: - "@babel/helper-module-transforms" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-validator-identifier" "^7.25.7" - "@babel/traverse" "^7.25.7" - -"@babel/plugin-transform-modules-umd@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.25.7.tgz#00ee7a7e124289549381bfb0e24d87fd7f848367" - integrity sha512-p88Jg6QqsaPh+EB7I9GJrIqi1Zt4ZBHUQtjw3z1bzEXcLh6GfPqzZJ6G+G1HBGKUNukT58MnKG7EN7zXQBCODw== - dependencies: - "@babel/helper-module-transforms" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-named-capturing-groups-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.25.7.tgz#a2f3f6d7f38693b462542951748f0a72a34d196d" - integrity sha512-BtAT9LzCISKG3Dsdw5uso4oV1+v2NlVXIIomKJgQybotJY3OwCwJmkongjHgwGKoZXd0qG5UZ12JUlDQ07W6Ow== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-new-target@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.25.7.tgz#52b2bde523b76c548749f38dc3054f1f45e82bc9" - integrity sha512-CfCS2jDsbcZaVYxRFo2qtavW8SpdzmBXC2LOI4oO0rP+JSRDxxF3inF4GcPsLgfb5FjkhXG5/yR/lxuRs2pySA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-nullish-coalescing-operator@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-nullish-coalescing-operator/-/plugin-transform-nullish-coalescing-operator-7.25.8.tgz#befb4900c130bd52fccf2b926314557987f1b552" - integrity sha512-Z7WJJWdQc8yCWgAmjI3hyC+5PXIubH9yRKzkl9ZEG647O9szl9zvmKLzpbItlijBnVhTUf1cpyWBsZ3+2wjWPQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-numeric-separator@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-numeric-separator/-/plugin-transform-numeric-separator-7.25.8.tgz#91e370486371637bd42161052f2602c701386891" - integrity sha512-rm9a5iEFPS4iMIy+/A/PiS0QN0UyjPIeVvbU5EMZFKJZHt8vQnasbpo3T3EFcxzCeYO0BHfc4RqooCZc51J86Q== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-object-rest-spread@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-rest-spread/-/plugin-transform-object-rest-spread-7.25.8.tgz#0904ac16bcce41df4db12d915d6780f85c7fb04b" - integrity sha512-LkUu0O2hnUKHKE7/zYOIjByMa4VRaV2CD/cdGz0AxU9we+VA3kDDggKEzI0Oz1IroG+6gUP6UmWEHBMWZU316g== - dependencies: - "@babel/helper-compilation-targets" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/plugin-transform-parameters" "^7.25.7" - -"@babel/plugin-transform-object-super@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.25.7.tgz#582a9cea8cf0a1e02732be5b5a703a38dedf5661" - integrity sha512-pWT6UXCEW3u1t2tcAGtE15ornCBvopHj9Bps9D2DsH15APgNVOTwwczGckX+WkAvBmuoYKRCFa4DK+jM8vh5AA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-replace-supers" "^7.25.7" - -"@babel/plugin-transform-optional-catch-binding@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-optional-catch-binding/-/plugin-transform-optional-catch-binding-7.25.8.tgz#2649b86a3bb202c6894ec81a6ddf41b94d8f3103" - integrity sha512-EbQYweoMAHOn7iJ9GgZo14ghhb9tTjgOc88xFgYngifx7Z9u580cENCV159M4xDh3q/irbhSjZVpuhpC2gKBbg== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-optional-chaining@^7.25.7", "@babel/plugin-transform-optional-chaining@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-optional-chaining/-/plugin-transform-optional-chaining-7.25.8.tgz#f46283b78adcc5b6ab988a952f989e7dce70653f" - integrity sha512-q05Bk7gXOxpTHoQ8RSzGSh/LHVB9JEIkKnk3myAWwZHnYiTGYtbdrYkIsS8Xyh4ltKf7GNUSgzs/6P2bJtBAQg== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - -"@babel/plugin-transform-parameters@^7.12.1", "@babel/plugin-transform-parameters@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.25.7.tgz#80c38b03ef580f6d6bffe1c5254bb35986859ac7" - integrity sha512-FYiTvku63me9+1Nz7TOx4YMtW3tWXzfANZtrzHhUZrz4d47EEtMQhzFoZWESfXuAMMT5mwzD4+y1N8ONAX6lMQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-private-methods@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-private-methods/-/plugin-transform-private-methods-7.25.7.tgz#c790a04f837b4bd61d6b0317b43aa11ff67dce80" - integrity sha512-KY0hh2FluNxMLwOCHbxVOKfdB5sjWG4M183885FmaqWWiGMhRZq4DQRKH6mHdEucbJnyDyYiZNwNG424RymJjA== - dependencies: - "@babel/helper-create-class-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-private-property-in-object@^7.25.8": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-private-property-in-object/-/plugin-transform-private-property-in-object-7.25.8.tgz#1234f856ce85e061f9688764194e51ea7577c434" - integrity sha512-8Uh966svuB4V8RHHg0QJOB32QK287NBksJOByoKmHMp1TAobNniNalIkI2i5IPj5+S9NYCG4VIjbEuiSN8r+ow== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-create-class-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-property-literals@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.25.7.tgz#a8612b4ea4e10430f00012ecf0155662c7d6550d" - integrity sha512-lQEeetGKfFi0wHbt8ClQrUSUMfEeI3MMm74Z73T9/kuz990yYVtfofjf3NuA42Jy3auFOpbjDyCSiIkTs1VIYw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-react-constant-elements@^7.18.12", "@babel/plugin-transform-react-constant-elements@^7.21.3": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-constant-elements/-/plugin-transform-react-constant-elements-7.25.7.tgz#b7f18dcdfac137a635a3f1242ea7c931df82a666" - integrity sha512-/qXt69Em8HgsjCLu7G3zdIQn7A2QwmYND7Wa0LTp09Na+Zn8L5d0A7wSXrKi18TJRc/Q5S1i1De/SU1LzVkSvA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-react-display-name@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-display-name/-/plugin-transform-react-display-name-7.25.7.tgz#2753e875a1b702fb1d806c4f5d4c194d64cadd88" - integrity sha512-r0QY7NVU8OnrwE+w2IWiRom0wwsTbjx4+xH2RTd7AVdof3uurXOF+/mXHQDRk+2jIvWgSaCHKMgggfvM4dyUGA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-react-jsx-development@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx-development/-/plugin-transform-react-jsx-development-7.25.7.tgz#2fbd77887b8fa2942d7cb61edf1029ea1b048554" - integrity sha512-5yd3lH1PWxzW6IZj+p+Y4OLQzz0/LzlOG8vGqonHfVR3euf1vyzyMUJk9Ac+m97BH46mFc/98t9PmYLyvgL3qg== - dependencies: - "@babel/plugin-transform-react-jsx" "^7.25.7" - -"@babel/plugin-transform-react-jsx@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx/-/plugin-transform-react-jsx-7.25.7.tgz#f5e2af6020a562fe048dd343e571c4428e6c5632" - integrity sha512-vILAg5nwGlR9EXE8JIOX4NHXd49lrYbN8hnjffDtoULwpL9hUx/N55nqh2qd0q6FyNDfjl9V79ecKGvFbcSA0Q== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-module-imports" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/plugin-syntax-jsx" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/plugin-transform-react-pure-annotations@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-pure-annotations/-/plugin-transform-react-pure-annotations-7.25.7.tgz#6d0b8dadb2d3c5cbb8ade68c5efd49470b0d65f7" - integrity sha512-6YTHJ7yjjgYqGc8S+CbEXhLICODk0Tn92j+vNJo07HFk9t3bjFgAKxPLFhHwF2NjmQVSI1zBRfBWUeVBa2osfA== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-regenerator@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.25.7.tgz#6eb006e6d26f627bc2f7844a9f19770721ad6f3e" - integrity sha512-mgDoQCRjrY3XK95UuV60tZlFCQGXEtMg8H+IsW72ldw1ih1jZhzYXbJvghmAEpg5UVhhnCeia1CkGttUvCkiMQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - regenerator-transform "^0.15.2" - -"@babel/plugin-transform-reserved-words@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.25.7.tgz#dc56b25e02afaabef3ce0c5b06b0916e8523e995" - integrity sha512-3OfyfRRqiGeOvIWSagcwUTVk2hXBsr/ww7bLn6TRTuXnexA+Udov2icFOxFX9abaj4l96ooYkcNN1qi2Zvqwng== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-runtime@^7.18.6": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.25.7.tgz#435a4fab67273f00047dc806e05069c9c6344e12" - integrity sha512-Y9p487tyTzB0yDYQOtWnC+9HGOuogtP3/wNpun1xJXEEvI6vip59BSBTsHnekZLqxmPcgsrAKt46HAAb//xGhg== - dependencies: - "@babel/helper-module-imports" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - babel-plugin-polyfill-corejs2 "^0.4.10" - babel-plugin-polyfill-corejs3 "^0.10.6" - babel-plugin-polyfill-regenerator "^0.6.1" - semver "^6.3.1" - -"@babel/plugin-transform-shorthand-properties@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.25.7.tgz#92690a9c671915602d91533c278cc8f6bf12275f" - integrity sha512-uBbxNwimHi5Bv3hUccmOFlUy3ATO6WagTApenHz9KzoIdn0XeACdB12ZJ4cjhuB2WSi80Ez2FWzJnarccriJeA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-spread@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.25.7.tgz#df83e899a9fc66284ee601a7b738568435b92998" - integrity sha512-Mm6aeymI0PBh44xNIv/qvo8nmbkpZze1KvR8MkEqbIREDxoiWTi18Zr2jryfRMwDfVZF9foKh060fWgni44luw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - -"@babel/plugin-transform-sticky-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.25.7.tgz#341c7002bef7f29037be7fb9684e374442dd0d17" - integrity sha512-ZFAeNkpGuLnAQ/NCsXJ6xik7Id+tHuS+NT+ue/2+rn/31zcdnupCdmunOizEaP0JsUmTFSTOPoQY7PkK2pttXw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-template-literals@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.25.7.tgz#e566c581bb16d8541dd8701093bb3457adfce16b" - integrity sha512-SI274k0nUsFFmyQupiO7+wKATAmMFf8iFgq2O+vVFXZ0SV9lNfT1NGzBEhjquFmD8I9sqHLguH+gZVN3vww2AA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-typeof-symbol@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.25.7.tgz#debb1287182efd20488f126be343328c679b66eb" - integrity sha512-OmWmQtTHnO8RSUbL0NTdtpbZHeNTnm68Gj5pA4Y2blFNh+V4iZR68V1qL9cI37J21ZN7AaCnkfdHtLExQPf2uA== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-typescript@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typescript/-/plugin-transform-typescript-7.25.7.tgz#8fc7c3d28ddd36bce45b9b48594129d0e560cfbe" - integrity sha512-VKlgy2vBzj8AmEzunocMun2fF06bsSWV+FvVXohtL6FGve/+L217qhHxRTVGHEDO/YR8IANcjzgJsd04J8ge5Q== - dependencies: - "@babel/helper-annotate-as-pure" "^7.25.7" - "@babel/helper-create-class-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.25.7" - "@babel/plugin-syntax-typescript" "^7.25.7" - -"@babel/plugin-transform-unicode-escapes@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.25.7.tgz#973592b6d13a914794e1de8cf1383e50e0f87f81" - integrity sha512-BN87D7KpbdiABA+t3HbVqHzKWUDN3dymLaTnPFAMyc8lV+KN3+YzNhVRNdinaCPA4AUqx7ubXbQ9shRjYBl3SQ== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-unicode-property-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-property-regex/-/plugin-transform-unicode-property-regex-7.25.7.tgz#25349197cce964b1343f74fa7cfdf791a1b1919e" - integrity sha512-IWfR89zcEPQGB/iB408uGtSPlQd3Jpq11Im86vUgcmSTcoWAiQMCTOa2K2yNNqFJEBVICKhayctee65Ka8OB0w== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-unicode-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.25.7.tgz#f93a93441baf61f713b6d5552aaa856bfab34809" - integrity sha512-8JKfg/hiuA3qXnlLx8qtv5HWRbgyFx2hMMtpDDuU2rTckpKkGu4ycK5yYHwuEa16/quXfoxHBIApEsNyMWnt0g== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/plugin-transform-unicode-sets-regex@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-sets-regex/-/plugin-transform-unicode-sets-regex-7.25.7.tgz#d1b3295d29e0f8f4df76abc909ad1ebee919560c" - integrity sha512-YRW8o9vzImwmh4Q3Rffd09bH5/hvY0pxg+1H1i0f7APoUeg12G7+HhLj9ZFNIrYkgBXhIijPJ+IXypN0hLTIbw== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - -"@babel/preset-env@^7.18.6", "@babel/preset-env@^7.19.4", "@babel/preset-env@^7.20.2": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.25.8.tgz#dc6b719627fb29cd9cccbbbe041802fd575b524c" - integrity sha512-58T2yulDHMN8YMUxiLq5YmWUnlDCyY1FsHM+v12VMx+1/FlrUj5tY50iDCpofFQEM8fMYOaY9YRvym2jcjn1Dg== - dependencies: - "@babel/compat-data" "^7.25.8" - "@babel/helper-compilation-targets" "^7.25.7" - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-validator-option" "^7.25.7" - "@babel/plugin-bugfix-firefox-class-in-computed-class-key" "^7.25.7" - "@babel/plugin-bugfix-safari-class-field-initializer-scope" "^7.25.7" - "@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression" "^7.25.7" - "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining" "^7.25.7" - "@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly" "^7.25.7" - "@babel/plugin-proposal-private-property-in-object" "7.21.0-placeholder-for-preset-env.2" - "@babel/plugin-syntax-import-assertions" "^7.25.7" - "@babel/plugin-syntax-import-attributes" "^7.25.7" - "@babel/plugin-syntax-unicode-sets-regex" "^7.18.6" - "@babel/plugin-transform-arrow-functions" "^7.25.7" - "@babel/plugin-transform-async-generator-functions" "^7.25.8" - "@babel/plugin-transform-async-to-generator" "^7.25.7" - "@babel/plugin-transform-block-scoped-functions" "^7.25.7" - "@babel/plugin-transform-block-scoping" "^7.25.7" - "@babel/plugin-transform-class-properties" "^7.25.7" - "@babel/plugin-transform-class-static-block" "^7.25.8" - "@babel/plugin-transform-classes" "^7.25.7" - "@babel/plugin-transform-computed-properties" "^7.25.7" - "@babel/plugin-transform-destructuring" "^7.25.7" - "@babel/plugin-transform-dotall-regex" "^7.25.7" - "@babel/plugin-transform-duplicate-keys" "^7.25.7" - "@babel/plugin-transform-duplicate-named-capturing-groups-regex" "^7.25.7" - "@babel/plugin-transform-dynamic-import" "^7.25.8" - "@babel/plugin-transform-exponentiation-operator" "^7.25.7" - "@babel/plugin-transform-export-namespace-from" "^7.25.8" - "@babel/plugin-transform-for-of" "^7.25.7" - "@babel/plugin-transform-function-name" "^7.25.7" - "@babel/plugin-transform-json-strings" "^7.25.8" - "@babel/plugin-transform-literals" "^7.25.7" - "@babel/plugin-transform-logical-assignment-operators" "^7.25.8" - "@babel/plugin-transform-member-expression-literals" "^7.25.7" - "@babel/plugin-transform-modules-amd" "^7.25.7" - "@babel/plugin-transform-modules-commonjs" "^7.25.7" - "@babel/plugin-transform-modules-systemjs" "^7.25.7" - "@babel/plugin-transform-modules-umd" "^7.25.7" - "@babel/plugin-transform-named-capturing-groups-regex" "^7.25.7" - "@babel/plugin-transform-new-target" "^7.25.7" - "@babel/plugin-transform-nullish-coalescing-operator" "^7.25.8" - "@babel/plugin-transform-numeric-separator" "^7.25.8" - "@babel/plugin-transform-object-rest-spread" "^7.25.8" - "@babel/plugin-transform-object-super" "^7.25.7" - "@babel/plugin-transform-optional-catch-binding" "^7.25.8" - "@babel/plugin-transform-optional-chaining" "^7.25.8" - "@babel/plugin-transform-parameters" "^7.25.7" - "@babel/plugin-transform-private-methods" "^7.25.7" - "@babel/plugin-transform-private-property-in-object" "^7.25.8" - "@babel/plugin-transform-property-literals" "^7.25.7" - "@babel/plugin-transform-regenerator" "^7.25.7" - "@babel/plugin-transform-reserved-words" "^7.25.7" - "@babel/plugin-transform-shorthand-properties" "^7.25.7" - "@babel/plugin-transform-spread" "^7.25.7" - "@babel/plugin-transform-sticky-regex" "^7.25.7" - "@babel/plugin-transform-template-literals" "^7.25.7" - "@babel/plugin-transform-typeof-symbol" "^7.25.7" - "@babel/plugin-transform-unicode-escapes" "^7.25.7" - "@babel/plugin-transform-unicode-property-regex" "^7.25.7" - "@babel/plugin-transform-unicode-regex" "^7.25.7" - "@babel/plugin-transform-unicode-sets-regex" "^7.25.7" - "@babel/preset-modules" "0.1.6-no-external-plugins" - babel-plugin-polyfill-corejs2 "^0.4.10" - babel-plugin-polyfill-corejs3 "^0.10.6" - babel-plugin-polyfill-regenerator "^0.6.1" - core-js-compat "^3.38.1" - semver "^6.3.1" - -"@babel/preset-modules@0.1.6-no-external-plugins": - version "0.1.6-no-external-plugins" - resolved "https://registry.yarnpkg.com/@babel/preset-modules/-/preset-modules-0.1.6-no-external-plugins.tgz#ccb88a2c49c817236861fee7826080573b8a923a" - integrity sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA== - dependencies: - "@babel/helper-plugin-utils" "^7.0.0" - "@babel/types" "^7.4.4" - esutils "^2.0.2" - -"@babel/preset-react@^7.18.6": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/preset-react/-/preset-react-7.25.7.tgz#081cbe1dea363b732764d06a0fdda67ffa17735d" - integrity sha512-GjV0/mUEEXpi1U5ZgDprMRRgajGMRW3G5FjMr5KLKD8nT2fTG8+h/klV3+6Dm5739QE+K5+2e91qFKAYI3pmRg== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-validator-option" "^7.25.7" - "@babel/plugin-transform-react-display-name" "^7.25.7" - "@babel/plugin-transform-react-jsx" "^7.25.7" - "@babel/plugin-transform-react-jsx-development" "^7.25.7" - "@babel/plugin-transform-react-pure-annotations" "^7.25.7" - -"@babel/preset-typescript@^7.18.6", "@babel/preset-typescript@^7.21.0": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/preset-typescript/-/preset-typescript-7.25.7.tgz#43c5b68eccb856ae5b52274b77b1c3c413cde1b7" - integrity sha512-rkkpaXJZOFN45Fb+Gki0c+KMIglk4+zZXOoMJuyEK8y8Kkc8Jd3BDmP7qPsz0zQMJj+UD7EprF+AqAXcILnexw== - dependencies: - "@babel/helper-plugin-utils" "^7.25.7" - "@babel/helper-validator-option" "^7.25.7" - "@babel/plugin-syntax-jsx" "^7.25.7" - "@babel/plugin-transform-modules-commonjs" "^7.25.7" - "@babel/plugin-transform-typescript" "^7.25.7" - -"@babel/runtime-corejs3@^7.18.6": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/runtime-corejs3/-/runtime-corejs3-7.25.7.tgz#29ca319b1272e9d78faa3f7ee891d0af63c53aa2" - integrity sha512-gMmIEhg35sXk9Te5qbGp3W9YKrvLt3HV658/d3odWrHSqT0JeG5OzsJWFHRLiOohRyjRsJc/x03DhJm3i8VJxg== - dependencies: - core-js-pure "^3.30.2" - regenerator-runtime "^0.14.0" - -"@babel/runtime@^7.1.2", "@babel/runtime@^7.10.3", "@babel/runtime@^7.12.13", "@babel/runtime@^7.12.5", "@babel/runtime@^7.18.6", "@babel/runtime@^7.20.13", "@babel/runtime@^7.8.4": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.25.7.tgz#7ffb53c37a8f247c8c4d335e89cdf16a2e0d0fb6" - integrity sha512-FjoyLe754PMiYsFaN5C94ttGiOmBNYTf6pLr4xXHAT5uctHb092PBszndLDR5XA/jghQvn4n7JMHl7dmTgbm9w== - dependencies: - regenerator-runtime "^0.14.0" - -"@babel/template@^7.12.7", "@babel/template@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.25.7.tgz#27f69ce382855d915b14ab0fe5fb4cbf88fa0769" - integrity sha512-wRwtAgI3bAS+JGU2upWNL9lSlDcRCqD05BZ1n3X2ONLH1WilFP6O1otQjeMK/1g0pvYcXC7b/qVUB1keofjtZA== - dependencies: - "@babel/code-frame" "^7.25.7" - "@babel/parser" "^7.25.7" - "@babel/types" "^7.25.7" - -"@babel/traverse@^7.12.9", "@babel/traverse@^7.18.8", "@babel/traverse@^7.25.7": - version "7.25.7" - resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.25.7.tgz#83e367619be1cab8e4f2892ef30ba04c26a40fa8" - integrity sha512-jatJPT1Zjqvh/1FyJs6qAHL+Dzb7sTb+xr7Q+gM1b+1oBsMsQQ4FkVKb6dFlJvLlVssqkRzV05Jzervt9yhnzg== - dependencies: - "@babel/code-frame" "^7.25.7" - "@babel/generator" "^7.25.7" - "@babel/parser" "^7.25.7" - "@babel/template" "^7.25.7" - "@babel/types" "^7.25.7" - debug "^4.3.1" - globals "^11.1.0" - -"@babel/types@^7.12.7", "@babel/types@^7.20.0", "@babel/types@^7.21.3", "@babel/types@^7.25.7", "@babel/types@^7.25.8", "@babel/types@^7.4.4": - version "7.25.8" - resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.25.8.tgz#5cf6037258e8a9bcad533f4979025140cb9993e1" - integrity sha512-JWtuCu8VQsMladxVz/P4HzHUGCAwpuqacmowgXFs5XjxIgKuNjnLokQzuVjlTvIzODaDmpjT3oxcC48vyk9EWg== - dependencies: - "@babel/helper-string-parser" "^7.25.7" - "@babel/helper-validator-identifier" "^7.25.7" - to-fast-properties "^2.0.0" - -"@cmfcmf/docusaurus-search-local@^1.2.0": - version "1.2.0" - resolved "https://registry.yarnpkg.com/@cmfcmf/docusaurus-search-local/-/docusaurus-search-local-1.2.0.tgz#85c8fcfc4dd0e8481c5c0435fa754ab51e483f67" - integrity sha512-Tc0GhRBsfZAiB+f6BoPB8YCQap6JzzcDyJ0dLSCSzWQ6wdWvDlTBrHc1YqR8q8AZ+STRszL5eZpZFi5dbTCdYg== - dependencies: - "@algolia/autocomplete-js" "^1.8.2" - "@algolia/autocomplete-theme-classic" "^1.8.2" - "@algolia/client-search" "^4.12.0" - algoliasearch "^4.12.0" - cheerio "^1.0.0-rc.9" - clsx "^1.1.1" - lunr-languages "^1.4.0" - mark.js "^8.11.1" - tslib "^2.6.3" - -"@colors/colors@1.5.0": - version "1.5.0" - resolved "https://registry.yarnpkg.com/@colors/colors/-/colors-1.5.0.tgz#bb504579c1cae923e6576a4f5da43d25f97bdbd9" - integrity sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ== - -"@discoveryjs/json-ext@0.5.7": - version "0.5.7" - resolved "https://registry.yarnpkg.com/@discoveryjs/json-ext/-/json-ext-0.5.7.tgz#1d572bfbbe14b7704e0ba0f39b74815b84870d70" - integrity sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw== - -"@docsearch/css@3.6.2": - version "3.6.2" - resolved "https://registry.yarnpkg.com/@docsearch/css/-/css-3.6.2.tgz#ccd9c83dbfeaf34efe4e3547ee596714ae7e5891" - integrity sha512-vKNZepO2j7MrYBTZIGXvlUOIR+v9KRf70FApRgovWrj3GTs1EITz/Xb0AOlm1xsQBp16clVZj1SY/qaOJbQtZw== - -"@docsearch/react@^3.1.1": - version "3.6.2" - resolved "https://registry.yarnpkg.com/@docsearch/react/-/react-3.6.2.tgz#32b16dd7d5614f0d39e6bc018549816b68d171b8" - integrity sha512-rtZce46OOkVflCQH71IdbXSFK+S8iJZlUF56XBW5rIgx/eG5qoomC7Ag3anZson1bBac/JFQn7XOBfved/IMRA== - dependencies: - "@algolia/autocomplete-core" "1.9.3" - "@algolia/autocomplete-preset-algolia" "1.9.3" - "@docsearch/css" "3.6.2" - algoliasearch "^4.19.1" - -"@docusaurus/core@2.4.3", "@docusaurus/core@^2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/core/-/core-2.4.3.tgz#d86624901386fd8164ce4bff9cc7f16fde57f523" - integrity sha512-dWH5P7cgeNSIg9ufReX6gaCl/TmrGKD38Orbwuz05WPhAQtFXHd5B8Qym1TiXfvUNvwoYKkAJOJuGe8ou0Z7PA== - dependencies: - "@babel/core" "^7.18.6" - "@babel/generator" "^7.18.7" - "@babel/plugin-syntax-dynamic-import" "^7.8.3" - "@babel/plugin-transform-runtime" "^7.18.6" - "@babel/preset-env" "^7.18.6" - "@babel/preset-react" "^7.18.6" - "@babel/preset-typescript" "^7.18.6" - "@babel/runtime" "^7.18.6" - "@babel/runtime-corejs3" "^7.18.6" - "@babel/traverse" "^7.18.8" - "@docusaurus/cssnano-preset" "2.4.3" - "@docusaurus/logger" "2.4.3" - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/react-loadable" "5.5.2" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-common" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - "@slorber/static-site-generator-webpack-plugin" "^4.0.7" - "@svgr/webpack" "^6.2.1" - autoprefixer "^10.4.7" - babel-loader "^8.2.5" - babel-plugin-dynamic-import-node "^2.3.3" - boxen "^6.2.1" - chalk "^4.1.2" - chokidar "^3.5.3" - clean-css "^5.3.0" - cli-table3 "^0.6.2" - combine-promises "^1.1.0" - commander "^5.1.0" - copy-webpack-plugin "^11.0.0" - core-js "^3.23.3" - css-loader "^6.7.1" - css-minimizer-webpack-plugin "^4.0.0" - cssnano "^5.1.12" - del "^6.1.1" - detect-port "^1.3.0" - escape-html "^1.0.3" - eta "^2.0.0" - file-loader "^6.2.0" - fs-extra "^10.1.0" - html-minifier-terser "^6.1.0" - html-tags "^3.2.0" - html-webpack-plugin "^5.5.0" - import-fresh "^3.3.0" - leven "^3.1.0" - lodash "^4.17.21" - mini-css-extract-plugin "^2.6.1" - postcss "^8.4.14" - postcss-loader "^7.0.0" - prompts "^2.4.2" - react-dev-utils "^12.0.1" - react-helmet-async "^1.3.0" - react-loadable "npm:@docusaurus/react-loadable@5.5.2" - react-loadable-ssr-addon-v5-slorber "^1.0.1" - react-router "^5.3.3" - react-router-config "^5.1.1" - react-router-dom "^5.3.3" - rtl-detect "^1.0.4" - semver "^7.3.7" - serve-handler "^6.1.3" - shelljs "^0.8.5" - terser-webpack-plugin "^5.3.3" - tslib "^2.4.0" - update-notifier "^5.1.0" - url-loader "^4.1.1" - wait-on "^6.0.1" - webpack "^5.73.0" - webpack-bundle-analyzer "^4.5.0" - webpack-dev-server "^4.9.3" - webpack-merge "^5.8.0" - webpackbar "^5.0.2" - -"@docusaurus/cssnano-preset@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/cssnano-preset/-/cssnano-preset-2.4.3.tgz#1d7e833c41ce240fcc2812a2ac27f7b862f32de0" - integrity sha512-ZvGSRCi7z9wLnZrXNPG6DmVPHdKGd8dIn9pYbEOFiYihfv4uDR3UtxogmKf+rT8ZlKFf5Lqne8E8nt08zNM8CA== - dependencies: - cssnano-preset-advanced "^5.3.8" - postcss "^8.4.14" - postcss-sort-media-queries "^4.2.1" - tslib "^2.4.0" - -"@docusaurus/logger@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/logger/-/logger-2.4.3.tgz#518bbc965fb4ebe8f1d0b14e5f4161607552d34c" - integrity sha512-Zxws7r3yLufk9xM1zq9ged0YHs65mlRmtsobnFkdZTxWXdTYlWWLWdKyNKAsVC+D7zg+pv2fGbyabdOnyZOM3w== - dependencies: - chalk "^4.1.2" - tslib "^2.4.0" - -"@docusaurus/lqip-loader@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/lqip-loader/-/lqip-loader-2.4.3.tgz#aab8b7d873317e7490f29027047a05076d499746" - integrity sha512-hdumVOGbI4eiQQsZvbbosnm86FNkp23GikNanC0MJIIz8j3sCg8I0GEmg9nnVZor/2tE4ud5AWqjsVrx1CwcjA== - dependencies: - "@docusaurus/logger" "2.4.3" - file-loader "^6.2.0" - lodash "^4.17.21" - sharp "^0.30.7" - tslib "^2.4.0" - -"@docusaurus/mdx-loader@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/mdx-loader/-/mdx-loader-2.4.3.tgz#e8ff37f30a060eaa97b8121c135f74cb531a4a3e" - integrity sha512-b1+fDnWtl3GiqkL0BRjYtc94FZrcDDBV1j8446+4tptB9BAOlePwG2p/pK6vGvfL53lkOsszXMghr2g67M0vCw== - dependencies: - "@babel/parser" "^7.18.8" - "@babel/traverse" "^7.18.8" - "@docusaurus/logger" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@mdx-js/mdx" "^1.6.22" - escape-html "^1.0.3" - file-loader "^6.2.0" - fs-extra "^10.1.0" - image-size "^1.0.1" - mdast-util-to-string "^2.0.0" - remark-emoji "^2.2.0" - stringify-object "^3.3.0" - tslib "^2.4.0" - unified "^9.2.2" - unist-util-visit "^2.0.3" - url-loader "^4.1.1" - webpack "^5.73.0" - -"@docusaurus/module-type-aliases@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/module-type-aliases/-/module-type-aliases-2.4.3.tgz#d08ef67e4151e02f352a2836bcf9ecde3b9c56ac" - integrity sha512-cwkBkt1UCiduuvEAo7XZY01dJfRn7UR/75mBgOdb1hKknhrabJZ8YH+7savd/y9kLExPyrhe0QwdS9GuzsRRIA== - dependencies: - "@docusaurus/react-loadable" "5.5.2" - "@docusaurus/types" "2.4.3" - "@types/history" "^4.7.11" - "@types/react" "*" - "@types/react-router-config" "*" - "@types/react-router-dom" "*" - react-helmet-async "*" - react-loadable "npm:@docusaurus/react-loadable@5.5.2" - -"@docusaurus/plugin-content-blog@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-blog/-/plugin-content-blog-2.4.3.tgz#6473b974acab98e967414d8bbb0d37e0cedcea14" - integrity sha512-PVhypqaA0t98zVDpOeTqWUTvRqCEjJubtfFUQ7zJNYdbYTbS/E/ytq6zbLVsN/dImvemtO/5JQgjLxsh8XLo8Q== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/logger" "2.4.3" - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-common" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - cheerio "^1.0.0-rc.12" - feed "^4.2.2" - fs-extra "^10.1.0" - lodash "^4.17.21" - reading-time "^1.5.0" - tslib "^2.4.0" - unist-util-visit "^2.0.3" - utility-types "^3.10.0" - webpack "^5.73.0" - -"@docusaurus/plugin-content-docs@2.4.3", "@docusaurus/plugin-content-docs@^2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-docs/-/plugin-content-docs-2.4.3.tgz#aa224c0512351e81807adf778ca59fd9cd136973" - integrity sha512-N7Po2LSH6UejQhzTCsvuX5NOzlC+HiXOVvofnEPj0WhMu1etpLEXE6a4aTxrtg95lQ5kf0xUIdjX9sh3d3G76A== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/logger" "2.4.3" - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/module-type-aliases" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - "@types/react-router-config" "^5.0.6" - combine-promises "^1.1.0" - fs-extra "^10.1.0" - import-fresh "^3.3.0" - js-yaml "^4.1.0" - lodash "^4.17.21" - tslib "^2.4.0" - utility-types "^3.10.0" - webpack "^5.73.0" - -"@docusaurus/plugin-content-pages@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-pages/-/plugin-content-pages-2.4.3.tgz#7f285e718b53da8c8d0101e70840c75b9c0a1ac0" - integrity sha512-txtDVz7y3zGk67q0HjG0gRttVPodkHqE0bpJ+7dOaTH40CQFLSh7+aBeGnPOTl+oCPG+hxkim4SndqPqXjQ8Bg== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - fs-extra "^10.1.0" - tslib "^2.4.0" - webpack "^5.73.0" - -"@docusaurus/plugin-debug@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-debug/-/plugin-debug-2.4.3.tgz#2f90eb0c9286a9f225444e3a88315676fe02c245" - integrity sha512-LkUbuq3zCmINlFb+gAd4ZvYr+bPAzMC0hwND4F7V9bZ852dCX8YoWyovVUBKq4er1XsOwSQaHmNGtObtn8Av8Q== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - fs-extra "^10.1.0" - react-json-view "^1.21.3" - tslib "^2.4.0" - -"@docusaurus/plugin-google-analytics@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-analytics/-/plugin-google-analytics-2.4.3.tgz#0d19993136ade6f7a7741251b4f617400d92ab45" - integrity sha512-KzBV3k8lDkWOhg/oYGxlK5o9bOwX7KpPc/FTWoB+SfKhlHfhq7qcQdMi1elAaVEIop8tgK6gD1E58Q+XC6otSQ== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - tslib "^2.4.0" - -"@docusaurus/plugin-google-gtag@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-gtag/-/plugin-google-gtag-2.4.3.tgz#e1a80b0696771b488562e5b60eff21c9932d9e1c" - integrity sha512-5FMg0rT7sDy4i9AGsvJC71MQrqQZwgLNdDetLEGDHLfSHLvJhQbTCUGbGXknUgWXQJckcV/AILYeJy+HhxeIFA== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - tslib "^2.4.0" - -"@docusaurus/plugin-google-tag-manager@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-tag-manager/-/plugin-google-tag-manager-2.4.3.tgz#e41fbf79b0ffc2de1cc4013eb77798cff0ad98e3" - integrity sha512-1jTzp71yDGuQiX9Bi0pVp3alArV0LSnHXempvQTxwCGAEzUWWaBg4d8pocAlTpbP9aULQQqhgzrs8hgTRPOM0A== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - tslib "^2.4.0" - -"@docusaurus/plugin-ideal-image@^2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-ideal-image/-/plugin-ideal-image-2.4.3.tgz#b4988f4e82c3351596c54474eb35bddd9c827deb" - integrity sha512-cwnOKz5HwR/WwNL5lzGOWppyhaHQ2dPj1/x9hwv5VPwNmDDnWsYEwfBOTq8AYT27vFrYAH1tx9UX7QurRaIa4A== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/lqip-loader" "2.4.3" - "@docusaurus/responsive-loader" "^1.7.0" - "@docusaurus/theme-translations" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - "@endiliey/react-ideal-image" "^0.0.11" - react-waypoint "^10.3.0" - sharp "^0.30.7" - tslib "^2.4.0" - webpack "^5.73.0" - -"@docusaurus/plugin-sitemap@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/plugin-sitemap/-/plugin-sitemap-2.4.3.tgz#1b3930900a8f89670ce7e8f83fb4730cd3298c32" - integrity sha512-LRQYrK1oH1rNfr4YvWBmRzTL0LN9UAPxBbghgeFRBm5yloF6P+zv1tm2pe2hQTX/QP5bSKdnajCvfnScgKXMZQ== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/logger" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-common" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - fs-extra "^10.1.0" - sitemap "^7.1.1" - tslib "^2.4.0" - -"@docusaurus/preset-classic@^2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/preset-classic/-/preset-classic-2.4.3.tgz#074c57ebf29fa43d23bd1c8ce691226f542bc262" - integrity sha512-tRyMliepY11Ym6hB1rAFSNGwQDpmszvWYJvlK1E+md4SW8i6ylNHtpZjaYFff9Mdk3i/Pg8ItQq9P0daOJAvQw== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/plugin-content-blog" "2.4.3" - "@docusaurus/plugin-content-docs" "2.4.3" - "@docusaurus/plugin-content-pages" "2.4.3" - "@docusaurus/plugin-debug" "2.4.3" - "@docusaurus/plugin-google-analytics" "2.4.3" - "@docusaurus/plugin-google-gtag" "2.4.3" - "@docusaurus/plugin-google-tag-manager" "2.4.3" - "@docusaurus/plugin-sitemap" "2.4.3" - "@docusaurus/theme-classic" "2.4.3" - "@docusaurus/theme-common" "2.4.3" - "@docusaurus/theme-search-algolia" "2.4.3" - "@docusaurus/types" "2.4.3" - -"@docusaurus/react-loadable@5.5.2", "react-loadable@npm:@docusaurus/react-loadable@5.5.2": - version "5.5.2" - resolved "https://registry.yarnpkg.com/@docusaurus/react-loadable/-/react-loadable-5.5.2.tgz#81aae0db81ecafbdaee3651f12804580868fa6ce" - integrity sha512-A3dYjdBGuy0IGT+wyLIGIKLRE+sAk1iNk0f1HjNDysO7u8lhL4N3VEm+FAubmJbAztn94F7MxBTPmnixbiyFdQ== - dependencies: - "@types/react" "*" - prop-types "^15.6.2" - -"@docusaurus/responsive-loader@^1.7.0": - version "1.7.0" - resolved "https://registry.yarnpkg.com/@docusaurus/responsive-loader/-/responsive-loader-1.7.0.tgz#508df2779e04311aa2a38efb67cf743109afd681" - integrity sha512-N0cWuVqTRXRvkBxeMQcy/OF2l7GN8rmni5EzR3HpwR+iU2ckYPnziceojcxvvxQ5NqZg1QfEW0tycQgHp+e+Nw== - dependencies: - loader-utils "^2.0.0" - -"@docusaurus/theme-classic@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/theme-classic/-/theme-classic-2.4.3.tgz#29360f2eb03a0e1686eb19668633ef313970ee8f" - integrity sha512-QKRAJPSGPfDY2yCiPMIVyr+MqwZCIV2lxNzqbyUW0YkrlmdzzP3WuQJPMGLCjWgQp/5c9kpWMvMxjhpZx1R32Q== - dependencies: - "@docusaurus/core" "2.4.3" - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/module-type-aliases" "2.4.3" - "@docusaurus/plugin-content-blog" "2.4.3" - "@docusaurus/plugin-content-docs" "2.4.3" - "@docusaurus/plugin-content-pages" "2.4.3" - "@docusaurus/theme-common" "2.4.3" - "@docusaurus/theme-translations" "2.4.3" - "@docusaurus/types" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-common" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - "@mdx-js/react" "^1.6.22" - clsx "^1.2.1" - copy-text-to-clipboard "^3.0.1" - infima "0.2.0-alpha.43" - lodash "^4.17.21" - nprogress "^0.2.0" - postcss "^8.4.14" - prism-react-renderer "^1.3.5" - prismjs "^1.28.0" - react-router-dom "^5.3.3" - rtlcss "^3.5.0" - tslib "^2.4.0" - utility-types "^3.10.0" - -"@docusaurus/theme-common@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/theme-common/-/theme-common-2.4.3.tgz#bb31d70b6b67d0bdef9baa343192dcec49946a2e" - integrity sha512-7KaDJBXKBVGXw5WOVt84FtN8czGWhM0lbyWEZXGp8AFfL6sZQfRTluFp4QriR97qwzSyOfQb+nzcDZZU4tezUw== - dependencies: - "@docusaurus/mdx-loader" "2.4.3" - "@docusaurus/module-type-aliases" "2.4.3" - "@docusaurus/plugin-content-blog" "2.4.3" - "@docusaurus/plugin-content-docs" "2.4.3" - "@docusaurus/plugin-content-pages" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-common" "2.4.3" - "@types/history" "^4.7.11" - "@types/react" "*" - "@types/react-router-config" "*" - clsx "^1.2.1" - parse-numeric-range "^1.3.0" - prism-react-renderer "^1.3.5" - tslib "^2.4.0" - use-sync-external-store "^1.2.0" - utility-types "^3.10.0" - -"@docusaurus/theme-search-algolia@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/theme-search-algolia/-/theme-search-algolia-2.4.3.tgz#32d4cbefc3deba4112068fbdb0bde11ac51ece53" - integrity sha512-jziq4f6YVUB5hZOB85ELATwnxBz/RmSLD3ksGQOLDPKVzat4pmI8tddNWtriPpxR04BNT+ZfpPUMFkNFetSW1Q== - dependencies: - "@docsearch/react" "^3.1.1" - "@docusaurus/core" "2.4.3" - "@docusaurus/logger" "2.4.3" - "@docusaurus/plugin-content-docs" "2.4.3" - "@docusaurus/theme-common" "2.4.3" - "@docusaurus/theme-translations" "2.4.3" - "@docusaurus/utils" "2.4.3" - "@docusaurus/utils-validation" "2.4.3" - algoliasearch "^4.13.1" - algoliasearch-helper "^3.10.0" - clsx "^1.2.1" - eta "^2.0.0" - fs-extra "^10.1.0" - lodash "^4.17.21" - tslib "^2.4.0" - utility-types "^3.10.0" - -"@docusaurus/theme-translations@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/theme-translations/-/theme-translations-2.4.3.tgz#91ac73fc49b8c652b7a54e88b679af57d6ac6102" - integrity sha512-H4D+lbZbjbKNS/Zw1Lel64PioUAIT3cLYYJLUf3KkuO/oc9e0QCVhIYVtUI2SfBCF2NNdlyhBDQEEMygsCedIg== - dependencies: - fs-extra "^10.1.0" - tslib "^2.4.0" - -"@docusaurus/types@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/types/-/types-2.4.3.tgz#4aead281ca09f721b3c0a9b926818450cfa3db31" - integrity sha512-W6zNLGQqfrp/EoPD0bhb9n7OobP+RHpmvVzpA+Z/IuU3Q63njJM24hmT0GYboovWcDtFmnIJC9wcyx4RVPQscw== - dependencies: - "@types/history" "^4.7.11" - "@types/react" "*" - commander "^5.1.0" - joi "^17.6.0" - react-helmet-async "^1.3.0" - utility-types "^3.10.0" - webpack "^5.73.0" - webpack-merge "^5.8.0" - -"@docusaurus/utils-common@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/utils-common/-/utils-common-2.4.3.tgz#30656c39ef1ce7e002af7ba39ea08330f58efcfb" - integrity sha512-/jascp4GbLQCPVmcGkPzEQjNaAk3ADVfMtudk49Ggb+131B1WDD6HqlSmDf8MxGdy7Dja2gc+StHf01kiWoTDQ== - dependencies: - tslib "^2.4.0" - -"@docusaurus/utils-validation@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/utils-validation/-/utils-validation-2.4.3.tgz#8122c394feef3e96c73f6433987837ec206a63fb" - integrity sha512-G2+Vt3WR5E/9drAobP+hhZQMaswRwDlp6qOMi7o7ZypB+VO7N//DZWhZEwhcRGepMDJGQEwtPv7UxtYwPL9PBw== - dependencies: - "@docusaurus/logger" "2.4.3" - "@docusaurus/utils" "2.4.3" - joi "^17.6.0" - js-yaml "^4.1.0" - tslib "^2.4.0" - -"@docusaurus/utils@2.4.3": - version "2.4.3" - resolved "https://registry.yarnpkg.com/@docusaurus/utils/-/utils-2.4.3.tgz#52b000d989380a2125831b84e3a7327bef471e89" - integrity sha512-fKcXsjrD86Smxv8Pt0TBFqYieZZCPh4cbf9oszUq/AMhZn3ujwpKaVYZACPX8mmjtYx0JOgNx52CREBfiGQB4A== - dependencies: - "@docusaurus/logger" "2.4.3" - "@svgr/webpack" "^6.2.1" - escape-string-regexp "^4.0.0" - file-loader "^6.2.0" - fs-extra "^10.1.0" - github-slugger "^1.4.0" - globby "^11.1.0" - gray-matter "^4.0.3" - js-yaml "^4.1.0" - lodash "^4.17.21" - micromatch "^4.0.5" - resolve-pathname "^3.0.0" - shelljs "^0.8.5" - tslib "^2.4.0" - url-loader "^4.1.1" - webpack "^5.73.0" - -"@endiliey/react-ideal-image@^0.0.11": - version "0.0.11" - resolved "https://registry.yarnpkg.com/@endiliey/react-ideal-image/-/react-ideal-image-0.0.11.tgz#dc3803d04e1409cf88efa4bba0f67667807bdf27" - integrity sha512-QxMjt/Gvur/gLxSoCy7VIyGGGrGmDN+VHcXkN3R2ApoWX0EYUE+hMgPHSW/PV6VVebZ1Nd4t2UnGRBDihu16JQ== - -"@hapi/hoek@^9.0.0", "@hapi/hoek@^9.3.0": - version "9.3.0" - resolved "https://registry.yarnpkg.com/@hapi/hoek/-/hoek-9.3.0.tgz#8368869dcb735be2e7f5cb7647de78e167a251fb" - integrity sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ== - -"@hapi/topo@^5.1.0": - version "5.1.0" - resolved "https://registry.yarnpkg.com/@hapi/topo/-/topo-5.1.0.tgz#dc448e332c6c6e37a4dc02fd84ba8d44b9afb012" - integrity sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg== - dependencies: - "@hapi/hoek" "^9.0.0" - -"@jest/schemas@^29.6.3": - version "29.6.3" - resolved "https://registry.yarnpkg.com/@jest/schemas/-/schemas-29.6.3.tgz#430b5ce8a4e0044a7e3819663305a7b3091c8e03" - integrity sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA== - dependencies: - "@sinclair/typebox" "^0.27.8" - -"@jest/types@^29.6.3": - version "29.6.3" - resolved "https://registry.yarnpkg.com/@jest/types/-/types-29.6.3.tgz#1131f8cf634e7e84c5e77bab12f052af585fba59" - integrity sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw== - dependencies: - "@jest/schemas" "^29.6.3" - "@types/istanbul-lib-coverage" "^2.0.0" - "@types/istanbul-reports" "^3.0.0" - "@types/node" "*" - "@types/yargs" "^17.0.8" - chalk "^4.0.0" - -"@jridgewell/gen-mapping@^0.3.5": - version "0.3.5" - resolved "https://registry.yarnpkg.com/@jridgewell/gen-mapping/-/gen-mapping-0.3.5.tgz#dcce6aff74bdf6dad1a95802b69b04a2fcb1fb36" - integrity sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg== - dependencies: - "@jridgewell/set-array" "^1.2.1" - "@jridgewell/sourcemap-codec" "^1.4.10" - "@jridgewell/trace-mapping" "^0.3.24" - -"@jridgewell/resolve-uri@^3.1.0": - version "3.1.2" - resolved "https://registry.yarnpkg.com/@jridgewell/resolve-uri/-/resolve-uri-3.1.2.tgz#7a0ee601f60f99a20c7c7c5ff0c80388c1189bd6" - integrity sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw== - -"@jridgewell/set-array@^1.2.1": - version "1.2.1" - resolved "https://registry.yarnpkg.com/@jridgewell/set-array/-/set-array-1.2.1.tgz#558fb6472ed16a4c850b889530e6b36438c49280" - integrity sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A== - -"@jridgewell/source-map@^0.3.3": - version "0.3.6" - resolved "https://registry.yarnpkg.com/@jridgewell/source-map/-/source-map-0.3.6.tgz#9d71ca886e32502eb9362c9a74a46787c36df81a" - integrity sha512-1ZJTZebgqllO79ue2bm3rIGud/bOe0pP5BjSRCRxxYkEZS8STV7zN84UBbiYu7jy+eCKSnVIUgoWWE/tt+shMQ== - dependencies: - "@jridgewell/gen-mapping" "^0.3.5" - "@jridgewell/trace-mapping" "^0.3.25" - -"@jridgewell/sourcemap-codec@^1.4.10", "@jridgewell/sourcemap-codec@^1.4.14": - version "1.5.0" - resolved "https://registry.yarnpkg.com/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.5.0.tgz#3188bcb273a414b0d215fd22a58540b989b9409a" - integrity sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ== - -"@jridgewell/trace-mapping@^0.3.20", "@jridgewell/trace-mapping@^0.3.24", "@jridgewell/trace-mapping@^0.3.25": - version "0.3.25" - resolved "https://registry.yarnpkg.com/@jridgewell/trace-mapping/-/trace-mapping-0.3.25.tgz#15f190e98895f3fc23276ee14bc76b675c2e50f0" - integrity sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ== - dependencies: - "@jridgewell/resolve-uri" "^3.1.0" - "@jridgewell/sourcemap-codec" "^1.4.14" - -"@leichtgewicht/ip-codec@^2.0.1": - version "2.0.5" - resolved "https://registry.yarnpkg.com/@leichtgewicht/ip-codec/-/ip-codec-2.0.5.tgz#4fc56c15c580b9adb7dc3c333a134e540b44bfb1" - integrity sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw== - -"@mdx-js/mdx@^1.6.22": - version "1.6.22" - resolved "https://registry.yarnpkg.com/@mdx-js/mdx/-/mdx-1.6.22.tgz#8a723157bf90e78f17dc0f27995398e6c731f1ba" - integrity sha512-AMxuLxPz2j5/6TpF/XSdKpQP1NlG0z11dFOlq+2IP/lSgl11GY8ji6S/rgsViN/L0BDvHvUMruRb7ub+24LUYA== - dependencies: - "@babel/core" "7.12.9" - "@babel/plugin-syntax-jsx" "7.12.1" - "@babel/plugin-syntax-object-rest-spread" "7.8.3" - "@mdx-js/util" "1.6.22" - babel-plugin-apply-mdx-type-prop "1.6.22" - babel-plugin-extract-import-names "1.6.22" - camelcase-css "2.0.1" - detab "2.0.4" - hast-util-raw "6.0.1" - lodash.uniq "4.5.0" - mdast-util-to-hast "10.0.1" - remark-footnotes "2.0.0" - remark-mdx "1.6.22" - remark-parse "8.0.3" - remark-squeeze-paragraphs "4.0.0" - style-to-object "0.3.0" - unified "9.2.0" - unist-builder "2.0.3" - unist-util-visit "2.0.3" - -"@mdx-js/react@^1.6.22": - version "1.6.22" - resolved "https://registry.yarnpkg.com/@mdx-js/react/-/react-1.6.22.tgz#ae09b4744fddc74714ee9f9d6f17a66e77c43573" - integrity sha512-TDoPum4SHdfPiGSAaRBw7ECyI8VaHpK8GJugbJIJuqyh6kzw9ZLJZW3HGL3NNrJGxcAixUvqROm+YuQOo5eXtg== - -"@mdx-js/util@1.6.22": - version "1.6.22" - resolved "https://registry.yarnpkg.com/@mdx-js/util/-/util-1.6.22.tgz#219dfd89ae5b97a8801f015323ffa4b62f45718b" - integrity sha512-H1rQc1ZOHANWBvPcW+JpGwr+juXSxM8Q8YCkm3GhZd8REu1fHR3z99CErO1p9pkcfcxZnMdIZdIsXkOHY0NilA== - -"@nodelib/fs.scandir@2.1.5": - version "2.1.5" - resolved "https://registry.yarnpkg.com/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz#7619c2eb21b25483f6d167548b4cfd5a7488c3d5" - integrity sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g== - dependencies: - "@nodelib/fs.stat" "2.0.5" - run-parallel "^1.1.9" - -"@nodelib/fs.stat@2.0.5", "@nodelib/fs.stat@^2.0.2": - version "2.0.5" - resolved "https://registry.yarnpkg.com/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz#5bd262af94e9d25bd1e71b05deed44876a222e8b" - integrity sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A== - -"@nodelib/fs.walk@^1.2.3": - version "1.2.8" - resolved "https://registry.yarnpkg.com/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz#e95737e8bb6746ddedf69c556953494f196fe69a" - integrity sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg== - dependencies: - "@nodelib/fs.scandir" "2.1.5" - fastq "^1.6.0" - -"@polka/url@^1.0.0-next.24": - version "1.0.0-next.28" - resolved "https://registry.yarnpkg.com/@polka/url/-/url-1.0.0-next.28.tgz#d45e01c4a56f143ee69c54dd6b12eade9e270a73" - integrity sha512-8LduaNlMZGwdZ6qWrKlfa+2M4gahzFkprZiAt2TF8uS0qQgBizKXpXURqvTJ4WtmupWxaLqjRb2UCTe72mu+Aw== - -"@sideway/address@^4.1.5": - version "4.1.5" - resolved "https://registry.yarnpkg.com/@sideway/address/-/address-4.1.5.tgz#4bc149a0076623ced99ca8208ba780d65a99b9d5" - integrity sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q== - dependencies: - "@hapi/hoek" "^9.0.0" - -"@sideway/formula@^3.0.1": - version "3.0.1" - resolved "https://registry.yarnpkg.com/@sideway/formula/-/formula-3.0.1.tgz#80fcbcbaf7ce031e0ef2dd29b1bfc7c3f583611f" - integrity sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg== - -"@sideway/pinpoint@^2.0.0": - version "2.0.0" - resolved "https://registry.yarnpkg.com/@sideway/pinpoint/-/pinpoint-2.0.0.tgz#cff8ffadc372ad29fd3f78277aeb29e632cc70df" - integrity sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ== - -"@sinclair/typebox@^0.27.8": - version "0.27.8" - resolved "https://registry.yarnpkg.com/@sinclair/typebox/-/typebox-0.27.8.tgz#6667fac16c436b5434a387a34dedb013198f6e6e" - integrity sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA== - -"@sindresorhus/is@^0.14.0": - version "0.14.0" - resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-0.14.0.tgz#9fb3a3cf3132328151f353de4632e01e52102bea" - integrity sha512-9NET910DNaIPngYnLLPeg+Ogzqsi9uM4mSboU5y6p8S5DzMTVEsJZrawi+BoDNUVBa2DhJqQYUFvMDfgU062LQ== - -"@slorber/static-site-generator-webpack-plugin@^4.0.7": - version "4.0.7" - resolved "https://registry.yarnpkg.com/@slorber/static-site-generator-webpack-plugin/-/static-site-generator-webpack-plugin-4.0.7.tgz#fc1678bddefab014e2145cbe25b3ce4e1cfc36f3" - integrity sha512-Ug7x6z5lwrz0WqdnNFOMYrDQNTPAprvHLSh6+/fmml3qUiz6l5eq+2MzLKWtn/q5K5NpSiFsZTP/fck/3vjSxA== - dependencies: - eval "^0.1.8" - p-map "^4.0.0" - webpack-sources "^3.2.2" - -"@svgr/babel-plugin-add-jsx-attribute@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-add-jsx-attribute/-/babel-plugin-add-jsx-attribute-8.0.0.tgz#4001f5d5dd87fa13303e36ee106e3ff3a7eb8b22" - integrity sha512-b9MIk7yhdS1pMCZM8VeNfUlSKVRhsHZNMl5O9SfaX0l0t5wjdgu4IDzGB8bpnGBBOjGST3rRFVsaaEtI4W6f7g== - -"@svgr/babel-plugin-add-jsx-attribute@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-add-jsx-attribute/-/babel-plugin-add-jsx-attribute-6.5.1.tgz#74a5d648bd0347bda99d82409d87b8ca80b9a1ba" - integrity sha512-9PYGcXrAxitycIjRmZB+Q0JaN07GZIWaTBIGQzfaZv+qr1n8X1XUEJ5rZ/vx6OVD9RRYlrNnXWExQXcmZeD/BQ== - -"@svgr/babel-plugin-remove-jsx-attribute@*", "@svgr/babel-plugin-remove-jsx-attribute@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-remove-jsx-attribute/-/babel-plugin-remove-jsx-attribute-8.0.0.tgz#69177f7937233caca3a1afb051906698f2f59186" - integrity sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA== - -"@svgr/babel-plugin-remove-jsx-empty-expression@*", "@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-remove-jsx-empty-expression/-/babel-plugin-remove-jsx-empty-expression-8.0.0.tgz#c2c48104cfd7dcd557f373b70a56e9e3bdae1d44" - integrity sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA== - -"@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-replace-jsx-attribute-value/-/babel-plugin-replace-jsx-attribute-value-8.0.0.tgz#8fbb6b2e91fa26ac5d4aa25c6b6e4f20f9c0ae27" - integrity sha512-KVQ+PtIjb1BuYT3ht8M5KbzWBhdAjjUPdlMtpuw/VjT8coTrItWX6Qafl9+ji831JaJcu6PJNKCV0bp01lBNzQ== - -"@svgr/babel-plugin-replace-jsx-attribute-value@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-replace-jsx-attribute-value/-/babel-plugin-replace-jsx-attribute-value-6.5.1.tgz#fb9d22ea26d2bc5e0a44b763d4c46d5d3f596c60" - integrity sha512-8DPaVVE3fd5JKuIC29dqyMB54sA6mfgki2H2+swh+zNJoynC8pMPzOkidqHOSc6Wj032fhl8Z0TVn1GiPpAiJg== - -"@svgr/babel-plugin-svg-dynamic-title@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-dynamic-title/-/babel-plugin-svg-dynamic-title-8.0.0.tgz#1d5ba1d281363fc0f2f29a60d6d936f9bbc657b0" - integrity sha512-omNiKqwjNmOQJ2v6ge4SErBbkooV2aAWwaPFs2vUY7p7GhVkzRkJ00kILXQvRhA6miHnNpXv7MRnnSjdRjK8og== - -"@svgr/babel-plugin-svg-dynamic-title@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-dynamic-title/-/babel-plugin-svg-dynamic-title-6.5.1.tgz#01b2024a2b53ffaa5efceaa0bf3e1d5a4c520ce4" - integrity sha512-FwOEi0Il72iAzlkaHrlemVurgSQRDFbk0OC8dSvD5fSBPHltNh7JtLsxmZUhjYBZo2PpcU/RJvvi6Q0l7O7ogw== - -"@svgr/babel-plugin-svg-em-dimensions@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-em-dimensions/-/babel-plugin-svg-em-dimensions-8.0.0.tgz#35e08df300ea8b1d41cb8f62309c241b0369e501" - integrity sha512-mURHYnu6Iw3UBTbhGwE/vsngtCIbHE43xCRK7kCw4t01xyGqb2Pd+WXekRRoFOBIY29ZoOhUCTEweDMdrjfi9g== - -"@svgr/babel-plugin-svg-em-dimensions@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-em-dimensions/-/babel-plugin-svg-em-dimensions-6.5.1.tgz#dd3fa9f5b24eb4f93bcf121c3d40ff5facecb217" - integrity sha512-gWGsiwjb4tw+ITOJ86ndY/DZZ6cuXMNE/SjcDRg+HLuCmwpcjOktwRF9WgAiycTqJD/QXqL2f8IzE2Rzh7aVXA== - -"@svgr/babel-plugin-transform-react-native-svg@8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-react-native-svg/-/babel-plugin-transform-react-native-svg-8.1.0.tgz#90a8b63998b688b284f255c6a5248abd5b28d754" - integrity sha512-Tx8T58CHo+7nwJ+EhUwx3LfdNSG9R2OKfaIXXs5soiy5HtgoAEkDay9LIimLOcG8dJQH1wPZp/cnAv6S9CrR1Q== - -"@svgr/babel-plugin-transform-react-native-svg@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-react-native-svg/-/babel-plugin-transform-react-native-svg-6.5.1.tgz#1d8e945a03df65b601551097d8f5e34351d3d305" - integrity sha512-2jT3nTayyYP7kI6aGutkyfJ7UMGtuguD72OjeGLwVNyfPRBD8zQthlvL+fAbAKk5n9ZNcvFkp/b1lZ7VsYqVJg== - -"@svgr/babel-plugin-transform-svg-component@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-svg-component/-/babel-plugin-transform-svg-component-8.0.0.tgz#013b4bfca88779711f0ed2739f3f7efcefcf4f7e" - integrity sha512-DFx8xa3cZXTdb/k3kfPeaixecQLgKh5NVBMwD0AQxOzcZawK4oo1Jh9LbrcACUivsCA7TLG8eeWgrDXjTMhRmw== - -"@svgr/babel-plugin-transform-svg-component@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-svg-component/-/babel-plugin-transform-svg-component-6.5.1.tgz#48620b9e590e25ff95a80f811544218d27f8a250" - integrity sha512-a1p6LF5Jt33O3rZoVRBqdxL350oge54iZWHNI6LJB5tQ7EelvD/Mb1mfBiZNAan0dt4i3VArkFRjA4iObuNykQ== - -"@svgr/babel-preset@8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/babel-preset/-/babel-preset-8.1.0.tgz#0e87119aecdf1c424840b9d4565b7137cabf9ece" - integrity sha512-7EYDbHE7MxHpv4sxvnVPngw5fuR6pw79SkcrILHJ/iMpuKySNCl5W1qcwPEpU+LgyRXOaAFgH0KhwD18wwg6ug== - dependencies: - "@svgr/babel-plugin-add-jsx-attribute" "8.0.0" - "@svgr/babel-plugin-remove-jsx-attribute" "8.0.0" - "@svgr/babel-plugin-remove-jsx-empty-expression" "8.0.0" - "@svgr/babel-plugin-replace-jsx-attribute-value" "8.0.0" - "@svgr/babel-plugin-svg-dynamic-title" "8.0.0" - "@svgr/babel-plugin-svg-em-dimensions" "8.0.0" - "@svgr/babel-plugin-transform-react-native-svg" "8.1.0" - "@svgr/babel-plugin-transform-svg-component" "8.0.0" - -"@svgr/babel-preset@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/babel-preset/-/babel-preset-6.5.1.tgz#b90de7979c8843c5c580c7e2ec71f024b49eb828" - integrity sha512-6127fvO/FF2oi5EzSQOAjo1LE3OtNVh11R+/8FXa+mHx1ptAaS4cknIjnUA7e6j6fwGGJ17NzaTJFUwOV2zwCw== - dependencies: - "@svgr/babel-plugin-add-jsx-attribute" "^6.5.1" - "@svgr/babel-plugin-remove-jsx-attribute" "*" - "@svgr/babel-plugin-remove-jsx-empty-expression" "*" - "@svgr/babel-plugin-replace-jsx-attribute-value" "^6.5.1" - "@svgr/babel-plugin-svg-dynamic-title" "^6.5.1" - "@svgr/babel-plugin-svg-em-dimensions" "^6.5.1" - "@svgr/babel-plugin-transform-react-native-svg" "^6.5.1" - "@svgr/babel-plugin-transform-svg-component" "^6.5.1" - -"@svgr/core@8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/core/-/core-8.1.0.tgz#41146f9b40b1a10beaf5cc4f361a16a3c1885e88" - integrity sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA== - dependencies: - "@babel/core" "^7.21.3" - "@svgr/babel-preset" "8.1.0" - camelcase "^6.2.0" - cosmiconfig "^8.1.3" - snake-case "^3.0.4" - -"@svgr/core@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/core/-/core-6.5.1.tgz#d3e8aa9dbe3fbd747f9ee4282c1c77a27410488a" - integrity sha512-/xdLSWxK5QkqG524ONSjvg3V/FkNyCv538OIBdQqPNaAta3AsXj/Bd2FbvR87yMbXO2hFSWiAe/Q6IkVPDw+mw== - dependencies: - "@babel/core" "^7.19.6" - "@svgr/babel-preset" "^6.5.1" - "@svgr/plugin-jsx" "^6.5.1" - camelcase "^6.2.0" - cosmiconfig "^7.0.1" - -"@svgr/hast-util-to-babel-ast@8.0.0": - version "8.0.0" - resolved "https://registry.yarnpkg.com/@svgr/hast-util-to-babel-ast/-/hast-util-to-babel-ast-8.0.0.tgz#6952fd9ce0f470e1aded293b792a2705faf4ffd4" - integrity sha512-EbDKwO9GpfWP4jN9sGdYwPBU0kdomaPIL2Eu4YwmgP+sJeXT+L7bMwJUBnhzfH8Q2qMBqZ4fJwpCyYsAN3mt2Q== - dependencies: - "@babel/types" "^7.21.3" - entities "^4.4.0" - -"@svgr/hast-util-to-babel-ast@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/hast-util-to-babel-ast/-/hast-util-to-babel-ast-6.5.1.tgz#81800bd09b5bcdb968bf6ee7c863d2288fdb80d2" - integrity sha512-1hnUxxjd83EAxbL4a0JDJoD3Dao3hmjvyvyEV8PzWmLK3B9m9NPlW7GKjFyoWE8nM7HnXzPcmmSyOW8yOddSXw== - dependencies: - "@babel/types" "^7.20.0" - entities "^4.4.0" - -"@svgr/plugin-jsx@8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/plugin-jsx/-/plugin-jsx-8.1.0.tgz#96969f04a24b58b174ee4cd974c60475acbd6928" - integrity sha512-0xiIyBsLlr8quN+WyuxooNW9RJ0Dpr8uOnH/xrCVO8GLUcwHISwj1AG0k+LFzteTkAA0GbX0kj9q6Dk70PTiPA== - dependencies: - "@babel/core" "^7.21.3" - "@svgr/babel-preset" "8.1.0" - "@svgr/hast-util-to-babel-ast" "8.0.0" - svg-parser "^2.0.4" - -"@svgr/plugin-jsx@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/plugin-jsx/-/plugin-jsx-6.5.1.tgz#0e30d1878e771ca753c94e69581c7971542a7072" - integrity sha512-+UdQxI3jgtSjCykNSlEMuy1jSRQlGC7pqBCPvkG/2dATdWo082zHTTK3uhnAju2/6XpE6B5mZ3z4Z8Ns01S8Gw== - dependencies: - "@babel/core" "^7.19.6" - "@svgr/babel-preset" "^6.5.1" - "@svgr/hast-util-to-babel-ast" "^6.5.1" - svg-parser "^2.0.4" - -"@svgr/plugin-svgo@8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/plugin-svgo/-/plugin-svgo-8.1.0.tgz#b115b7b967b564f89ac58feae89b88c3decd0f00" - integrity sha512-Ywtl837OGO9pTLIN/onoWLmDQ4zFUycI1g76vuKGEz6evR/ZTJlJuz3G/fIkb6OVBJ2g0o6CGJzaEjfmEo3AHA== - dependencies: - cosmiconfig "^8.1.3" - deepmerge "^4.3.1" - svgo "^3.0.2" - -"@svgr/plugin-svgo@^6.5.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/plugin-svgo/-/plugin-svgo-6.5.1.tgz#0f91910e988fc0b842f88e0960c2862e022abe84" - integrity sha512-omvZKf8ixP9z6GWgwbtmP9qQMPX4ODXi+wzbVZgomNFsUIlHA1sf4fThdwTWSsZGgvGAG6yE+b/F5gWUkcZ/iQ== - dependencies: - cosmiconfig "^7.0.1" - deepmerge "^4.2.2" - svgo "^2.8.0" - -"@svgr/webpack@^6.2.1": - version "6.5.1" - resolved "https://registry.yarnpkg.com/@svgr/webpack/-/webpack-6.5.1.tgz#ecf027814fc1cb2decc29dc92f39c3cf691e40e8" - integrity sha512-cQ/AsnBkXPkEK8cLbv4Dm7JGXq2XrumKnL1dRpJD9rIO2fTIlJI9a1uCciYG1F2aUsox/hJQyNGbt3soDxSRkA== - dependencies: - "@babel/core" "^7.19.6" - "@babel/plugin-transform-react-constant-elements" "^7.18.12" - "@babel/preset-env" "^7.19.4" - "@babel/preset-react" "^7.18.6" - "@babel/preset-typescript" "^7.18.6" - "@svgr/core" "^6.5.1" - "@svgr/plugin-jsx" "^6.5.1" - "@svgr/plugin-svgo" "^6.5.1" - -"@svgr/webpack@^8.1.0": - version "8.1.0" - resolved "https://registry.yarnpkg.com/@svgr/webpack/-/webpack-8.1.0.tgz#16f1b5346f102f89fda6ec7338b96a701d8be0c2" - integrity sha512-LnhVjMWyMQV9ZmeEy26maJk+8HTIbd59cH4F2MJ439k9DqejRisfFNGAPvRYlKETuh9LrImlS8aKsBgKjMA8WA== - dependencies: - "@babel/core" "^7.21.3" - "@babel/plugin-transform-react-constant-elements" "^7.21.3" - "@babel/preset-env" "^7.20.2" - "@babel/preset-react" "^7.18.6" - "@babel/preset-typescript" "^7.21.0" - "@svgr/core" "8.1.0" - "@svgr/plugin-jsx" "8.1.0" - "@svgr/plugin-svgo" "8.1.0" - -"@swc/core-darwin-arm64@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-darwin-arm64/-/core-darwin-arm64-1.7.39.tgz#8954552632e8100e30625dba3b926fb861f37209" - integrity sha512-o2nbEL6scMBMCTvY9OnbyVXtepLuNbdblV9oNJEFia5v5eGj9WMrnRQiylH3Wp/G2NYkW7V1/ZVW+kfvIeYe9A== - -"@swc/core-darwin-x64@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-darwin-x64/-/core-darwin-x64-1.7.39.tgz#bd4699cca0b104629422eabaea1bc09afcd1ccc2" - integrity sha512-qMlv3XPgtPi/Fe11VhiPDHSLiYYk2dFYl747oGsHZPq+6tIdDQjIhijXPcsUHIXYDyG7lNpODPL8cP/X1sc9MA== - -"@swc/core-linux-arm-gnueabihf@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-linux-arm-gnueabihf/-/core-linux-arm-gnueabihf-1.7.39.tgz#921603cd294734d673b292efd6385d13ffb075ed" - integrity sha512-NP+JIkBs1ZKnpa3Lk2W1kBJMwHfNOxCUJXuTa2ckjFsuZ8OUu2gwdeLFkTHbR43dxGwH5UzSmuGocXeMowra/Q== - -"@swc/core-linux-arm64-gnu@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-linux-arm64-gnu/-/core-linux-arm64-gnu-1.7.39.tgz#d751faf13b575bb0eb422a283a9e61c11e547dc8" - integrity sha512-cPc+/HehyHyHcvAsk3ML/9wYcpWVIWax3YBaA+ScecJpSE04l/oBHPfdqKUPslqZ+Gcw0OWnIBGJT/fBZW2ayw== - -"@swc/core-linux-arm64-musl@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-linux-arm64-musl/-/core-linux-arm64-musl-1.7.39.tgz#ac9b346dd5891798956e6b573f5111126c00fe17" - integrity sha512-8RxgBC6ubFem66bk9XJ0vclu3exJ6eD7x7CwDhp5AD/tulZslTYXM7oNPjEtje3xxabXuj/bEUMNvHZhQRFdqA== - -"@swc/core-linux-x64-gnu@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-linux-x64-gnu/-/core-linux-x64-gnu-1.7.39.tgz#1a0bb356bc83cc3c6c88e0a35281fd0c57aa27cc" - integrity sha512-3gtCPEJuXLQEolo9xsXtuPDocmXQx12vewEyFFSMSjOfakuPOBmOQMa0sVL8Wwius8C1eZVeD1fgk0omMqeC+Q== - -"@swc/core-linux-x64-musl@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-linux-x64-musl/-/core-linux-x64-musl-1.7.39.tgz#800dc36a964e04bd04944934218506eff19cc158" - integrity sha512-mg39pW5x/eqqpZDdtjZJxrUvQNSvJF4O8wCl37fbuFUqOtXs4TxsjZ0aolt876HXxxhsQl7rS+N4KioEMSgTZw== - -"@swc/core-win32-arm64-msvc@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-win32-arm64-msvc/-/core-win32-arm64-msvc-1.7.39.tgz#91dcd6a9996714a78005984f08e8cc8dcdf8a90f" - integrity sha512-NZwuS0mNJowH3e9bMttr7B1fB8bW5svW/yyySigv9qmV5VcQRNz1kMlCvrCLYRsa93JnARuiaBI6FazSeG8mpA== - -"@swc/core-win32-ia32-msvc@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-win32-ia32-msvc/-/core-win32-ia32-msvc-1.7.39.tgz#464bd804d92d3e09cb72cc9764ea3a53e58e8405" - integrity sha512-qFmvv5UExbJPXhhvCVDBnjK5Duqxr048dlVB6ZCgGzbRxuarOlawCzzLK4N172230pzlAWGLgn9CWl3+N6zfHA== - -"@swc/core-win32-x64-msvc@1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core-win32-x64-msvc/-/core-win32-x64-msvc-1.7.39.tgz#a30d68b49ffdd325d676d5d2d5ff8d5edc6ff761" - integrity sha512-o+5IMqgOtj9+BEOp16atTfBgCogVak9svhBpwsbcJQp67bQbxGYhAPPDW/hZ2rpSSF7UdzbY9wudoX9G4trcuQ== - -"@swc/core@^1.7.39": - version "1.7.39" - resolved "https://registry.yarnpkg.com/@swc/core/-/core-1.7.39.tgz#8f830dce7c31b2def931701ec1c0f8ed203024d0" - integrity sha512-jns6VFeOT49uoTKLWIEfiQqJAlyqldNAt80kAr8f7a5YjX0zgnG3RBiLMpksx4Ka4SlK4O6TJ/lumIM3Trp82g== - dependencies: - "@swc/counter" "^0.1.3" - "@swc/types" "^0.1.13" - optionalDependencies: - "@swc/core-darwin-arm64" "1.7.39" - "@swc/core-darwin-x64" "1.7.39" - "@swc/core-linux-arm-gnueabihf" "1.7.39" - "@swc/core-linux-arm64-gnu" "1.7.39" - "@swc/core-linux-arm64-musl" "1.7.39" - "@swc/core-linux-x64-gnu" "1.7.39" - "@swc/core-linux-x64-musl" "1.7.39" - "@swc/core-win32-arm64-msvc" "1.7.39" - "@swc/core-win32-ia32-msvc" "1.7.39" - "@swc/core-win32-x64-msvc" "1.7.39" - -"@swc/counter@^0.1.3": - version "0.1.3" - resolved "https://registry.yarnpkg.com/@swc/counter/-/counter-0.1.3.tgz#cc7463bd02949611c6329596fccd2b0ec782b0e9" - integrity sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ== - -"@swc/types@^0.1.13": - version "0.1.13" - resolved "https://registry.yarnpkg.com/@swc/types/-/types-0.1.13.tgz#441734f8bfa6e9e738f1c68e98be6da282ecc7db" - integrity sha512-JL7eeCk6zWCbiYQg2xQSdLXQJl8Qoc9rXmG2cEKvHe3CKwMHwHGpfOb8frzNLmbycOo6I51qxnLnn9ESf4I20Q== - dependencies: - "@swc/counter" "^0.1.3" - -"@szmarczak/http-timer@^1.1.2": - version "1.1.2" - resolved "https://registry.yarnpkg.com/@szmarczak/http-timer/-/http-timer-1.1.2.tgz#b1665e2c461a2cd92f4c1bbf50d5454de0d4b421" - integrity sha512-XIB2XbzHTN6ieIjfIMV9hlVcfPU26s2vafYWQcZHWXHOxiaRZYEDKEwdl129Zyg50+foYV2jCgtrqSA6qNuNSA== - dependencies: - defer-to-connect "^1.0.1" - -"@trysound/sax@0.2.0": - version "0.2.0" - resolved "https://registry.yarnpkg.com/@trysound/sax/-/sax-0.2.0.tgz#cccaab758af56761eb7bf37af6f03f326dd798ad" - integrity sha512-L7z9BgrNEcYyUYtF+HaEfiS5ebkh9jXqbszz7pC0hRBPaatV0XjSD3+eHrpqFemQfgwiFF0QPIarnIihIDn7OA== - -"@types/body-parser@*": - version "1.19.5" - resolved "https://registry.yarnpkg.com/@types/body-parser/-/body-parser-1.19.5.tgz#04ce9a3b677dc8bd681a17da1ab9835dc9d3ede4" - integrity sha512-fB3Zu92ucau0iQ0JMCFQE7b/dv8Ot07NI3KaZIkIUNXq82k4eBAqUaneXfleGY9JWskeS9y+u0nXMyspcuQrCg== - dependencies: - "@types/connect" "*" - "@types/node" "*" - -"@types/bonjour@^3.5.9": - version "3.5.13" - resolved "https://registry.yarnpkg.com/@types/bonjour/-/bonjour-3.5.13.tgz#adf90ce1a105e81dd1f9c61fdc5afda1bfb92956" - integrity sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ== - dependencies: - "@types/node" "*" - -"@types/connect-history-api-fallback@^1.3.5": - version "1.5.4" - resolved "https://registry.yarnpkg.com/@types/connect-history-api-fallback/-/connect-history-api-fallback-1.5.4.tgz#7de71645a103056b48ac3ce07b3520b819c1d5b3" - integrity sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw== - dependencies: - "@types/express-serve-static-core" "*" - "@types/node" "*" - -"@types/connect@*": - version "3.4.38" - resolved "https://registry.yarnpkg.com/@types/connect/-/connect-3.4.38.tgz#5ba7f3bc4fbbdeaff8dded952e5ff2cc53f8d858" - integrity sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug== - dependencies: - "@types/node" "*" - -"@types/estree@^1.0.5": - version "1.0.6" - resolved "https://registry.yarnpkg.com/@types/estree/-/estree-1.0.6.tgz#628effeeae2064a1b4e79f78e81d87b7e5fc7b50" - integrity sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw== - -"@types/express-serve-static-core@*", "@types/express-serve-static-core@^5.0.0": - version "5.0.0" - resolved "https://registry.yarnpkg.com/@types/express-serve-static-core/-/express-serve-static-core-5.0.0.tgz#91f06cda1049e8f17eeab364798ed79c97488a1c" - integrity sha512-AbXMTZGt40T+KON9/Fdxx0B2WK5hsgxcfXJLr5bFpZ7b4JCex2WyQPTEKdXqfHiY5nKKBScZ7yCoO6Pvgxfvnw== - dependencies: - "@types/node" "*" - "@types/qs" "*" - "@types/range-parser" "*" - "@types/send" "*" - -"@types/express-serve-static-core@^4.17.33": - version "4.19.6" - resolved "https://registry.yarnpkg.com/@types/express-serve-static-core/-/express-serve-static-core-4.19.6.tgz#e01324c2a024ff367d92c66f48553ced0ab50267" - integrity sha512-N4LZ2xG7DatVqhCZzOGb1Yi5lMbXSZcmdLDe9EzSndPV2HpWYWzRbaerl2n27irrm94EPpprqa8KpskPT085+A== - dependencies: - "@types/node" "*" - "@types/qs" "*" - "@types/range-parser" "*" - "@types/send" "*" - -"@types/express@*": - version "5.0.0" - resolved "https://registry.yarnpkg.com/@types/express/-/express-5.0.0.tgz#13a7d1f75295e90d19ed6e74cab3678488eaa96c" - integrity sha512-DvZriSMehGHL1ZNLzi6MidnsDhUZM/x2pRdDIKdwbUNqqwHxMlRdkxtn6/EPKyqKpHqTl/4nRZsRNLpZxZRpPQ== - dependencies: - "@types/body-parser" "*" - "@types/express-serve-static-core" "^5.0.0" - "@types/qs" "*" - "@types/serve-static" "*" - -"@types/express@^4.17.13": - version "4.17.21" - resolved "https://registry.yarnpkg.com/@types/express/-/express-4.17.21.tgz#c26d4a151e60efe0084b23dc3369ebc631ed192d" - integrity sha512-ejlPM315qwLpaQlQDTjPdsUFSc6ZsP4AN6AlWnogPjQ7CVi7PYF3YVz+CY3jE2pwYf7E/7HlDAN0rV2GxTG0HQ== - dependencies: - "@types/body-parser" "*" - "@types/express-serve-static-core" "^4.17.33" - "@types/qs" "*" - "@types/serve-static" "*" - -"@types/hast@^2.0.0": - version "2.3.10" - resolved "https://registry.yarnpkg.com/@types/hast/-/hast-2.3.10.tgz#5c9d9e0b304bbb8879b857225c5ebab2d81d7643" - integrity sha512-McWspRw8xx8J9HurkVBfYj0xKoE25tOFlHGdx4MJ5xORQrMGZNqJhVQWaIbm6Oyla5kYOXtDiopzKRJzEOkwJw== - dependencies: - "@types/unist" "^2" - -"@types/history@^4.7.11": - version "4.7.11" - resolved "https://registry.yarnpkg.com/@types/history/-/history-4.7.11.tgz#56588b17ae8f50c53983a524fc3cc47437969d64" - integrity sha512-qjDJRrmvBMiTx+jyLxvLfJU7UznFuokDv4f3WRuriHKERccVpFU+8XMQUAbDzoiJCsmexxRExQeMwwCdamSKDA== - -"@types/html-minifier-terser@^6.0.0": - version "6.1.0" - resolved "https://registry.yarnpkg.com/@types/html-minifier-terser/-/html-minifier-terser-6.1.0.tgz#4fc33a00c1d0c16987b1a20cf92d20614c55ac35" - integrity sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg== - -"@types/http-errors@*": - version "2.0.4" - resolved "https://registry.yarnpkg.com/@types/http-errors/-/http-errors-2.0.4.tgz#7eb47726c391b7345a6ec35ad7f4de469cf5ba4f" - integrity sha512-D0CFMMtydbJAegzOyHjtiKPLlvnm3iTZyZRSZoLq2mRhDdmLfIWOCYPfQJ4cu2erKghU++QvjcUjp/5h7hESpA== - -"@types/http-proxy@^1.17.8": - version "1.17.15" - resolved "https://registry.yarnpkg.com/@types/http-proxy/-/http-proxy-1.17.15.tgz#12118141ce9775a6499ecb4c01d02f90fc839d36" - integrity sha512-25g5atgiVNTIv0LBDTg1H74Hvayx0ajtJPLLcYE3whFv75J0pWNtOBzaXJQgDTmrX1bx5U9YC2w/n65BN1HwRQ== - dependencies: - "@types/node" "*" - -"@types/istanbul-lib-coverage@*", "@types/istanbul-lib-coverage@^2.0.0": - version "2.0.6" - resolved "https://registry.yarnpkg.com/@types/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.6.tgz#7739c232a1fee9b4d3ce8985f314c0c6d33549d7" - integrity sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w== - -"@types/istanbul-lib-report@*": - version "3.0.3" - resolved "https://registry.yarnpkg.com/@types/istanbul-lib-report/-/istanbul-lib-report-3.0.3.tgz#53047614ae72e19fc0401d872de3ae2b4ce350bf" - integrity sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA== - dependencies: - "@types/istanbul-lib-coverage" "*" - -"@types/istanbul-reports@^3.0.0": - version "3.0.4" - resolved "https://registry.yarnpkg.com/@types/istanbul-reports/-/istanbul-reports-3.0.4.tgz#0f03e3d2f670fbdac586e34b433783070cc16f54" - integrity sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ== - dependencies: - "@types/istanbul-lib-report" "*" - -"@types/json-schema@^7.0.4", "@types/json-schema@^7.0.5", "@types/json-schema@^7.0.8", "@types/json-schema@^7.0.9": - version "7.0.15" - resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.15.tgz#596a1747233694d50f6ad8a7869fcb6f56cf5841" - integrity sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA== - -"@types/mdast@^3.0.0": - version "3.0.15" - resolved "https://registry.yarnpkg.com/@types/mdast/-/mdast-3.0.15.tgz#49c524a263f30ffa28b71ae282f813ed000ab9f5" - integrity sha512-LnwD+mUEfxWMa1QpDraczIn6k0Ee3SMicuYSSzS6ZYl2gKS09EClnJYGd8Du6rfc5r/GZEk5o1mRb8TaTj03sQ== - dependencies: - "@types/unist" "^2" - -"@types/mime@^1": - version "1.3.5" - resolved "https://registry.yarnpkg.com/@types/mime/-/mime-1.3.5.tgz#1ef302e01cf7d2b5a0fa526790c9123bf1d06690" - integrity sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w== - -"@types/node-forge@^1.3.0": - version "1.3.11" - resolved "https://registry.yarnpkg.com/@types/node-forge/-/node-forge-1.3.11.tgz#0972ea538ddb0f4d9c2fa0ec5db5724773a604da" - integrity sha512-FQx220y22OKNTqaByeBGqHWYz4cl94tpcxeFdvBo3wjG6XPBuZ0BNgNZRV5J5TFmmcsJ4IzsLkmGRiQbnYsBEQ== - dependencies: - "@types/node" "*" - -"@types/node@*": - version "22.7.8" - resolved "https://registry.yarnpkg.com/@types/node/-/node-22.7.8.tgz#a1dbf0dc5f71bdd2642fc89caef65d58747ce825" - integrity sha512-a922jJy31vqR5sk+kAdIENJjHblqcZ4RmERviFsER4WJcEONqxKcjNOlk0q7OUfrF5sddT+vng070cdfMlrPLg== - dependencies: - undici-types "~6.19.2" - -"@types/node@^17.0.5": - version "17.0.45" - resolved "https://registry.yarnpkg.com/@types/node/-/node-17.0.45.tgz#2c0fafd78705e7a18b7906b5201a522719dc5190" - integrity sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw== - -"@types/parse-json@^4.0.0": - version "4.0.2" - resolved "https://registry.yarnpkg.com/@types/parse-json/-/parse-json-4.0.2.tgz#5950e50960793055845e956c427fc2b0d70c5239" - integrity sha512-dISoDXWWQwUquiKsyZ4Ng+HX2KsPL7LyHKHQwgGFEA3IaKac4Obd+h2a/a6waisAoepJlBcx9paWqjA8/HVjCw== - -"@types/parse5@^5.0.0": - version "5.0.3" - resolved "https://registry.yarnpkg.com/@types/parse5/-/parse5-5.0.3.tgz#e7b5aebbac150f8b5fdd4a46e7f0bd8e65e19109" - integrity sha512-kUNnecmtkunAoQ3CnjmMkzNU/gtxG8guhi+Fk2U/kOpIKjIMKnXGp4IJCgQJrXSgMsWYimYG4TGjz/UzbGEBTw== - -"@types/prop-types@*": - version "15.7.13" - resolved "https://registry.yarnpkg.com/@types/prop-types/-/prop-types-15.7.13.tgz#2af91918ee12d9d32914feb13f5326658461b451" - integrity sha512-hCZTSvwbzWGvhqxp/RqVqwU999pBf2vp7hzIjiYOsl8wqOmUxkQ6ddw1cV3l8811+kdUFus/q4d1Y3E3SyEifA== - -"@types/qs@*": - version "6.9.16" - resolved "https://registry.yarnpkg.com/@types/qs/-/qs-6.9.16.tgz#52bba125a07c0482d26747d5d4947a64daf8f794" - integrity sha512-7i+zxXdPD0T4cKDuxCUXJ4wHcsJLwENa6Z3dCu8cfCK743OGy5Nu1RmAGqDPsoTDINVEcdXKRvR/zre+P2Ku1A== - -"@types/range-parser@*": - version "1.2.7" - resolved "https://registry.yarnpkg.com/@types/range-parser/-/range-parser-1.2.7.tgz#50ae4353eaaddc04044279812f52c8c65857dbcb" - integrity sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ== - -"@types/react-router-config@*", "@types/react-router-config@^5.0.6": - version "5.0.11" - resolved "https://registry.yarnpkg.com/@types/react-router-config/-/react-router-config-5.0.11.tgz#2761a23acc7905a66a94419ee40294a65aaa483a" - integrity sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw== - dependencies: - "@types/history" "^4.7.11" - "@types/react" "*" - "@types/react-router" "^5.1.0" - -"@types/react-router-dom@*": - version "5.3.3" - resolved "https://registry.yarnpkg.com/@types/react-router-dom/-/react-router-dom-5.3.3.tgz#e9d6b4a66fcdbd651a5f106c2656a30088cc1e83" - integrity sha512-kpqnYK4wcdm5UaWI3fLcELopqLrHgLqNsdpHauzlQktfkHL3npOSwtj1Uz9oKBAzs7lFtVkV8j83voAz2D8fhw== - dependencies: - "@types/history" "^4.7.11" - "@types/react" "*" - "@types/react-router" "*" - -"@types/react-router@*", "@types/react-router@^5.1.0": - version "5.1.20" - resolved "https://registry.yarnpkg.com/@types/react-router/-/react-router-5.1.20.tgz#88eccaa122a82405ef3efbcaaa5dcdd9f021387c" - integrity sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q== - dependencies: - "@types/history" "^4.7.11" - "@types/react" "*" - -"@types/react@*": - version "18.3.11" - resolved "https://registry.yarnpkg.com/@types/react/-/react-18.3.11.tgz#9d530601ff843ee0d7030d4227ea4360236bd537" - integrity sha512-r6QZ069rFTjrEYgFdOck1gK7FLVsgJE7tTz0pQBczlBNUhBNk0MQH4UbnFSwjpQLMkLzgqvBBa+qGpLje16eTQ== - dependencies: - "@types/prop-types" "*" - csstype "^3.0.2" - -"@types/retry@0.12.0": - version "0.12.0" - resolved "https://registry.yarnpkg.com/@types/retry/-/retry-0.12.0.tgz#2b35eccfcee7d38cd72ad99232fbd58bffb3c84d" - integrity sha512-wWKOClTTiizcZhXnPY4wikVAwmdYHp8q6DmC+EJUzAMsycb7HB32Kh9RN4+0gExjmPmZSAQjgURXIGATPegAvA== - -"@types/sax@^1.2.1": - version "1.2.7" - resolved "https://registry.yarnpkg.com/@types/sax/-/sax-1.2.7.tgz#ba5fe7df9aa9c89b6dff7688a19023dd2963091d" - integrity sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A== - dependencies: - "@types/node" "*" - -"@types/send@*": - version "0.17.4" - resolved "https://registry.yarnpkg.com/@types/send/-/send-0.17.4.tgz#6619cd24e7270793702e4e6a4b958a9010cfc57a" - integrity sha512-x2EM6TJOybec7c52BX0ZspPodMsQUd5L6PRwOunVyVUhXiBSKf3AezDL8Dgvgt5o0UfKNfuA0eMLr2wLT4AiBA== - dependencies: - "@types/mime" "^1" - "@types/node" "*" - -"@types/serve-index@^1.9.1": - version "1.9.4" - resolved "https://registry.yarnpkg.com/@types/serve-index/-/serve-index-1.9.4.tgz#e6ae13d5053cb06ed36392110b4f9a49ac4ec898" - integrity sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug== - dependencies: - "@types/express" "*" - -"@types/serve-static@*", "@types/serve-static@^1.13.10": - version "1.15.7" - resolved "https://registry.yarnpkg.com/@types/serve-static/-/serve-static-1.15.7.tgz#22174bbd74fb97fe303109738e9b5c2f3064f714" - integrity sha512-W8Ym+h8nhuRwaKPaDw34QUkwsGi6Rc4yYqvKFo5rm2FUEhCFbzVWrxXUxuKK8TASjWsysJY0nsmNCGhCOIsrOw== - dependencies: - "@types/http-errors" "*" - "@types/node" "*" - "@types/send" "*" - -"@types/sockjs@^0.3.33": - version "0.3.36" - resolved "https://registry.yarnpkg.com/@types/sockjs/-/sockjs-0.3.36.tgz#ce322cf07bcc119d4cbf7f88954f3a3bd0f67535" - integrity sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q== - dependencies: - "@types/node" "*" - -"@types/unist@^2", "@types/unist@^2.0.0", "@types/unist@^2.0.2", "@types/unist@^2.0.3": - version "2.0.11" - resolved "https://registry.yarnpkg.com/@types/unist/-/unist-2.0.11.tgz#11af57b127e32487774841f7a4e54eab166d03c4" - integrity sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA== - -"@types/ws@^8.5.5": - version "8.5.12" - resolved "https://registry.yarnpkg.com/@types/ws/-/ws-8.5.12.tgz#619475fe98f35ccca2a2f6c137702d85ec247b7e" - integrity sha512-3tPRkv1EtkDpzlgyKyI8pGsGZAGPEaXeu0DOj5DI25Ja91bdAYddYHbADRYVrZMRbfW+1l5YwXVDKohDJNQxkQ== - dependencies: - "@types/node" "*" - -"@types/yargs-parser@*": - version "21.0.3" - resolved "https://registry.yarnpkg.com/@types/yargs-parser/-/yargs-parser-21.0.3.tgz#815e30b786d2e8f0dcd85fd5bcf5e1a04d008f15" - integrity sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ== - -"@types/yargs@^17.0.8": - version "17.0.33" - resolved "https://registry.yarnpkg.com/@types/yargs/-/yargs-17.0.33.tgz#8c32303da83eec050a84b3c7ae7b9f922d13e32d" - integrity sha512-WpxBCKWPLr4xSsHgz511rFJAM+wS28w2zEO1QDNY5zM/S8ok70NNfztH0xwhqKyaK0OHCbN98LDAZuy1ctxDkA== - dependencies: - "@types/yargs-parser" "*" - -"@webassemblyjs/ast@1.12.1", "@webassemblyjs/ast@^1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/ast/-/ast-1.12.1.tgz#bb16a0e8b1914f979f45864c23819cc3e3f0d4bb" - integrity sha512-EKfMUOPRRUTy5UII4qJDGPpqfwjOmZ5jeGFwid9mnoqIFK+e0vqoi1qH56JpmZSzEL53jKnNzScdmftJyG5xWg== - dependencies: - "@webassemblyjs/helper-numbers" "1.11.6" - "@webassemblyjs/helper-wasm-bytecode" "1.11.6" - -"@webassemblyjs/floating-point-hex-parser@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.11.6.tgz#dacbcb95aff135c8260f77fa3b4c5fea600a6431" - integrity sha512-ejAj9hfRJ2XMsNHk/v6Fu2dGS+i4UaXBXGemOfQ/JfQ6mdQg/WXtwleQRLLS4OvfDhv8rYnVwH27YJLMyYsxhw== - -"@webassemblyjs/helper-api-error@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-api-error/-/helper-api-error-1.11.6.tgz#6132f68c4acd59dcd141c44b18cbebbd9f2fa768" - integrity sha512-o0YkoP4pVu4rN8aTJgAyj9hC2Sv5UlkzCHhxqWj8butaLvnpdc2jOwh4ewE6CX0txSfLn/UYaV/pheS2Txg//Q== - -"@webassemblyjs/helper-buffer@1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-buffer/-/helper-buffer-1.12.1.tgz#6df20d272ea5439bf20ab3492b7fb70e9bfcb3f6" - integrity sha512-nzJwQw99DNDKr9BVCOZcLuJJUlqkJh+kVzVl6Fmq/tI5ZtEyWT1KZMyOXltXLZJmDtvLCDgwsyrkohEtopTXCw== - -"@webassemblyjs/helper-numbers@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-numbers/-/helper-numbers-1.11.6.tgz#cbce5e7e0c1bd32cf4905ae444ef64cea919f1b5" - integrity sha512-vUIhZ8LZoIWHBohiEObxVm6hwP034jwmc9kuq5GdHZH0wiLVLIPcMCdpJzG4C11cHoQ25TFIQj9kaVADVX7N3g== - dependencies: - "@webassemblyjs/floating-point-hex-parser" "1.11.6" - "@webassemblyjs/helper-api-error" "1.11.6" - "@xtuc/long" "4.2.2" - -"@webassemblyjs/helper-wasm-bytecode@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.6.tgz#bb2ebdb3b83aa26d9baad4c46d4315283acd51e9" - integrity sha512-sFFHKwcmBprO9e7Icf0+gddyWYDViL8bpPjJJl0WHxCdETktXdmtWLGVzoHbqUcY4Be1LkNfwTmXOJUFZYSJdA== - -"@webassemblyjs/helper-wasm-section@1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.12.1.tgz#3da623233ae1a60409b509a52ade9bc22a37f7bf" - integrity sha512-Jif4vfB6FJlUlSbgEMHUyk1j234GTNG9dBJ4XJdOySoj518Xj0oGsNi59cUQF4RRMS9ouBUxDDdyBVfPTypa5g== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@webassemblyjs/helper-buffer" "1.12.1" - "@webassemblyjs/helper-wasm-bytecode" "1.11.6" - "@webassemblyjs/wasm-gen" "1.12.1" - -"@webassemblyjs/ieee754@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/ieee754/-/ieee754-1.11.6.tgz#bb665c91d0b14fffceb0e38298c329af043c6e3a" - integrity sha512-LM4p2csPNvbij6U1f19v6WR56QZ8JcHg3QIJTlSwzFcmx6WSORicYj6I63f9yU1kEUtrpG+kjkiIAkevHpDXrg== - dependencies: - "@xtuc/ieee754" "^1.2.0" - -"@webassemblyjs/leb128@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/leb128/-/leb128-1.11.6.tgz#70e60e5e82f9ac81118bc25381a0b283893240d7" - integrity sha512-m7a0FhE67DQXgouf1tbN5XQcdWoNgaAuoULHIfGFIEVKA6tu/edls6XnIlkmS6FrXAquJRPni3ZZKjw6FSPjPQ== - dependencies: - "@xtuc/long" "4.2.2" - -"@webassemblyjs/utf8@1.11.6": - version "1.11.6" - resolved "https://registry.yarnpkg.com/@webassemblyjs/utf8/-/utf8-1.11.6.tgz#90f8bc34c561595fe156603be7253cdbcd0fab5a" - integrity sha512-vtXf2wTQ3+up9Zsg8sa2yWiQpzSsMyXj0qViVP6xKGCUT8p8YJ6HqI7l5eCnWx1T/FYdsv07HQs2wTFbbof/RA== - -"@webassemblyjs/wasm-edit@^1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-edit/-/wasm-edit-1.12.1.tgz#9f9f3ff52a14c980939be0ef9d5df9ebc678ae3b" - integrity sha512-1DuwbVvADvS5mGnXbE+c9NfA8QRcZ6iKquqjjmR10k6o+zzsRVesil54DKexiowcFCPdr/Q0qaMgB01+SQ1u6g== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@webassemblyjs/helper-buffer" "1.12.1" - "@webassemblyjs/helper-wasm-bytecode" "1.11.6" - "@webassemblyjs/helper-wasm-section" "1.12.1" - "@webassemblyjs/wasm-gen" "1.12.1" - "@webassemblyjs/wasm-opt" "1.12.1" - "@webassemblyjs/wasm-parser" "1.12.1" - "@webassemblyjs/wast-printer" "1.12.1" - -"@webassemblyjs/wasm-gen@1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-gen/-/wasm-gen-1.12.1.tgz#a6520601da1b5700448273666a71ad0a45d78547" - integrity sha512-TDq4Ojh9fcohAw6OIMXqiIcTq5KUXTGRkVxbSo1hQnSy6lAM5GSdfwWeSxpAo0YzgsgF182E/U0mDNhuA0tW7w== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@webassemblyjs/helper-wasm-bytecode" "1.11.6" - "@webassemblyjs/ieee754" "1.11.6" - "@webassemblyjs/leb128" "1.11.6" - "@webassemblyjs/utf8" "1.11.6" - -"@webassemblyjs/wasm-opt@1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-opt/-/wasm-opt-1.12.1.tgz#9e6e81475dfcfb62dab574ac2dda38226c232bc5" - integrity sha512-Jg99j/2gG2iaz3hijw857AVYekZe2SAskcqlWIZXjji5WStnOpVoat3gQfT/Q5tb2djnCjBtMocY/Su1GfxPBg== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@webassemblyjs/helper-buffer" "1.12.1" - "@webassemblyjs/wasm-gen" "1.12.1" - "@webassemblyjs/wasm-parser" "1.12.1" - -"@webassemblyjs/wasm-parser@1.12.1", "@webassemblyjs/wasm-parser@^1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-parser/-/wasm-parser-1.12.1.tgz#c47acb90e6f083391e3fa61d113650eea1e95937" - integrity sha512-xikIi7c2FHXysxXe3COrVUPSheuBtpcfhbpFj4gmu7KRLYOzANztwUU0IbsqvMqzuNK2+glRGWCEqZo1WCLyAQ== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@webassemblyjs/helper-api-error" "1.11.6" - "@webassemblyjs/helper-wasm-bytecode" "1.11.6" - "@webassemblyjs/ieee754" "1.11.6" - "@webassemblyjs/leb128" "1.11.6" - "@webassemblyjs/utf8" "1.11.6" - -"@webassemblyjs/wast-printer@1.12.1": - version "1.12.1" - resolved "https://registry.yarnpkg.com/@webassemblyjs/wast-printer/-/wast-printer-1.12.1.tgz#bcecf661d7d1abdaf989d8341a4833e33e2b31ac" - integrity sha512-+X4WAlOisVWQMikjbcvY2e0rwPsKQ9F688lksZhBcPycBBuii3O7m8FACbDMWDojpAqvjIncrG8J0XHKyQfVeA== - dependencies: - "@webassemblyjs/ast" "1.12.1" - "@xtuc/long" "4.2.2" - -"@xtuc/ieee754@^1.2.0": - version "1.2.0" - resolved "https://registry.yarnpkg.com/@xtuc/ieee754/-/ieee754-1.2.0.tgz#eef014a3145ae477a1cbc00cd1e552336dceb790" - integrity sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA== - -"@xtuc/long@4.2.2": - version "4.2.2" - resolved "https://registry.yarnpkg.com/@xtuc/long/-/long-4.2.2.tgz#d291c6a4e97989b5c61d9acf396ae4fe133a718d" - integrity sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ== - -accepts@~1.3.4, accepts@~1.3.5, accepts@~1.3.8: - version "1.3.8" - resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.3.8.tgz#0bf0be125b67014adcb0b0921e62db7bffe16b2e" - integrity sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw== - dependencies: - mime-types "~2.1.34" - negotiator "0.6.3" - -acorn-import-attributes@^1.9.5: - version "1.9.5" - resolved "https://registry.yarnpkg.com/acorn-import-attributes/-/acorn-import-attributes-1.9.5.tgz#7eb1557b1ba05ef18b5ed0ec67591bfab04688ef" - integrity sha512-n02Vykv5uA3eHGM/Z2dQrcD56kL8TyDb2p1+0P83PClMnC/nc+anbQRhIOWnSq4Ke/KvDPrY3C9hDtC/A3eHnQ== - -acorn-walk@^8.0.0: - version "8.3.4" - resolved "https://registry.yarnpkg.com/acorn-walk/-/acorn-walk-8.3.4.tgz#794dd169c3977edf4ba4ea47583587c5866236b7" - integrity sha512-ueEepnujpqee2o5aIYnvHU6C0A42MNdsIDeqy5BydrkuC5R1ZuUFnm27EeFJGoEHJQgn3uleRvmTXaJgfXbt4g== - dependencies: - acorn "^8.11.0" - -acorn@^8.0.4, acorn@^8.11.0, acorn@^8.7.1, acorn@^8.8.2: - version "8.13.0" - resolved "https://registry.yarnpkg.com/acorn/-/acorn-8.13.0.tgz#2a30d670818ad16ddd6a35d3842dacec9e5d7ca3" - integrity sha512-8zSiw54Oxrdym50NlZ9sUusyO1Z1ZchgRLWRaK6c86XJFClyCgFKetdowBg5bKxyp/u+CDBJG4Mpp0m3HLZl9w== - -address@^1.0.1, address@^1.1.2: - version "1.2.2" - resolved "https://registry.yarnpkg.com/address/-/address-1.2.2.tgz#2b5248dac5485a6390532c6a517fda2e3faac89e" - integrity sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA== - -aggregate-error@^3.0.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/aggregate-error/-/aggregate-error-3.1.0.tgz#92670ff50f5359bdb7a3e0d40d0ec30c5737687a" - integrity sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA== - dependencies: - clean-stack "^2.0.0" - indent-string "^4.0.0" - -ajv-formats@^2.1.1: - version "2.1.1" - resolved "https://registry.yarnpkg.com/ajv-formats/-/ajv-formats-2.1.1.tgz#6e669400659eb74973bbf2e33327180a0996b520" - integrity sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA== - dependencies: - ajv "^8.0.0" - -ajv-keywords@^3.4.1, ajv-keywords@^3.5.2: - version "3.5.2" - resolved "https://registry.yarnpkg.com/ajv-keywords/-/ajv-keywords-3.5.2.tgz#31f29da5ab6e00d1c2d329acf7b5929614d5014d" - integrity sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ== - -ajv-keywords@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/ajv-keywords/-/ajv-keywords-5.1.0.tgz#69d4d385a4733cdbeab44964a1170a88f87f0e16" - integrity sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw== - dependencies: - fast-deep-equal "^3.1.3" - -ajv@^6.12.2, ajv@^6.12.4, ajv@^6.12.5: - version "6.12.6" - resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.12.6.tgz#baf5a62e802b07d977034586f8c3baf5adf26df4" - integrity sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g== - dependencies: - fast-deep-equal "^3.1.1" - fast-json-stable-stringify "^2.0.0" - json-schema-traverse "^0.4.1" - uri-js "^4.2.2" - -ajv@^8.0.0, ajv@^8.9.0: - version "8.17.1" - resolved "https://registry.yarnpkg.com/ajv/-/ajv-8.17.1.tgz#37d9a5c776af6bc92d7f4f9510eba4c0a60d11a6" - integrity sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g== - dependencies: - fast-deep-equal "^3.1.3" - fast-uri "^3.0.1" - json-schema-traverse "^1.0.0" - require-from-string "^2.0.2" - -algoliasearch-helper@^3.10.0: - version "3.22.5" - resolved "https://registry.yarnpkg.com/algoliasearch-helper/-/algoliasearch-helper-3.22.5.tgz#2fcc26814e10a121a2c2526a1b05c754061c56c0" - integrity sha512-lWvhdnc+aKOKx8jyA3bsdEgHzm/sglC4cYdMG4xSQyRiPLJVJtH/IVYZG3Hp6PkTEhQqhyVYkeP9z2IlcHJsWw== - dependencies: - "@algolia/events" "^4.0.1" - -algoliasearch@^4.12.0, algoliasearch@^4.13.1, algoliasearch@^4.19.1: - version "4.24.0" - resolved "https://registry.yarnpkg.com/algoliasearch/-/algoliasearch-4.24.0.tgz#b953b3e2309ef8f25da9de311b95b994ac918275" - integrity sha512-bf0QV/9jVejssFBmz2HQLxUadxk574t4iwjCKp5E7NBzwKkrDEhKPISIIjAU/p6K5qDx3qoeh4+26zWN1jmw3g== - dependencies: - "@algolia/cache-browser-local-storage" "4.24.0" - "@algolia/cache-common" "4.24.0" - "@algolia/cache-in-memory" "4.24.0" - "@algolia/client-account" "4.24.0" - "@algolia/client-analytics" "4.24.0" - "@algolia/client-common" "4.24.0" - "@algolia/client-personalization" "4.24.0" - "@algolia/client-search" "4.24.0" - "@algolia/logger-common" "4.24.0" - "@algolia/logger-console" "4.24.0" - "@algolia/recommend" "4.24.0" - "@algolia/requester-browser-xhr" "4.24.0" - "@algolia/requester-common" "4.24.0" - "@algolia/requester-node-http" "4.24.0" - "@algolia/transporter" "4.24.0" - -ansi-align@^3.0.0, ansi-align@^3.0.1: - version "3.0.1" - resolved "https://registry.yarnpkg.com/ansi-align/-/ansi-align-3.0.1.tgz#0cdf12e111ace773a86e9a1fad1225c43cb19a59" - integrity sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w== - dependencies: - string-width "^4.1.0" - -ansi-html-community@^0.0.8: - version "0.0.8" - resolved "https://registry.yarnpkg.com/ansi-html-community/-/ansi-html-community-0.0.8.tgz#69fbc4d6ccbe383f9736934ae34c3f8290f1bf41" - integrity sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw== - -ansi-regex@^5.0.1: - version "5.0.1" - resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.1.tgz#082cb2c89c9fe8659a311a53bd6a4dc5301db304" - integrity sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ== - -ansi-regex@^6.0.1: - version "6.1.0" - resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-6.1.0.tgz#95ec409c69619d6cb1b8b34f14b660ef28ebd654" - integrity sha512-7HSX4QQb4CspciLpVFwyRe79O3xsIZDDLER21kERQ71oaPodF8jL725AgJMFAYbooIqolJoRLuM81SpeUkpkvA== - -ansi-styles@^3.2.1: - version "3.2.1" - resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d" - integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA== - dependencies: - color-convert "^1.9.0" - -ansi-styles@^4.0.0, ansi-styles@^4.1.0: - version "4.3.0" - resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.3.0.tgz#edd803628ae71c04c85ae7a0906edad34b648937" - integrity sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg== - dependencies: - color-convert "^2.0.1" - -ansi-styles@^6.1.0: - version "6.2.1" - resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-6.2.1.tgz#0e62320cf99c21afff3b3012192546aacbfb05c5" - integrity sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug== - -anymatch@~3.1.2: - version "3.1.3" - resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-3.1.3.tgz#790c58b19ba1720a84205b57c618d5ad8524973e" - integrity sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw== - dependencies: - normalize-path "^3.0.0" - picomatch "^2.0.4" - -arg@^5.0.0: - version "5.0.2" - resolved "https://registry.yarnpkg.com/arg/-/arg-5.0.2.tgz#c81433cc427c92c4dcf4865142dbca6f15acd59c" - integrity sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg== - -argparse@^1.0.7: - version "1.0.10" - resolved "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz#bcd6791ea5ae09725e17e5ad988134cd40b3d911" - integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg== - dependencies: - sprintf-js "~1.0.2" - -argparse@^2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/argparse/-/argparse-2.0.1.tgz#246f50f3ca78a3240f6c997e8a9bd1eac49e4b38" - integrity sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q== - -array-flatten@1.1.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-1.1.1.tgz#9a5f699051b1e7073328f2a008968b64ea2955d2" - integrity sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg== - -array-union@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/array-union/-/array-union-2.1.0.tgz#b798420adbeb1de828d84acd8a2e23d3efe85e8d" - integrity sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw== - -asap@~2.0.3: - version "2.0.6" - resolved "https://registry.yarnpkg.com/asap/-/asap-2.0.6.tgz#e50347611d7e690943208bbdafebcbc2fb866d46" - integrity sha512-BSHWgDSAiKs50o2Re8ppvp3seVHXSRM44cdSsT9FfNEUUZLOGWVCsiWaRPWM1Znn+mqZ1OfVZ3z3DWEzSp7hRA== - -at-least-node@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/at-least-node/-/at-least-node-1.0.0.tgz#602cd4b46e844ad4effc92a8011a3c46e0238dc2" - integrity sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg== - -autoprefixer@^10.4.12, autoprefixer@^10.4.7: - version "10.4.20" - resolved "https://registry.yarnpkg.com/autoprefixer/-/autoprefixer-10.4.20.tgz#5caec14d43976ef42e32dcb4bd62878e96be5b3b" - integrity sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g== - dependencies: - browserslist "^4.23.3" - caniuse-lite "^1.0.30001646" - fraction.js "^4.3.7" - normalize-range "^0.1.2" - picocolors "^1.0.1" - postcss-value-parser "^4.2.0" - -axios@^0.25.0: - version "0.25.0" - resolved "https://registry.yarnpkg.com/axios/-/axios-0.25.0.tgz#349cfbb31331a9b4453190791760a8d35b093e0a" - integrity sha512-cD8FOb0tRH3uuEe6+evtAbgJtfxr7ly3fQjYcMcuPlgkwVS9xboaVIpcDV+cYQe+yGykgwZCs1pzjntcGa6l5g== - dependencies: - follow-redirects "^1.14.7" - -babel-loader@^8.2.5: - version "8.4.1" - resolved "https://registry.yarnpkg.com/babel-loader/-/babel-loader-8.4.1.tgz#6ccb75c66e62c3b144e1c5f2eaec5b8f6c08c675" - integrity sha512-nXzRChX+Z1GoE6yWavBQg6jDslyFF3SDjl2paADuoQtQW10JqShJt62R6eJQ5m/pjJFDT8xgKIWSP85OY8eXeA== - dependencies: - find-cache-dir "^3.3.1" - loader-utils "^2.0.4" - make-dir "^3.1.0" - schema-utils "^2.6.5" - -babel-plugin-apply-mdx-type-prop@1.6.22: - version "1.6.22" - resolved "https://registry.yarnpkg.com/babel-plugin-apply-mdx-type-prop/-/babel-plugin-apply-mdx-type-prop-1.6.22.tgz#d216e8fd0de91de3f1478ef3231e05446bc8705b" - integrity sha512-VefL+8o+F/DfK24lPZMtJctrCVOfgbqLAGZSkxwhazQv4VxPg3Za/i40fu22KR2m8eEda+IfSOlPLUSIiLcnCQ== - dependencies: - "@babel/helper-plugin-utils" "7.10.4" - "@mdx-js/util" "1.6.22" - -babel-plugin-dynamic-import-node@^2.3.3: - version "2.3.3" - resolved "https://registry.yarnpkg.com/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.3.tgz#84fda19c976ec5c6defef57f9427b3def66e17a3" - integrity sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ== - dependencies: - object.assign "^4.1.0" - -babel-plugin-extract-import-names@1.6.22: - version "1.6.22" - resolved "https://registry.yarnpkg.com/babel-plugin-extract-import-names/-/babel-plugin-extract-import-names-1.6.22.tgz#de5f9a28eb12f3eb2578bf74472204e66d1a13dc" - integrity sha512-yJ9BsJaISua7d8zNT7oRG1ZLBJCIdZ4PZqmH8qa9N5AK01ifk3fnkc98AXhtzE7UkfCsEumvoQWgoYLhOnJ7jQ== - dependencies: - "@babel/helper-plugin-utils" "7.10.4" - -babel-plugin-polyfill-corejs2@^0.4.10: - version "0.4.11" - resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.4.11.tgz#30320dfe3ffe1a336c15afdcdafd6fd615b25e33" - integrity sha512-sMEJ27L0gRHShOh5G54uAAPaiCOygY/5ratXuiyb2G46FmlSpc9eFCzYVyDiPxfNbwzA7mYahmjQc5q+CZQ09Q== - dependencies: - "@babel/compat-data" "^7.22.6" - "@babel/helper-define-polyfill-provider" "^0.6.2" - semver "^6.3.1" - -babel-plugin-polyfill-corejs3@^0.10.6: - version "0.10.6" - resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.10.6.tgz#2deda57caef50f59c525aeb4964d3b2f867710c7" - integrity sha512-b37+KR2i/khY5sKmWNVQAnitvquQbNdWy6lJdsr0kmquCKEEUgMKK4SboVM3HtfnZilfjr4MMQ7vY58FVWDtIA== - dependencies: - "@babel/helper-define-polyfill-provider" "^0.6.2" - core-js-compat "^3.38.0" - -babel-plugin-polyfill-regenerator@^0.6.1: - version "0.6.2" - resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.6.2.tgz#addc47e240edd1da1058ebda03021f382bba785e" - integrity sha512-2R25rQZWP63nGwaAswvDazbPXfrM3HwVoBXK6HcqeKrSrL/JqcC/rDcf95l4r7LXLyxDXc8uQDa064GubtCABg== - dependencies: - "@babel/helper-define-polyfill-provider" "^0.6.2" - -bail@^1.0.0: - version "1.0.5" - resolved "https://registry.yarnpkg.com/bail/-/bail-1.0.5.tgz#b6fa133404a392cbc1f8c4bf63f5953351e7a776" - integrity sha512-xFbRxM1tahm08yHBP16MMjVUAvDaBMD38zsM9EMAUN61omwLmKlOpB/Zku5QkjZ8TZ4vn53pj+t518cH0S03RQ== - -balanced-match@^1.0.0: - version "1.0.2" - resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz#e83e3a7e3f300b34cb9d87f615fa0cbf357690ee" - integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw== - -base16@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/base16/-/base16-1.0.0.tgz#e297f60d7ec1014a7a971a39ebc8a98c0b681e70" - integrity sha512-pNdYkNPiJUnEhnfXV56+sQy8+AaPcG3POZAUnwr4EeqCUZFz4u2PePbo3e5Gj4ziYPCWGUZT9RHisvJKnwFuBQ== - -base64-js@^1.3.1: - version "1.5.1" - resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.5.1.tgz#1b1b440160a5bf7ad40b650f095963481903930a" - integrity sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA== - -batch@0.6.1: - version "0.6.1" - resolved "https://registry.yarnpkg.com/batch/-/batch-0.6.1.tgz#dc34314f4e679318093fc760272525f94bf25c16" - integrity sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw== - -big.js@^5.2.2: - version "5.2.2" - resolved "https://registry.yarnpkg.com/big.js/-/big.js-5.2.2.tgz#65f0af382f578bcdc742bd9c281e9cb2d7768328" - integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ== - -binary-extensions@^2.0.0: - version "2.3.0" - resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-2.3.0.tgz#f6e14a97858d327252200242d4ccfe522c445522" - integrity sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw== - -bl@^4.0.3: - version "4.1.0" - resolved "https://registry.yarnpkg.com/bl/-/bl-4.1.0.tgz#451535264182bec2fbbc83a62ab98cf11d9f7b3a" - integrity sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w== - dependencies: - buffer "^5.5.0" - inherits "^2.0.4" - readable-stream "^3.4.0" - -body-parser@1.20.3: - version "1.20.3" - resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.20.3.tgz#1953431221c6fb5cd63c4b36d53fab0928e548c6" - integrity sha512-7rAxByjUMqQ3/bHJy7D6OGXvx/MMc4IqBn/X0fcM1QUcAItpZrBEYhWGem+tzXH90c+G01ypMcYJBO9Y30203g== - dependencies: - bytes "3.1.2" - content-type "~1.0.5" - debug "2.6.9" - depd "2.0.0" - destroy "1.2.0" - http-errors "2.0.0" - iconv-lite "0.4.24" - on-finished "2.4.1" - qs "6.13.0" - raw-body "2.5.2" - type-is "~1.6.18" - unpipe "1.0.0" - -bonjour-service@^1.0.11: - version "1.2.1" - resolved "https://registry.yarnpkg.com/bonjour-service/-/bonjour-service-1.2.1.tgz#eb41b3085183df3321da1264719fbada12478d02" - integrity sha512-oSzCS2zV14bh2kji6vNe7vrpJYCHGvcZnlffFQ1MEoX/WOeQ/teD8SYWKR942OI3INjq8OMNJlbPK5LLLUxFDw== - dependencies: - fast-deep-equal "^3.1.3" - multicast-dns "^7.2.5" - -boolbase@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/boolbase/-/boolbase-1.0.0.tgz#68dff5fbe60c51eb37725ea9e3ed310dcc1e776e" - integrity sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww== - -boxen@^5.0.0: - version "5.1.2" - resolved "https://registry.yarnpkg.com/boxen/-/boxen-5.1.2.tgz#788cb686fc83c1f486dfa8a40c68fc2b831d2b50" - integrity sha512-9gYgQKXx+1nP8mP7CzFyaUARhg7D3n1dF/FnErWmu9l6JvGpNUN278h0aSb+QjoiKSWG+iZ3uHrcqk0qrY9RQQ== - dependencies: - ansi-align "^3.0.0" - camelcase "^6.2.0" - chalk "^4.1.0" - cli-boxes "^2.2.1" - string-width "^4.2.2" - type-fest "^0.20.2" - widest-line "^3.1.0" - wrap-ansi "^7.0.0" - -boxen@^6.2.1: - version "6.2.1" - resolved "https://registry.yarnpkg.com/boxen/-/boxen-6.2.1.tgz#b098a2278b2cd2845deef2dff2efc38d329b434d" - integrity sha512-H4PEsJXfFI/Pt8sjDWbHlQPx4zL/bvSQjcilJmaulGt5mLDorHOHpmdXAJcBcmru7PhYSp/cDMWRko4ZUMFkSw== - dependencies: - ansi-align "^3.0.1" - camelcase "^6.2.0" - chalk "^4.1.2" - cli-boxes "^3.0.0" - string-width "^5.0.1" - type-fest "^2.5.0" - widest-line "^4.0.1" - wrap-ansi "^8.0.1" - -brace-expansion@^1.1.7: - version "1.1.11" - resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd" - integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA== - dependencies: - balanced-match "^1.0.0" - concat-map "0.0.1" - -braces@^3.0.3, braces@~3.0.2: - version "3.0.3" - resolved "https://registry.yarnpkg.com/braces/-/braces-3.0.3.tgz#490332f40919452272d55a8480adc0c441358789" - integrity sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA== - dependencies: - fill-range "^7.1.1" - -browserslist@^4.0.0, browserslist@^4.18.1, browserslist@^4.21.10, browserslist@^4.21.4, browserslist@^4.23.3, browserslist@^4.24.0: - version "4.24.2" - resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.24.2.tgz#f5845bc91069dbd55ee89faf9822e1d885d16580" - integrity sha512-ZIc+Q62revdMcqC6aChtW4jz3My3klmCO1fEmINZY/8J3EpBg5/A/D0AKmBveUh6pgoeycoMkVMko84tuYS+Gg== - dependencies: - caniuse-lite "^1.0.30001669" - electron-to-chromium "^1.5.41" - node-releases "^2.0.18" - update-browserslist-db "^1.1.1" - -buffer-from@^1.0.0: - version "1.1.2" - resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.2.tgz#2b146a6fd72e80b4f55d255f35ed59a3a9a41bd5" - integrity sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ== - -buffer@^5.5.0: - version "5.7.1" - resolved "https://registry.yarnpkg.com/buffer/-/buffer-5.7.1.tgz#ba62e7c13133053582197160851a8f648e99eed0" - integrity sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ== - dependencies: - base64-js "^1.3.1" - ieee754 "^1.1.13" - -bytes@3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.0.0.tgz#d32815404d689699f85a4ea4fa8755dd13a96048" - integrity sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw== - -bytes@3.1.2: - version "3.1.2" - resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.1.2.tgz#8b0beeb98605adf1b128fa4386403c009e0221a5" - integrity sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg== - -cacheable-request@^6.0.0: - version "6.1.0" - resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-6.1.0.tgz#20ffb8bd162ba4be11e9567d823db651052ca912" - integrity sha512-Oj3cAGPCqOZX7Rz64Uny2GYAZNliQSqfbePrgAQ1wKAihYmCUnraBtJtKcGR4xz7wF+LoJC+ssFZvv5BgF9Igg== - dependencies: - clone-response "^1.0.2" - get-stream "^5.1.0" - http-cache-semantics "^4.0.0" - keyv "^3.0.0" - lowercase-keys "^2.0.0" - normalize-url "^4.1.0" - responselike "^1.0.2" - -call-bind@^1.0.5, call-bind@^1.0.7: - version "1.0.7" - resolved "https://registry.yarnpkg.com/call-bind/-/call-bind-1.0.7.tgz#06016599c40c56498c18769d2730be242b6fa3b9" - integrity sha512-GHTSNSYICQ7scH7sZ+M2rFopRoLh8t2bLSW6BbgrtLsahOIB5iyAVJf9GjWK3cYTDaMj4XdBpM1cA6pIS0Kv2w== - dependencies: - es-define-property "^1.0.0" - es-errors "^1.3.0" - function-bind "^1.1.2" - get-intrinsic "^1.2.4" - set-function-length "^1.2.1" - -callsites@^3.0.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/callsites/-/callsites-3.1.0.tgz#b3630abd8943432f54b3f0519238e33cd7df2f73" - integrity sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ== - -camel-case@^4.1.2: - version "4.1.2" - resolved "https://registry.yarnpkg.com/camel-case/-/camel-case-4.1.2.tgz#9728072a954f805228225a6deea6b38461e1bd5a" - integrity sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw== - dependencies: - pascal-case "^3.1.2" - tslib "^2.0.3" - -camelcase-css@2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/camelcase-css/-/camelcase-css-2.0.1.tgz#ee978f6947914cc30c6b44741b6ed1df7f043fd5" - integrity sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA== - -camelcase@^6.2.0: - version "6.3.0" - resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-6.3.0.tgz#5685b95eb209ac9c0c177467778c9c84df58ba9a" - integrity sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA== - -caniuse-api@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/caniuse-api/-/caniuse-api-3.0.0.tgz#5e4d90e2274961d46291997df599e3ed008ee4c0" - integrity sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw== - dependencies: - browserslist "^4.0.0" - caniuse-lite "^1.0.0" - lodash.memoize "^4.1.2" - lodash.uniq "^4.5.0" - -caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001646, caniuse-lite@^1.0.30001669: - version "1.0.30001669" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001669.tgz#fda8f1d29a8bfdc42de0c170d7f34a9cf19ed7a3" - integrity sha512-DlWzFDJqstqtIVx1zeSpIMLjunf5SmwOw0N2Ck/QSQdS8PLS4+9HrLaYei4w8BIAL7IB/UEDu889d8vhCTPA0w== - -ccount@^1.0.0: - version "1.1.0" - resolved "https://registry.yarnpkg.com/ccount/-/ccount-1.1.0.tgz#246687debb6014735131be8abab2d93898f8d043" - integrity sha512-vlNK021QdI7PNeiUh/lKkC/mNHHfV0m/Ad5JoI0TYtlBnJAslM/JIkm/tGC88bkLIwO6OQ5uV6ztS6kVAtCDlg== - -chalk@^2.4.2: - version "2.4.2" - resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424" - integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ== - dependencies: - ansi-styles "^3.2.1" - escape-string-regexp "^1.0.5" - supports-color "^5.3.0" - -chalk@^4.0.0, chalk@^4.1.0, chalk@^4.1.2: - version "4.1.2" - resolved "https://registry.yarnpkg.com/chalk/-/chalk-4.1.2.tgz#aac4e2b7734a740867aeb16bf02aad556a1e7a01" - integrity sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA== - dependencies: - ansi-styles "^4.1.0" - supports-color "^7.1.0" - -character-entities-legacy@^1.0.0: - version "1.1.4" - resolved "https://registry.yarnpkg.com/character-entities-legacy/-/character-entities-legacy-1.1.4.tgz#94bc1845dce70a5bb9d2ecc748725661293d8fc1" - integrity sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA== - -character-entities@^1.0.0: - version "1.2.4" - resolved "https://registry.yarnpkg.com/character-entities/-/character-entities-1.2.4.tgz#e12c3939b7eaf4e5b15e7ad4c5e28e1d48c5b16b" - integrity sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw== - -character-reference-invalid@^1.0.0: - version "1.1.4" - resolved "https://registry.yarnpkg.com/character-reference-invalid/-/character-reference-invalid-1.1.4.tgz#083329cda0eae272ab3dbbf37e9a382c13af1560" - integrity sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg== - -cheerio-select@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/cheerio-select/-/cheerio-select-2.1.0.tgz#4d8673286b8126ca2a8e42740d5e3c4884ae21b4" - integrity sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g== - dependencies: - boolbase "^1.0.0" - css-select "^5.1.0" - css-what "^6.1.0" - domelementtype "^2.3.0" - domhandler "^5.0.3" - domutils "^3.0.1" - -cheerio@^1.0.0-rc.12, cheerio@^1.0.0-rc.9: - version "1.0.0" - resolved "https://registry.yarnpkg.com/cheerio/-/cheerio-1.0.0.tgz#1ede4895a82f26e8af71009f961a9b8cb60d6a81" - integrity sha512-quS9HgjQpdaXOvsZz82Oz7uxtXiy6UIsIQcpBj7HRw2M63Skasm9qlDocAM7jNuaxdhpPU7c4kJN+gA5MCu4ww== - dependencies: - cheerio-select "^2.1.0" - dom-serializer "^2.0.0" - domhandler "^5.0.3" - domutils "^3.1.0" - encoding-sniffer "^0.2.0" - htmlparser2 "^9.1.0" - parse5 "^7.1.2" - parse5-htmlparser2-tree-adapter "^7.0.0" - parse5-parser-stream "^7.1.2" - undici "^6.19.5" - whatwg-mimetype "^4.0.0" - -chokidar@^3.4.2, chokidar@^3.5.3: - version "3.6.0" - resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.6.0.tgz#197c6cc669ef2a8dc5e7b4d97ee4e092c3eb0d5b" - integrity sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw== - dependencies: - anymatch "~3.1.2" - braces "~3.0.2" - glob-parent "~5.1.2" - is-binary-path "~2.1.0" - is-glob "~4.0.1" - normalize-path "~3.0.0" - readdirp "~3.6.0" - optionalDependencies: - fsevents "~2.3.2" - -chownr@^1.1.1: - version "1.1.4" - resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.4.tgz#6fc9d7b42d32a583596337666e7d08084da2cc6b" - integrity sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg== - -chrome-trace-event@^1.0.2: - version "1.0.4" - resolved "https://registry.yarnpkg.com/chrome-trace-event/-/chrome-trace-event-1.0.4.tgz#05bffd7ff928465093314708c93bdfa9bd1f0f5b" - integrity sha512-rNjApaLzuwaOTjCiT8lSDdGN1APCiqkChLMJxJPWLunPAt5fy8xgU9/jNOchV84wfIxrA0lRQB7oCT8jrn/wrQ== - -ci-info@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-2.0.0.tgz#67a9e964be31a51e15e5010d58e6f12834002f46" - integrity sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ== - -ci-info@^3.2.0: - version "3.9.0" - resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-3.9.0.tgz#4279a62028a7b1f262f3473fc9605f5e218c59b4" - integrity sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ== - -clean-css@^5.2.2, clean-css@^5.3.0: - version "5.3.3" - resolved "https://registry.yarnpkg.com/clean-css/-/clean-css-5.3.3.tgz#b330653cd3bd6b75009cc25c714cae7b93351ccd" - integrity sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg== - dependencies: - source-map "~0.6.0" - -clean-stack@^2.0.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/clean-stack/-/clean-stack-2.2.0.tgz#ee8472dbb129e727b31e8a10a427dee9dfe4008b" - integrity sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A== - -cli-boxes@^2.2.1: - version "2.2.1" - resolved "https://registry.yarnpkg.com/cli-boxes/-/cli-boxes-2.2.1.tgz#ddd5035d25094fce220e9cab40a45840a440318f" - integrity sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw== - -cli-boxes@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/cli-boxes/-/cli-boxes-3.0.0.tgz#71a10c716feeba005e4504f36329ef0b17cf3145" - integrity sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g== - -cli-table3@^0.6.2: - version "0.6.5" - resolved "https://registry.yarnpkg.com/cli-table3/-/cli-table3-0.6.5.tgz#013b91351762739c16a9567c21a04632e449bf2f" - integrity sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ== - dependencies: - string-width "^4.2.0" - optionalDependencies: - "@colors/colors" "1.5.0" - -clone-deep@^4.0.1: - version "4.0.1" - resolved "https://registry.yarnpkg.com/clone-deep/-/clone-deep-4.0.1.tgz#c19fd9bdbbf85942b4fd979c84dcf7d5f07c2387" - integrity sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ== - dependencies: - is-plain-object "^2.0.4" - kind-of "^6.0.2" - shallow-clone "^3.0.0" - -clone-response@^1.0.2: - version "1.0.3" - resolved "https://registry.yarnpkg.com/clone-response/-/clone-response-1.0.3.tgz#af2032aa47816399cf5f0a1d0db902f517abb8c3" - integrity sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA== - dependencies: - mimic-response "^1.0.0" - -clsx@^1.1.1, clsx@^1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/clsx/-/clsx-1.2.1.tgz#0ddc4a20a549b59c93a4116bb26f5294ca17dc12" - integrity sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg== - -collapse-white-space@^1.0.2: - version "1.0.6" - resolved "https://registry.yarnpkg.com/collapse-white-space/-/collapse-white-space-1.0.6.tgz#e63629c0016665792060dbbeb79c42239d2c5287" - integrity sha512-jEovNnrhMuqyCcjfEJA56v0Xq8SkIoPKDyaHahwo3POf4qcSXqMYuwNcOTzp74vTsR9Tn08z4MxWqAhcekogkQ== - -color-convert@^1.9.0: - version "1.9.3" - resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8" - integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg== - dependencies: - color-name "1.1.3" - -color-convert@^2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-2.0.1.tgz#72d3a68d598c9bdb3af2ad1e84f21d896abd4de3" - integrity sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ== - dependencies: - color-name "~1.1.4" - -color-name@1.1.3: - version "1.1.3" - resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25" - integrity sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw== - -color-name@^1.0.0, color-name@~1.1.4: - version "1.1.4" - resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz#c2a09a87acbde69543de6f63fa3995c826c536a2" - integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA== - -color-string@^1.9.0: - version "1.9.1" - resolved "https://registry.yarnpkg.com/color-string/-/color-string-1.9.1.tgz#4467f9146f036f855b764dfb5bf8582bf342c7a4" - integrity sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg== - dependencies: - color-name "^1.0.0" - simple-swizzle "^0.2.2" - -color@^4.2.3: - version "4.2.3" - resolved "https://registry.yarnpkg.com/color/-/color-4.2.3.tgz#d781ecb5e57224ee43ea9627560107c0e0c6463a" - integrity sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A== - dependencies: - color-convert "^2.0.1" - color-string "^1.9.0" - -colord@^2.9.1: - version "2.9.3" - resolved "https://registry.yarnpkg.com/colord/-/colord-2.9.3.tgz#4f8ce919de456f1d5c1c368c307fe20f3e59fb43" - integrity sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw== - -colorette@^2.0.10: - version "2.0.20" - resolved "https://registry.yarnpkg.com/colorette/-/colorette-2.0.20.tgz#9eb793e6833067f7235902fcd3b09917a000a95a" - integrity sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w== - -combine-promises@^1.1.0: - version "1.2.0" - resolved "https://registry.yarnpkg.com/combine-promises/-/combine-promises-1.2.0.tgz#5f2e68451862acf85761ded4d9e2af7769c2ca6a" - integrity sha512-VcQB1ziGD0NXrhKxiwyNbCDmRzs/OShMs2GqW2DlU2A/Sd0nQxE1oWDAE5O0ygSx5mgQOn9eIFh7yKPgFRVkPQ== - -comma-separated-tokens@^1.0.0: - version "1.0.8" - resolved "https://registry.yarnpkg.com/comma-separated-tokens/-/comma-separated-tokens-1.0.8.tgz#632b80b6117867a158f1080ad498b2fbe7e3f5ea" - integrity sha512-GHuDRO12Sypu2cV70d1dkA2EUmXHgntrzbpvOB+Qy+49ypNfGgFQIC2fhhXbnyrJRynDCAARsT7Ou0M6hirpfw== - -commander@^2.20.0: - version "2.20.3" - resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.3.tgz#fd485e84c03eb4881c20722ba48035e8531aeb33" - integrity sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ== - -commander@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/commander/-/commander-5.1.0.tgz#46abbd1652f8e059bddaef99bbdcb2ad9cf179ae" - integrity sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg== - -commander@^7.2.0: - version "7.2.0" - resolved "https://registry.yarnpkg.com/commander/-/commander-7.2.0.tgz#a36cb57d0b501ce108e4d20559a150a391d97ab7" - integrity sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw== - -commander@^8.3.0: - version "8.3.0" - resolved "https://registry.yarnpkg.com/commander/-/commander-8.3.0.tgz#4837ea1b2da67b9c616a67afbb0fafee567bca66" - integrity sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww== - -commondir@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/commondir/-/commondir-1.0.1.tgz#ddd800da0c66127393cca5950ea968a3aaf1253b" - integrity sha512-W9pAhw0ja1Edb5GVdIF1mjZw/ASI0AlShXM83UUGe2DVr5TdAPEA1OA8m/g8zWp9x6On7gqufY+FatDbC3MDQg== - -compressible@~2.0.16: - version "2.0.18" - resolved "https://registry.yarnpkg.com/compressible/-/compressible-2.0.18.tgz#af53cca6b070d4c3c0750fbd77286a6d7cc46fba" - integrity sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg== - dependencies: - mime-db ">= 1.43.0 < 2" - -compression@^1.7.4: - version "1.7.4" - resolved "https://registry.yarnpkg.com/compression/-/compression-1.7.4.tgz#95523eff170ca57c29a0ca41e6fe131f41e5bb8f" - integrity sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ== - dependencies: - accepts "~1.3.5" - bytes "3.0.0" - compressible "~2.0.16" - debug "2.6.9" - on-headers "~1.0.2" - safe-buffer "5.1.2" - vary "~1.1.2" - -concat-map@0.0.1: - version "0.0.1" - resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b" - integrity sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg== - -configstore@^5.0.1: - version "5.0.1" - resolved "https://registry.yarnpkg.com/configstore/-/configstore-5.0.1.tgz#d365021b5df4b98cdd187d6a3b0e3f6a7cc5ed96" - integrity sha512-aMKprgk5YhBNyH25hj8wGt2+D52Sw1DRRIzqBwLp2Ya9mFmY8KPvvtvmna8SxVR9JMZ4kzMD68N22vlaRpkeFA== - dependencies: - dot-prop "^5.2.0" - graceful-fs "^4.1.2" - make-dir "^3.0.0" - unique-string "^2.0.0" - write-file-atomic "^3.0.0" - xdg-basedir "^4.0.0" - -connect-history-api-fallback@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/connect-history-api-fallback/-/connect-history-api-fallback-2.0.0.tgz#647264845251a0daf25b97ce87834cace0f5f1c8" - integrity sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA== - -consola@^2.15.3: - version "2.15.3" - resolved "https://registry.yarnpkg.com/consola/-/consola-2.15.3.tgz#2e11f98d6a4be71ff72e0bdf07bd23e12cb61550" - integrity sha512-9vAdYbHj6x2fLKC4+oPH0kFzY/orMZyG2Aj+kNylHxKGJ/Ed4dpNyAQYwJOdqO4zdM7XpVHmyejQDcQHrnuXbw== - -"consolidated-events@^1.1.0 || ^2.0.0": - version "2.0.2" - resolved "https://registry.yarnpkg.com/consolidated-events/-/consolidated-events-2.0.2.tgz#da8d8f8c2b232831413d9e190dc11669c79f4a91" - integrity sha512-2/uRVMdRypf5z/TW/ncD/66l75P5hH2vM/GR8Jf8HLc2xnfJtmina6F6du8+v4Z2vTrMo7jC+W1tmEEuuELgkQ== - -content-disposition@0.5.2: - version "0.5.2" - resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.2.tgz#0cf68bb9ddf5f2be7961c3a85178cb85dba78cb4" - integrity sha512-kRGRZw3bLlFISDBgwTSA1TMBFN6J6GWDeubmDE3AF+3+yXL8hTWv8r5rkLbqYXY4RjPk/EzHnClI3zQf1cFmHA== - -content-disposition@0.5.4: - version "0.5.4" - resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.4.tgz#8b82b4efac82512a02bb0b1dcec9d2c5e8eb5bfe" - integrity sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ== - dependencies: - safe-buffer "5.2.1" - -content-type@~1.0.4, content-type@~1.0.5: - version "1.0.5" - resolved "https://registry.yarnpkg.com/content-type/-/content-type-1.0.5.tgz#8b773162656d1d1086784c8f23a54ce6d73d7918" - integrity sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA== - -convert-source-map@^1.7.0: - version "1.9.0" - resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.9.0.tgz#7faae62353fb4213366d0ca98358d22e8368b05f" - integrity sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A== - -convert-source-map@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-2.0.0.tgz#4b560f649fc4e918dd0ab75cf4961e8bc882d82a" - integrity sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg== - -cookie-signature@1.0.6: - version "1.0.6" - resolved "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz#e303a882b342cc3ee8ca513a79999734dab3ae2c" - integrity sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ== - -cookie@0.7.1: - version "0.7.1" - resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.7.1.tgz#2f73c42142d5d5cf71310a74fc4ae61670e5dbc9" - integrity sha512-6DnInpx7SJ2AK3+CTUE/ZM0vWTUboZCegxhC2xiIydHR9jNuTAASBrfEpHhiGOZw/nX51bHt6YQl8jsGo4y/0w== - -copy-text-to-clipboard@^3.0.1: - version "3.2.0" - resolved "https://registry.yarnpkg.com/copy-text-to-clipboard/-/copy-text-to-clipboard-3.2.0.tgz#0202b2d9bdae30a49a53f898626dcc3b49ad960b" - integrity sha512-RnJFp1XR/LOBDckxTib5Qjr/PMfkatD0MUCQgdpqS8MdKiNUzBjAQBEN6oUy+jW7LI93BBG3DtMB2KOOKpGs2Q== - -copy-webpack-plugin@^11.0.0: - version "11.0.0" - resolved "https://registry.yarnpkg.com/copy-webpack-plugin/-/copy-webpack-plugin-11.0.0.tgz#96d4dbdb5f73d02dd72d0528d1958721ab72e04a" - integrity sha512-fX2MWpamkW0hZxMEg0+mYnA40LTosOSa5TqZ9GYIBzyJa9C3QUaMPSE2xAi/buNr8u89SfD9wHSQVBzrRa/SOQ== - dependencies: - fast-glob "^3.2.11" - glob-parent "^6.0.1" - globby "^13.1.1" - normalize-path "^3.0.0" - schema-utils "^4.0.0" - serialize-javascript "^6.0.0" - -core-js-compat@^3.38.0, core-js-compat@^3.38.1: - version "3.38.1" - resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.38.1.tgz#2bc7a298746ca5a7bcb9c164bcb120f2ebc09a09" - integrity sha512-JRH6gfXxGmrzF3tZ57lFx97YARxCXPaMzPo6jELZhv88pBH5VXpQ+y0znKGlFnzuaihqhLbefxSJxWJMPtfDzw== - dependencies: - browserslist "^4.23.3" - -core-js-pure@^3.30.2: - version "3.38.1" - resolved "https://registry.yarnpkg.com/core-js-pure/-/core-js-pure-3.38.1.tgz#e8534062a54b7221344884ba9b52474be495ada3" - integrity sha512-BY8Etc1FZqdw1glX0XNOq2FDwfrg/VGqoZOZCdaL+UmdaqDwQwYXkMJT4t6In+zfEfOJDcM9T0KdbBeJg8KKCQ== - -core-js@^3.23.3: - version "3.38.1" - resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.38.1.tgz#aa375b79a286a670388a1a363363d53677c0383e" - integrity sha512-OP35aUorbU3Zvlx7pjsFdu1rGNnD4pgw/CWoYzRY3t2EzoVT7shKHY1dlAy3f41cGIO7ZDPQimhGFTlEYkG/Hw== - -core-util-is@~1.0.0: - version "1.0.3" - resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.3.tgz#a6042d3634c2b27e9328f837b965fac83808db85" - integrity sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ== - -cosmiconfig@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-6.0.0.tgz#da4fee853c52f6b1e6935f41c1a2fc50bd4a9982" - integrity sha512-xb3ZL6+L8b9JLLCx3ZdoZy4+2ECphCMo2PwqgP1tlfVq6M6YReyzBJtvWWtbDSpNr9hn96pkCiZqUcFEc+54Qg== - dependencies: - "@types/parse-json" "^4.0.0" - import-fresh "^3.1.0" - parse-json "^5.0.0" - path-type "^4.0.0" - yaml "^1.7.2" - -cosmiconfig@^7.0.1: - version "7.1.0" - resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-7.1.0.tgz#1443b9afa596b670082ea46cbd8f6a62b84635f6" - integrity sha512-AdmX6xUzdNASswsFtmwSt7Vj8po9IuqXm0UXz7QKPuEUmPB4XyjGfaAr2PSuELMwkRMVH1EpIkX5bTZGRB3eCA== - dependencies: - "@types/parse-json" "^4.0.0" - import-fresh "^3.2.1" - parse-json "^5.0.0" - path-type "^4.0.0" - yaml "^1.10.0" - -cosmiconfig@^8.1.3, cosmiconfig@^8.3.5: - version "8.3.6" - resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-8.3.6.tgz#060a2b871d66dba6c8538ea1118ba1ac16f5fae3" - integrity sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA== - dependencies: - import-fresh "^3.3.0" - js-yaml "^4.1.0" - parse-json "^5.2.0" - path-type "^4.0.0" - -cross-fetch@^3.1.5: - version "3.1.8" - resolved "https://registry.yarnpkg.com/cross-fetch/-/cross-fetch-3.1.8.tgz#0327eba65fd68a7d119f8fb2bf9334a1a7956f82" - integrity sha512-cvA+JwZoU0Xq+h6WkMvAUqPEYy92Obet6UdKLfW60qn99ftItKjB5T+BkyWOFWe2pUyfQ+IJHmpOTznqk1M6Kg== - dependencies: - node-fetch "^2.6.12" - -cross-spawn@^7.0.3: - version "7.0.3" - resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-7.0.3.tgz#f73a85b9d5d41d045551c177e2882d4ac85728a6" - integrity sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w== - dependencies: - path-key "^3.1.0" - shebang-command "^2.0.0" - which "^2.0.1" - -crypto-random-string@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/crypto-random-string/-/crypto-random-string-2.0.0.tgz#ef2a7a966ec11083388369baa02ebead229b30d5" - integrity sha512-v1plID3y9r/lPhviJ1wrXpLeyUIGAZ2SHNYTEapm7/8A9nLPoyvVp3RK/EPFqn5kEznyWgYZNsRtYYIWbuG8KA== - -css-declaration-sorter@^6.3.1: - version "6.4.1" - resolved "https://registry.yarnpkg.com/css-declaration-sorter/-/css-declaration-sorter-6.4.1.tgz#28beac7c20bad7f1775be3a7129d7eae409a3a71" - integrity sha512-rtdthzxKuyq6IzqX6jEcIzQF/YqccluefyCYheovBOLhFT/drQA9zj/UbRAa9J7C0o6EG6u3E6g+vKkay7/k3g== - -css-loader@^6.7.1: - version "6.11.0" - resolved "https://registry.yarnpkg.com/css-loader/-/css-loader-6.11.0.tgz#33bae3bf6363d0a7c2cf9031c96c744ff54d85ba" - integrity sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g== - dependencies: - icss-utils "^5.1.0" - postcss "^8.4.33" - postcss-modules-extract-imports "^3.1.0" - postcss-modules-local-by-default "^4.0.5" - postcss-modules-scope "^3.2.0" - postcss-modules-values "^4.0.0" - postcss-value-parser "^4.2.0" - semver "^7.5.4" - -css-minimizer-webpack-plugin@^4.0.0: - version "4.2.2" - resolved "https://registry.yarnpkg.com/css-minimizer-webpack-plugin/-/css-minimizer-webpack-plugin-4.2.2.tgz#79f6199eb5adf1ff7ba57f105e3752d15211eb35" - integrity sha512-s3Of/4jKfw1Hj9CxEO1E5oXhQAxlayuHO2y/ML+C6I9sQ7FdzfEV6QgMLN3vI+qFsjJGIAFLKtQK7t8BOXAIyA== - dependencies: - cssnano "^5.1.8" - jest-worker "^29.1.2" - postcss "^8.4.17" - schema-utils "^4.0.0" - serialize-javascript "^6.0.0" - source-map "^0.6.1" - -css-select@^4.1.3: - version "4.3.0" - resolved "https://registry.yarnpkg.com/css-select/-/css-select-4.3.0.tgz#db7129b2846662fd8628cfc496abb2b59e41529b" - integrity sha512-wPpOYtnsVontu2mODhA19JrqWxNsfdatRKd64kmpRbQgh1KtItko5sTnEpPdpSaJszTOhEMlF/RPz28qj4HqhQ== - dependencies: - boolbase "^1.0.0" - css-what "^6.0.1" - domhandler "^4.3.1" - domutils "^2.8.0" - nth-check "^2.0.1" - -css-select@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/css-select/-/css-select-5.1.0.tgz#b8ebd6554c3637ccc76688804ad3f6a6fdaea8a6" - integrity sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg== - dependencies: - boolbase "^1.0.0" - css-what "^6.1.0" - domhandler "^5.0.2" - domutils "^3.0.1" - nth-check "^2.0.1" - -css-tree@^1.1.2, css-tree@^1.1.3: - version "1.1.3" - resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-1.1.3.tgz#eb4870fb6fd7707327ec95c2ff2ab09b5e8db91d" - integrity sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q== - dependencies: - mdn-data "2.0.14" - source-map "^0.6.1" - -css-tree@^2.3.1: - version "2.3.1" - resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-2.3.1.tgz#10264ce1e5442e8572fc82fbe490644ff54b5c20" - integrity sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw== - dependencies: - mdn-data "2.0.30" - source-map-js "^1.0.1" - -css-tree@~2.2.0: - version "2.2.1" - resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-2.2.1.tgz#36115d382d60afd271e377f9c5f67d02bd48c032" - integrity sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA== - dependencies: - mdn-data "2.0.28" - source-map-js "^1.0.1" - -css-what@^6.0.1, css-what@^6.1.0: - version "6.1.0" - resolved "https://registry.yarnpkg.com/css-what/-/css-what-6.1.0.tgz#fb5effcf76f1ddea2c81bdfaa4de44e79bac70f4" - integrity sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw== - -cssesc@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/cssesc/-/cssesc-3.0.0.tgz#37741919903b868565e1c09ea747445cd18983ee" - integrity sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg== - -cssnano-preset-advanced@^5.3.8: - version "5.3.10" - resolved "https://registry.yarnpkg.com/cssnano-preset-advanced/-/cssnano-preset-advanced-5.3.10.tgz#25558a1fbf3a871fb6429ce71e41be7f5aca6eef" - integrity sha512-fnYJyCS9jgMU+cmHO1rPSPf9axbQyD7iUhLO5Df6O4G+fKIOMps+ZbU0PdGFejFBBZ3Pftf18fn1eG7MAPUSWQ== - dependencies: - autoprefixer "^10.4.12" - cssnano-preset-default "^5.2.14" - postcss-discard-unused "^5.1.0" - postcss-merge-idents "^5.1.1" - postcss-reduce-idents "^5.2.0" - postcss-zindex "^5.1.0" - -cssnano-preset-default@^5.2.14: - version "5.2.14" - resolved "https://registry.yarnpkg.com/cssnano-preset-default/-/cssnano-preset-default-5.2.14.tgz#309def4f7b7e16d71ab2438052093330d9ab45d8" - integrity sha512-t0SFesj/ZV2OTylqQVOrFgEh5uanxbO6ZAdeCrNsUQ6fVuXwYTxJPNAGvGTxHbD68ldIJNec7PyYZDBrfDQ+6A== - dependencies: - css-declaration-sorter "^6.3.1" - cssnano-utils "^3.1.0" - postcss-calc "^8.2.3" - postcss-colormin "^5.3.1" - postcss-convert-values "^5.1.3" - postcss-discard-comments "^5.1.2" - postcss-discard-duplicates "^5.1.0" - postcss-discard-empty "^5.1.1" - postcss-discard-overridden "^5.1.0" - postcss-merge-longhand "^5.1.7" - postcss-merge-rules "^5.1.4" - postcss-minify-font-values "^5.1.0" - postcss-minify-gradients "^5.1.1" - postcss-minify-params "^5.1.4" - postcss-minify-selectors "^5.2.1" - postcss-normalize-charset "^5.1.0" - postcss-normalize-display-values "^5.1.0" - postcss-normalize-positions "^5.1.1" - postcss-normalize-repeat-style "^5.1.1" - postcss-normalize-string "^5.1.0" - postcss-normalize-timing-functions "^5.1.0" - postcss-normalize-unicode "^5.1.1" - postcss-normalize-url "^5.1.0" - postcss-normalize-whitespace "^5.1.1" - postcss-ordered-values "^5.1.3" - postcss-reduce-initial "^5.1.2" - postcss-reduce-transforms "^5.1.0" - postcss-svgo "^5.1.0" - postcss-unique-selectors "^5.1.1" - -cssnano-utils@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/cssnano-utils/-/cssnano-utils-3.1.0.tgz#95684d08c91511edfc70d2636338ca37ef3a6861" - integrity sha512-JQNR19/YZhz4psLX/rQ9M83e3z2Wf/HdJbryzte4a3NSuafyp9w/I4U+hx5C2S9g41qlstH7DEWnZaaj83OuEA== - -cssnano@^5.1.12, cssnano@^5.1.8: - version "5.1.15" - resolved "https://registry.yarnpkg.com/cssnano/-/cssnano-5.1.15.tgz#ded66b5480d5127fcb44dac12ea5a983755136bf" - integrity sha512-j+BKgDcLDQA+eDifLx0EO4XSA56b7uut3BQFH+wbSaSTuGLuiyTa/wbRYthUXX8LC9mLg+WWKe8h+qJuwTAbHw== - dependencies: - cssnano-preset-default "^5.2.14" - lilconfig "^2.0.3" - yaml "^1.10.2" - -csso@^4.2.0: - version "4.2.0" - resolved "https://registry.yarnpkg.com/csso/-/csso-4.2.0.tgz#ea3a561346e8dc9f546d6febedd50187cf389529" - integrity sha512-wvlcdIbf6pwKEk7vHj8/Bkc0B4ylXZruLvOgs9doS5eOsOpuodOV2zJChSpkp+pRpYQLQMeF04nr3Z68Sta9jA== - dependencies: - css-tree "^1.1.2" - -csso@^5.0.5: - version "5.0.5" - resolved "https://registry.yarnpkg.com/csso/-/csso-5.0.5.tgz#f9b7fe6cc6ac0b7d90781bb16d5e9874303e2ca6" - integrity sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ== - dependencies: - css-tree "~2.2.0" - -csstype@^3.0.2: - version "3.1.3" - resolved "https://registry.yarnpkg.com/csstype/-/csstype-3.1.3.tgz#d80ff294d114fb0e6ac500fbf85b60137d7eff81" - integrity sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw== - -debounce@^1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/debounce/-/debounce-1.2.1.tgz#38881d8f4166a5c5848020c11827b834bcb3e0a5" - integrity sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug== - -debug@2.6.9, debug@^2.6.0: - version "2.6.9" - resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f" - integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA== - dependencies: - ms "2.0.0" - -debug@4, debug@^4.1.0, debug@^4.1.1, debug@^4.3.1: - version "4.3.7" - resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.7.tgz#87945b4151a011d76d95a198d7111c865c360a52" - integrity sha512-Er2nc/H7RrMXZBFCEim6TCmMk02Z8vLC2Rbi1KEBggpo0fS6l0S1nnapwmIi3yW/+GOJap1Krg4w0Hg80oCqgQ== - dependencies: - ms "^2.1.3" - -decompress-response@^3.3.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-3.3.0.tgz#80a4dd323748384bfa248083622aedec982adff3" - integrity sha512-BzRPQuY1ip+qDonAOz42gRm/pg9F768C+npV/4JOsxRC2sq+Rlk+Q4ZCAsOhnIaMrgarILY+RMUIvMmmX1qAEA== - dependencies: - mimic-response "^1.0.0" - -decompress-response@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-6.0.0.tgz#ca387612ddb7e104bd16d85aab00d5ecf09c66fc" - integrity sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ== - dependencies: - mimic-response "^3.1.0" - -deep-extend@^0.6.0: - version "0.6.0" - resolved "https://registry.yarnpkg.com/deep-extend/-/deep-extend-0.6.0.tgz#c4fa7c95404a17a9c3e8ca7e1537312b736330ac" - integrity sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA== - -deepmerge@^4.2.2, deepmerge@^4.3.1: - version "4.3.1" - resolved "https://registry.yarnpkg.com/deepmerge/-/deepmerge-4.3.1.tgz#44b5f2147cd3b00d4b56137685966f26fd25dd4a" - integrity sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A== - -default-gateway@^6.0.3: - version "6.0.3" - resolved "https://registry.yarnpkg.com/default-gateway/-/default-gateway-6.0.3.tgz#819494c888053bdb743edbf343d6cdf7f2943a71" - integrity sha512-fwSOJsbbNzZ/CUFpqFBqYfYNLj1NbMPm8MMCIzHjC83iSJRBEGmDUxU+WP661BaBQImeC2yHwXtz+P/O9o+XEg== - dependencies: - execa "^5.0.0" - -defer-to-connect@^1.0.1: - version "1.1.3" - resolved "https://registry.yarnpkg.com/defer-to-connect/-/defer-to-connect-1.1.3.tgz#331ae050c08dcf789f8c83a7b81f0ed94f4ac591" - integrity sha512-0ISdNousHvZT2EiFlZeZAHBUvSxmKswVCEf8hW7KWgG4a8MVEu/3Vb6uWYozkjylyCxe0JBIiRB1jV45S70WVQ== - -define-data-property@^1.0.1, define-data-property@^1.1.4: - version "1.1.4" - resolved "https://registry.yarnpkg.com/define-data-property/-/define-data-property-1.1.4.tgz#894dc141bb7d3060ae4366f6a0107e68fbe48c5e" - integrity sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A== - dependencies: - es-define-property "^1.0.0" - es-errors "^1.3.0" - gopd "^1.0.1" - -define-lazy-prop@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/define-lazy-prop/-/define-lazy-prop-2.0.0.tgz#3f7ae421129bcaaac9bc74905c98a0009ec9ee7f" - integrity sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og== - -define-properties@^1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/define-properties/-/define-properties-1.2.1.tgz#10781cc616eb951a80a034bafcaa7377f6af2b6c" - integrity sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg== - dependencies: - define-data-property "^1.0.1" - has-property-descriptors "^1.0.0" - object-keys "^1.1.1" - -del@^6.1.1: - version "6.1.1" - resolved "https://registry.yarnpkg.com/del/-/del-6.1.1.tgz#3b70314f1ec0aa325c6b14eb36b95786671edb7a" - integrity sha512-ua8BhapfP0JUJKC/zV9yHHDW/rDoDxP4Zhn3AkA6/xT6gY7jYXJiaeyBZznYVujhZZET+UgcbZiQ7sN3WqcImg== - dependencies: - globby "^11.0.1" - graceful-fs "^4.2.4" - is-glob "^4.0.1" - is-path-cwd "^2.2.0" - is-path-inside "^3.0.2" - p-map "^4.0.0" - rimraf "^3.0.2" - slash "^3.0.0" - -depd@2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/depd/-/depd-2.0.0.tgz#b696163cc757560d09cf22cc8fad1571b79e76df" - integrity sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw== - -depd@~1.1.2: - version "1.1.2" - resolved "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz#9bcd52e14c097763e749b274c4346ed2e560b5a9" - integrity sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ== - -destroy@1.2.0: - version "1.2.0" - resolved "https://registry.yarnpkg.com/destroy/-/destroy-1.2.0.tgz#4803735509ad8be552934c67df614f94e66fa015" - integrity sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg== - -detab@2.0.4: - version "2.0.4" - resolved "https://registry.yarnpkg.com/detab/-/detab-2.0.4.tgz#b927892069aff405fbb9a186fe97a44a92a94b43" - integrity sha512-8zdsQA5bIkoRECvCrNKPla84lyoR7DSAyf7p0YgXzBO9PDJx8KntPUay7NS6yp+KdxdVtiE5SpHKtbp2ZQyA9g== - dependencies: - repeat-string "^1.5.4" - -detect-libc@^2.0.0, detect-libc@^2.0.1: - version "2.0.3" - resolved "https://registry.yarnpkg.com/detect-libc/-/detect-libc-2.0.3.tgz#f0cd503b40f9939b894697d19ad50895e30cf700" - integrity sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw== - -detect-node@^2.0.4: - version "2.1.0" - resolved "https://registry.yarnpkg.com/detect-node/-/detect-node-2.1.0.tgz#c9c70775a49c3d03bc2c06d9a73be550f978f8b1" - integrity sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g== - -detect-port-alt@^1.1.6: - version "1.1.6" - resolved "https://registry.yarnpkg.com/detect-port-alt/-/detect-port-alt-1.1.6.tgz#24707deabe932d4a3cf621302027c2b266568275" - integrity sha512-5tQykt+LqfJFBEYaDITx7S7cR7mJ/zQmLXZ2qt5w04ainYZw6tBf9dBunMjVeVOdYVRUzUOE4HkY5J7+uttb5Q== - dependencies: - address "^1.0.1" - debug "^2.6.0" - -detect-port@^1.3.0: - version "1.6.1" - resolved "https://registry.yarnpkg.com/detect-port/-/detect-port-1.6.1.tgz#45e4073997c5f292b957cb678fb0bb8ed4250a67" - integrity sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q== - dependencies: - address "^1.0.1" - debug "4" - -dir-glob@^3.0.1: - version "3.0.1" - resolved "https://registry.yarnpkg.com/dir-glob/-/dir-glob-3.0.1.tgz#56dbf73d992a4a93ba1584f4534063fd2e41717f" - integrity sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA== - dependencies: - path-type "^4.0.0" - -dns-packet@^5.2.2: - version "5.6.1" - resolved "https://registry.yarnpkg.com/dns-packet/-/dns-packet-5.6.1.tgz#ae888ad425a9d1478a0674256ab866de1012cf2f" - integrity sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw== - dependencies: - "@leichtgewicht/ip-codec" "^2.0.1" - -dom-converter@^0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/dom-converter/-/dom-converter-0.2.0.tgz#6721a9daee2e293682955b6afe416771627bb768" - integrity sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA== - dependencies: - utila "~0.4" - -dom-serializer@^1.0.1: - version "1.4.1" - resolved "https://registry.yarnpkg.com/dom-serializer/-/dom-serializer-1.4.1.tgz#de5d41b1aea290215dc45a6dae8adcf1d32e2d30" - integrity sha512-VHwB3KfrcOOkelEG2ZOfxqLZdfkil8PtJi4P8N2MMXucZq2yLp75ClViUlOVwyoHEDjYU433Aq+5zWP61+RGag== - dependencies: - domelementtype "^2.0.1" - domhandler "^4.2.0" - entities "^2.0.0" - -dom-serializer@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/dom-serializer/-/dom-serializer-2.0.0.tgz#e41b802e1eedf9f6cae183ce5e622d789d7d8e53" - integrity sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg== - dependencies: - domelementtype "^2.3.0" - domhandler "^5.0.2" - entities "^4.2.0" - -domelementtype@^2.0.1, domelementtype@^2.2.0, domelementtype@^2.3.0: - version "2.3.0" - resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-2.3.0.tgz#5c45e8e869952626331d7aab326d01daf65d589d" - integrity sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw== - -domhandler@^4.0.0, domhandler@^4.2.0, domhandler@^4.3.1: - version "4.3.1" - resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-4.3.1.tgz#8d792033416f59d68bc03a5aa7b018c1ca89279c" - integrity sha512-GrwoxYN+uWlzO8uhUXRl0P+kHE4GtVPfYzVLcUxPL7KNdHKj66vvlhiweIHqYYXWlw+T8iLMp42Lm67ghw4WMQ== - dependencies: - domelementtype "^2.2.0" - -domhandler@^5.0.2, domhandler@^5.0.3: - version "5.0.3" - resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-5.0.3.tgz#cc385f7f751f1d1fc650c21374804254538c7d31" - integrity sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w== - dependencies: - domelementtype "^2.3.0" - -domutils@^2.5.2, domutils@^2.8.0: - version "2.8.0" - resolved "https://registry.yarnpkg.com/domutils/-/domutils-2.8.0.tgz#4437def5db6e2d1f5d6ee859bd95ca7d02048135" - integrity sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A== - dependencies: - dom-serializer "^1.0.1" - domelementtype "^2.2.0" - domhandler "^4.2.0" - -domutils@^3.0.1, domutils@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/domutils/-/domutils-3.1.0.tgz#c47f551278d3dc4b0b1ab8cbb42d751a6f0d824e" - integrity sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA== - dependencies: - dom-serializer "^2.0.0" - domelementtype "^2.3.0" - domhandler "^5.0.3" - -dot-case@^3.0.4: - version "3.0.4" - resolved "https://registry.yarnpkg.com/dot-case/-/dot-case-3.0.4.tgz#9b2b670d00a431667a8a75ba29cd1b98809ce751" - integrity sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w== - dependencies: - no-case "^3.0.4" - tslib "^2.0.3" - -dot-prop@^5.2.0: - version "5.3.0" - resolved "https://registry.yarnpkg.com/dot-prop/-/dot-prop-5.3.0.tgz#90ccce708cd9cd82cc4dc8c3ddd9abdd55b20e88" - integrity sha512-QM8q3zDe58hqUqjraQOmzZ1LIH9SWQJTlEKCH4kJ2oQvLZk7RbQXvtDM2XEq3fwkV9CCvvH4LA0AV+ogFsBM2Q== - dependencies: - is-obj "^2.0.0" - -duplexer3@^0.1.4: - version "0.1.5" - resolved "https://registry.yarnpkg.com/duplexer3/-/duplexer3-0.1.5.tgz#0b5e4d7bad5de8901ea4440624c8e1d20099217e" - integrity sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA== - -duplexer@^0.1.2: - version "0.1.2" - resolved "https://registry.yarnpkg.com/duplexer/-/duplexer-0.1.2.tgz#3abe43aef3835f8ae077d136ddce0f276b0400e6" - integrity sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg== - -eastasianwidth@^0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/eastasianwidth/-/eastasianwidth-0.2.0.tgz#696ce2ec0aa0e6ea93a397ffcf24aa7840c827cb" - integrity sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA== - -ee-first@1.1.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d" - integrity sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow== - -electron-to-chromium@^1.5.41: - version "1.5.42" - resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.5.42.tgz#4b3ca7648fb0865daec92298f9ba79e278a476a3" - integrity sha512-gIfKavKDw1mhvic9nbzA5lZw8QSHpdMwLwXc0cWidQz9B15pDoDdDH4boIatuFfeoCatb3a/NGL6CYRVFxGZ9g== - -emoji-regex@^8.0.0: - version "8.0.0" - resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-8.0.0.tgz#e818fd69ce5ccfcb404594f842963bf53164cc37" - integrity sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A== - -emoji-regex@^9.2.2: - version "9.2.2" - resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-9.2.2.tgz#840c8803b0d8047f4ff0cf963176b32d4ef3ed72" - integrity sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg== - -emojis-list@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-3.0.0.tgz#5570662046ad29e2e916e71aae260abdff4f6a78" - integrity sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q== - -emoticon@^3.2.0: - version "3.2.0" - resolved "https://registry.yarnpkg.com/emoticon/-/emoticon-3.2.0.tgz#c008ca7d7620fac742fe1bf4af8ff8fed154ae7f" - integrity sha512-SNujglcLTTg+lDAcApPNgEdudaqQFiAbJCqzjNxJkvN9vAwCGi0uu8IUVvx+f16h+V44KCY6Y2yboroc9pilHg== - -encodeurl@~1.0.2: - version "1.0.2" - resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz#ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59" - integrity sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w== - -encodeurl@~2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-2.0.0.tgz#7b8ea898077d7e409d3ac45474ea38eaf0857a58" - integrity sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg== - -encoding-sniffer@^0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/encoding-sniffer/-/encoding-sniffer-0.2.0.tgz#799569d66d443babe82af18c9f403498365ef1d5" - integrity sha512-ju7Wq1kg04I3HtiYIOrUrdfdDvkyO9s5XM8QAj/bN61Yo/Vb4vgJxy5vi4Yxk01gWHbrofpPtpxM8bKger9jhg== - dependencies: - iconv-lite "^0.6.3" - whatwg-encoding "^3.1.1" - -end-of-stream@^1.1.0, end-of-stream@^1.4.1: - version "1.4.4" - resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.4.tgz#5ae64a5f45057baf3626ec14da0ca5e4b2431eb0" - integrity sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q== - dependencies: - once "^1.4.0" - -enhanced-resolve@^5.17.1: - version "5.17.1" - resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-5.17.1.tgz#67bfbbcc2f81d511be77d686a90267ef7f898a15" - integrity sha512-LMHl3dXhTcfv8gM4kEzIUeTQ+7fpdA0l2tUf34BddXPkz2A5xJ5L/Pchd5BL6rdccM9QGvu0sWZzK1Z1t4wwyg== - dependencies: - graceful-fs "^4.2.4" - tapable "^2.2.0" - -entities@^2.0.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/entities/-/entities-2.2.0.tgz#098dc90ebb83d8dffa089d55256b351d34c4da55" - integrity sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A== - -entities@^4.2.0, entities@^4.4.0, entities@^4.5.0: - version "4.5.0" - resolved "https://registry.yarnpkg.com/entities/-/entities-4.5.0.tgz#5d268ea5e7113ec74c4d033b79ea5a35a488fb48" - integrity sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw== - -error-ex@^1.3.1: - version "1.3.2" - resolved "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz#b4ac40648107fdcdcfae242f428bea8a14d4f1bf" - integrity sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g== - dependencies: - is-arrayish "^0.2.1" - -es-define-property@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/es-define-property/-/es-define-property-1.0.0.tgz#c7faefbdff8b2696cf5f46921edfb77cc4ba3845" - integrity sha512-jxayLKShrEqqzJ0eumQbVhTYQM27CfT1T35+gCgDFoL82JLsXqTJ76zv6A0YLOgEnLUMvLzsDsGIrl8NFpT2gQ== - dependencies: - get-intrinsic "^1.2.4" - -es-errors@^1.3.0: - version "1.3.0" - resolved "https://registry.yarnpkg.com/es-errors/-/es-errors-1.3.0.tgz#05f75a25dab98e4fb1dcd5e1472c0546d5057c8f" - integrity sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw== - -es-module-lexer@^1.2.1: - version "1.5.4" - resolved "https://registry.yarnpkg.com/es-module-lexer/-/es-module-lexer-1.5.4.tgz#a8efec3a3da991e60efa6b633a7cad6ab8d26b78" - integrity sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw== - -escalade@^3.2.0: - version "3.2.0" - resolved "https://registry.yarnpkg.com/escalade/-/escalade-3.2.0.tgz#011a3f69856ba189dffa7dc8fcce99d2a87903e5" - integrity sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA== - -escape-goat@^2.0.0: - version "2.1.1" - resolved "https://registry.yarnpkg.com/escape-goat/-/escape-goat-2.1.1.tgz#1b2dc77003676c457ec760b2dc68edb648188675" - integrity sha512-8/uIhbG12Csjy2JEW7D9pHbreaVaS/OpN3ycnyvElTdwM5n6GY6W6e2IPemfvGZeUMqZ9A/3GqIZMgKnBhAw/Q== - -escape-html@^1.0.3, escape-html@~1.0.3: - version "1.0.3" - resolved "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.3.tgz#0258eae4d3d0c0974de1c169188ef0051d1d1988" - integrity sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow== - -escape-string-regexp@^1.0.5: - version "1.0.5" - resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4" - integrity sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg== - -escape-string-regexp@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz#14ba83a5d373e3d311e5afca29cf5bfad965bf34" - integrity sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA== - -eslint-scope@5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-5.1.1.tgz#e786e59a66cb92b3f6c1fb0d508aab174848f48c" - integrity sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw== - dependencies: - esrecurse "^4.3.0" - estraverse "^4.1.1" - -esprima@^4.0.0: - version "4.0.1" - resolved "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz#13b04cdb3e6c5d19df91ab6987a8695619b0aa71" - integrity sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A== - -esrecurse@^4.3.0: - version "4.3.0" - resolved "https://registry.yarnpkg.com/esrecurse/-/esrecurse-4.3.0.tgz#7ad7964d679abb28bee72cec63758b1c5d2c9921" - integrity sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag== - dependencies: - estraverse "^5.2.0" - -estraverse@^4.1.1: - version "4.3.0" - resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-4.3.0.tgz#398ad3f3c5a24948be7725e83d11a7de28cdbd1d" - integrity sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw== - -estraverse@^5.2.0: - version "5.3.0" - resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-5.3.0.tgz#2eea5290702f26ab8fe5370370ff86c965d21123" - integrity sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA== - -esutils@^2.0.2: - version "2.0.3" - resolved "https://registry.yarnpkg.com/esutils/-/esutils-2.0.3.tgz#74d2eb4de0b8da1293711910d50775b9b710ef64" - integrity sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g== - -eta@^2.0.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/eta/-/eta-2.2.0.tgz#eb8b5f8c4e8b6306561a455e62cd7492fe3a9b8a" - integrity sha512-UVQ72Rqjy/ZKQalzV5dCCJP80GrmPrMxh6NlNf+erV6ObL0ZFkhCstWRawS85z3smdr3d2wXPsZEY7rDPfGd2g== - -etag@~1.8.1: - version "1.8.1" - resolved "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz#41ae2eeb65efa62268aebfea83ac7d79299b0887" - integrity sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg== - -eval@^0.1.8: - version "0.1.8" - resolved "https://registry.yarnpkg.com/eval/-/eval-0.1.8.tgz#2b903473b8cc1d1989b83a1e7923f883eb357f85" - integrity sha512-EzV94NYKoO09GLXGjXj9JIlXijVck4ONSr5wiCWDvhsvj5jxSrzTmRU/9C1DyB6uToszLs8aifA6NQ7lEQdvFw== - dependencies: - "@types/node" "*" - require-like ">= 0.1.1" - -eventemitter3@^4.0.0: - version "4.0.7" - resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-4.0.7.tgz#2de9b68f6528d5644ef5c59526a1b4a07306169f" - integrity sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw== - -events@^3.2.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/events/-/events-3.3.0.tgz#31a95ad0a924e2d2c419a813aeb2c4e878ea7400" - integrity sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q== - -execa@^5.0.0: - version "5.1.1" - resolved "https://registry.yarnpkg.com/execa/-/execa-5.1.1.tgz#f80ad9cbf4298f7bd1d4c9555c21e93741c411dd" - integrity sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg== - dependencies: - cross-spawn "^7.0.3" - get-stream "^6.0.0" - human-signals "^2.1.0" - is-stream "^2.0.0" - merge-stream "^2.0.0" - npm-run-path "^4.0.1" - onetime "^5.1.2" - signal-exit "^3.0.3" - strip-final-newline "^2.0.0" - -expand-template@^2.0.3: - version "2.0.3" - resolved "https://registry.yarnpkg.com/expand-template/-/expand-template-2.0.3.tgz#6e14b3fcee0f3a6340ecb57d2e8918692052a47c" - integrity sha512-XYfuKMvj4O35f/pOXLObndIRvyQ+/+6AhODh+OKWj9S9498pHHn/IMszH+gt0fBCRWMNfk1ZSp5x3AifmnI2vg== - -express@^4.17.3: - version "4.21.1" - resolved "https://registry.yarnpkg.com/express/-/express-4.21.1.tgz#9dae5dda832f16b4eec941a4e44aa89ec481b281" - integrity sha512-YSFlK1Ee0/GC8QaO91tHcDxJiE/X4FbpAyQWkxAvG6AXCuR65YzK8ua6D9hvi/TzUfZMpc+BwuM1IPw8fmQBiQ== - dependencies: - accepts "~1.3.8" - array-flatten "1.1.1" - body-parser "1.20.3" - content-disposition "0.5.4" - content-type "~1.0.4" - cookie "0.7.1" - cookie-signature "1.0.6" - debug "2.6.9" - depd "2.0.0" - encodeurl "~2.0.0" - escape-html "~1.0.3" - etag "~1.8.1" - finalhandler "1.3.1" - fresh "0.5.2" - http-errors "2.0.0" - merge-descriptors "1.0.3" - methods "~1.1.2" - on-finished "2.4.1" - parseurl "~1.3.3" - path-to-regexp "0.1.10" - proxy-addr "~2.0.7" - qs "6.13.0" - range-parser "~1.2.1" - safe-buffer "5.2.1" - send "0.19.0" - serve-static "1.16.2" - setprototypeof "1.2.0" - statuses "2.0.1" - type-is "~1.6.18" - utils-merge "1.0.1" - vary "~1.1.2" - -extend-shallow@^2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-2.0.1.tgz#51af7d614ad9a9f610ea1bafbb989d6b1c56890f" - integrity sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug== - dependencies: - is-extendable "^0.1.0" - -extend@^3.0.0: - version "3.0.2" - resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.2.tgz#f8b1136b4071fbd8eb140aff858b1019ec2915fa" - integrity sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g== - -fast-deep-equal@^3.1.1, fast-deep-equal@^3.1.3: - version "3.1.3" - resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz#3a7d56b559d6cbc3eb512325244e619a65c6c525" - integrity sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q== - -fast-glob@^3.2.11, fast-glob@^3.2.9, fast-glob@^3.3.0: - version "3.3.2" - resolved "https://registry.yarnpkg.com/fast-glob/-/fast-glob-3.3.2.tgz#a904501e57cfdd2ffcded45e99a54fef55e46129" - integrity sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow== - dependencies: - "@nodelib/fs.stat" "^2.0.2" - "@nodelib/fs.walk" "^1.2.3" - glob-parent "^5.1.2" - merge2 "^1.3.0" - micromatch "^4.0.4" - -fast-json-stable-stringify@^2.0.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz#874bf69c6f404c2b5d99c481341399fd55892633" - integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw== - -fast-uri@^3.0.1: - version "3.0.3" - resolved "https://registry.yarnpkg.com/fast-uri/-/fast-uri-3.0.3.tgz#892a1c91802d5d7860de728f18608a0573142241" - integrity sha512-aLrHthzCjH5He4Z2H9YZ+v6Ujb9ocRuW6ZzkJQOrTxleEijANq4v1TsaPaVG1PZcuurEzrLcWRyYBYXD5cEiaw== - -fastq@^1.6.0: - version "1.17.1" - resolved "https://registry.yarnpkg.com/fastq/-/fastq-1.17.1.tgz#2a523f07a4e7b1e81a42b91b8bf2254107753b47" - integrity sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w== - dependencies: - reusify "^1.0.4" - -faye-websocket@^0.11.3: - version "0.11.4" - resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.4.tgz#7f0d9275cfdd86a1c963dc8b65fcc451edcbb1da" - integrity sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g== - dependencies: - websocket-driver ">=0.5.1" - -fbemitter@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/fbemitter/-/fbemitter-3.0.0.tgz#00b2a1af5411254aab416cd75f9e6289bee4bff3" - integrity sha512-KWKaceCwKQU0+HPoop6gn4eOHk50bBv/VxjJtGMfwmJt3D29JpN4H4eisCtIPA+a8GVBam+ldMMpMjJUvpDyHw== - dependencies: - fbjs "^3.0.0" - -fbjs-css-vars@^1.0.0: - version "1.0.2" - resolved "https://registry.yarnpkg.com/fbjs-css-vars/-/fbjs-css-vars-1.0.2.tgz#216551136ae02fe255932c3ec8775f18e2c078b8" - integrity sha512-b2XGFAFdWZWg0phtAWLHCk836A1Xann+I+Dgd3Gk64MHKZO44FfoD1KxyvbSh0qZsIoXQGGlVztIY+oitJPpRQ== - -fbjs@^3.0.0, fbjs@^3.0.1: - version "3.0.5" - resolved "https://registry.yarnpkg.com/fbjs/-/fbjs-3.0.5.tgz#aa0edb7d5caa6340011790bd9249dbef8a81128d" - integrity sha512-ztsSx77JBtkuMrEypfhgc3cI0+0h+svqeie7xHbh1k/IKdcydnvadp/mUaGgjAOXQmQSxsqgaRhS3q9fy+1kxg== - dependencies: - cross-fetch "^3.1.5" - fbjs-css-vars "^1.0.0" - loose-envify "^1.0.0" - object-assign "^4.1.0" - promise "^7.1.1" - setimmediate "^1.0.5" - ua-parser-js "^1.0.35" - -feed@^4.2.2: - version "4.2.2" - resolved "https://registry.yarnpkg.com/feed/-/feed-4.2.2.tgz#865783ef6ed12579e2c44bbef3c9113bc4956a7e" - integrity sha512-u5/sxGfiMfZNtJ3OvQpXcvotFpYkL0n9u9mM2vkui2nGo8b4wvDkJ8gAkYqbA8QpGyFCv3RK0Z+Iv+9veCS9bQ== - dependencies: - xml-js "^1.6.11" - -file-loader@^6.2.0: - version "6.2.0" - resolved "https://registry.yarnpkg.com/file-loader/-/file-loader-6.2.0.tgz#baef7cf8e1840df325e4390b4484879480eebe4d" - integrity sha512-qo3glqyTa61Ytg4u73GultjHGjdRyig3tG6lPtyX/jOEJvHif9uB0/OCI2Kif6ctF3caQTW2G5gym21oAsI4pw== - dependencies: - loader-utils "^2.0.0" - schema-utils "^3.0.0" - -filesize@^8.0.6: - version "8.0.7" - resolved "https://registry.yarnpkg.com/filesize/-/filesize-8.0.7.tgz#695e70d80f4e47012c132d57a059e80c6b580bd8" - integrity sha512-pjmC+bkIF8XI7fWaH8KxHcZL3DPybs1roSKP4rKDvy20tAWwIObE4+JIseG2byfGKhud5ZnM4YSGKBz7Sh0ndQ== - -fill-range@^7.1.1: - version "7.1.1" - resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-7.1.1.tgz#44265d3cac07e3ea7dc247516380643754a05292" - integrity sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg== - dependencies: - to-regex-range "^5.0.1" - -finalhandler@1.3.1: - version "1.3.1" - resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.3.1.tgz#0c575f1d1d324ddd1da35ad7ece3df7d19088019" - integrity sha512-6BN9trH7bp3qvnrRyzsBz+g3lZxTNZTbVO2EV1CS0WIcDbawYVdYvGflME/9QP0h0pYlCDBCTjYa9nZzMDpyxQ== - dependencies: - debug "2.6.9" - encodeurl "~2.0.0" - escape-html "~1.0.3" - on-finished "2.4.1" - parseurl "~1.3.3" - statuses "2.0.1" - unpipe "~1.0.0" - -find-cache-dir@^3.3.1: - version "3.3.2" - resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-3.3.2.tgz#b30c5b6eff0730731aea9bbd9dbecbd80256d64b" - integrity sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig== - dependencies: - commondir "^1.0.1" - make-dir "^3.0.2" - pkg-dir "^4.1.0" - -find-up@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73" - integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg== - dependencies: - locate-path "^3.0.0" - -find-up@^4.0.0: - version "4.1.0" - resolved "https://registry.yarnpkg.com/find-up/-/find-up-4.1.0.tgz#97afe7d6cdc0bc5928584b7c8d7b16e8a9aa5d19" - integrity sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw== - dependencies: - locate-path "^5.0.0" - path-exists "^4.0.0" - -find-up@^5.0.0: - version "5.0.0" - resolved "https://registry.yarnpkg.com/find-up/-/find-up-5.0.0.tgz#4c92819ecb7083561e4f4a240a86be5198f536fc" - integrity sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng== - dependencies: - locate-path "^6.0.0" - path-exists "^4.0.0" - -flat@^5.0.2: - version "5.0.2" - resolved "https://registry.yarnpkg.com/flat/-/flat-5.0.2.tgz#8ca6fe332069ffa9d324c327198c598259ceb241" - integrity sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ== - -flux@^4.0.1: - version "4.0.4" - resolved "https://registry.yarnpkg.com/flux/-/flux-4.0.4.tgz#9661182ea81d161ee1a6a6af10d20485ef2ac572" - integrity sha512-NCj3XlayA2UsapRpM7va6wU1+9rE5FIL7qoMcmxWHRzbp0yujihMBm9BBHZ1MDIk5h5o2Bl6eGiCe8rYELAmYw== - dependencies: - fbemitter "^3.0.0" - fbjs "^3.0.1" - -follow-redirects@^1.0.0, follow-redirects@^1.14.7: - version "1.15.9" - resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.15.9.tgz#a604fa10e443bf98ca94228d9eebcc2e8a2c8ee1" - integrity sha512-gew4GsXizNgdoRyqmyfMHyAmXsZDk6mHkSxZFCzW9gwlbtOW44CDtYavM+y+72qD/Vq2l550kMF52DT8fOLJqQ== - -fork-ts-checker-webpack-plugin@^6.5.0: - version "6.5.3" - resolved "https://registry.yarnpkg.com/fork-ts-checker-webpack-plugin/-/fork-ts-checker-webpack-plugin-6.5.3.tgz#eda2eff6e22476a2688d10661688c47f611b37f3" - integrity sha512-SbH/l9ikmMWycd5puHJKTkZJKddF4iRLyW3DeZ08HTI7NGyLS38MXd/KGgeWumQO7YNQbW2u/NtPT2YowbPaGQ== - dependencies: - "@babel/code-frame" "^7.8.3" - "@types/json-schema" "^7.0.5" - chalk "^4.1.0" - chokidar "^3.4.2" - cosmiconfig "^6.0.0" - deepmerge "^4.2.2" - fs-extra "^9.0.0" - glob "^7.1.6" - memfs "^3.1.2" - minimatch "^3.0.4" - schema-utils "2.7.0" - semver "^7.3.2" - tapable "^1.0.0" - -forwarded@0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.2.0.tgz#2269936428aad4c15c7ebe9779a84bf0b2a81811" - integrity sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow== - -fraction.js@^4.3.7: - version "4.3.7" - resolved "https://registry.yarnpkg.com/fraction.js/-/fraction.js-4.3.7.tgz#06ca0085157e42fda7f9e726e79fefc4068840f7" - integrity sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew== - -fresh@0.5.2: - version "0.5.2" - resolved "https://registry.yarnpkg.com/fresh/-/fresh-0.5.2.tgz#3d8cadd90d976569fa835ab1f8e4b23a105605a7" - integrity sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q== - -fs-constants@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/fs-constants/-/fs-constants-1.0.0.tgz#6be0de9be998ce16af8afc24497b9ee9b7ccd9ad" - integrity sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow== - -fs-extra@^10.1.0: - version "10.1.0" - resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-10.1.0.tgz#02873cfbc4084dde127eaa5f9905eef2325d1abf" - integrity sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ== - dependencies: - graceful-fs "^4.2.0" - jsonfile "^6.0.1" - universalify "^2.0.0" - -fs-extra@^9.0.0: - version "9.1.0" - resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-9.1.0.tgz#5954460c764a8da2094ba3554bf839e6b9a7c86d" - integrity sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ== - dependencies: - at-least-node "^1.0.0" - graceful-fs "^4.2.0" - jsonfile "^6.0.1" - universalify "^2.0.0" - -fs-monkey@^1.0.4: - version "1.0.6" - resolved "https://registry.yarnpkg.com/fs-monkey/-/fs-monkey-1.0.6.tgz#8ead082953e88d992cf3ff844faa907b26756da2" - integrity sha512-b1FMfwetIKymC0eioW7mTywihSQE4oLzQn1dB6rZB5fx/3NpNEdAWeCSMB+60/AeT0TCXsxzAlcYVEFCTAksWg== - -fs.realpath@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f" - integrity sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw== - -fsevents@~2.3.2: - version "2.3.3" - resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.3.3.tgz#cac6407785d03675a2a5e1a5305c697b347d90d6" - integrity sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw== - -function-bind@^1.1.2: - version "1.1.2" - resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.2.tgz#2c02d864d97f3ea6c8830c464cbd11ab6eab7a1c" - integrity sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA== - -gensync@^1.0.0-beta.1, gensync@^1.0.0-beta.2: - version "1.0.0-beta.2" - resolved "https://registry.yarnpkg.com/gensync/-/gensync-1.0.0-beta.2.tgz#32a6ee76c3d7f52d46b2b1ae5d93fea8580a25e0" - integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg== - -get-intrinsic@^1.1.3, get-intrinsic@^1.2.4: - version "1.2.4" - resolved "https://registry.yarnpkg.com/get-intrinsic/-/get-intrinsic-1.2.4.tgz#e385f5a4b5227d449c3eabbad05494ef0abbeadd" - integrity sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ== - dependencies: - es-errors "^1.3.0" - function-bind "^1.1.2" - has-proto "^1.0.1" - has-symbols "^1.0.3" - hasown "^2.0.0" - -get-own-enumerable-property-symbols@^3.0.0: - version "3.0.2" - resolved "https://registry.yarnpkg.com/get-own-enumerable-property-symbols/-/get-own-enumerable-property-symbols-3.0.2.tgz#b5fde77f22cbe35f390b4e089922c50bce6ef664" - integrity sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g== - -get-stream@^4.1.0: - version "4.1.0" - resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-4.1.0.tgz#c1b255575f3dc21d59bfc79cd3d2b46b1c3a54b5" - integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w== - dependencies: - pump "^3.0.0" - -get-stream@^5.1.0: - version "5.2.0" - resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-5.2.0.tgz#4966a1795ee5ace65e706c4b7beb71257d6e22d3" - integrity sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA== - dependencies: - pump "^3.0.0" - -get-stream@^6.0.0: - version "6.0.1" - resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-6.0.1.tgz#a262d8eef67aced57c2852ad6167526a43cbf7b7" - integrity sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg== - -github-from-package@0.0.0: - version "0.0.0" - resolved "https://registry.yarnpkg.com/github-from-package/-/github-from-package-0.0.0.tgz#97fb5d96bfde8973313f20e8288ef9a167fa64ce" - integrity sha512-SyHy3T1v2NUXn29OsWdxmK6RwHD+vkj3v8en8AOBZ1wBQ/hCAQ5bAQTD02kW4W9tUp/3Qh6J8r9EvntiyCmOOw== - -github-slugger@^1.4.0: - version "1.5.0" - resolved "https://registry.yarnpkg.com/github-slugger/-/github-slugger-1.5.0.tgz#17891bbc73232051474d68bd867a34625c955f7d" - integrity sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw== - -glob-parent@^5.1.2, glob-parent@~5.1.2: - version "5.1.2" - resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.2.tgz#869832c58034fe68a4093c17dc15e8340d8401c4" - integrity sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow== - dependencies: - is-glob "^4.0.1" - -glob-parent@^6.0.1: - version "6.0.2" - resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-6.0.2.tgz#6d237d99083950c79290f24c7642a3de9a28f9e3" - integrity sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A== - dependencies: - is-glob "^4.0.3" - -glob-to-regexp@^0.4.1: - version "0.4.1" - resolved "https://registry.yarnpkg.com/glob-to-regexp/-/glob-to-regexp-0.4.1.tgz#c75297087c851b9a578bd217dd59a92f59fe546e" - integrity sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw== - -glob@^7.0.0, glob@^7.1.3, glob@^7.1.6: - version "7.2.3" - resolved "https://registry.yarnpkg.com/glob/-/glob-7.2.3.tgz#b8df0fb802bbfa8e89bd1d938b4e16578ed44f2b" - integrity sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q== - dependencies: - fs.realpath "^1.0.0" - inflight "^1.0.4" - inherits "2" - minimatch "^3.1.1" - once "^1.3.0" - path-is-absolute "^1.0.0" - -global-dirs@^3.0.0: - version "3.0.1" - resolved "https://registry.yarnpkg.com/global-dirs/-/global-dirs-3.0.1.tgz#0c488971f066baceda21447aecb1a8b911d22485" - integrity sha512-NBcGGFbBA9s1VzD41QXDG+3++t9Mn5t1FpLdhESY6oKY4gYTFpX4wO3sqGUa0Srjtbfj3szX0RnemmrVRUdULA== - dependencies: - ini "2.0.0" - -global-modules@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-2.0.0.tgz#997605ad2345f27f51539bea26574421215c7780" - integrity sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A== - dependencies: - global-prefix "^3.0.0" - -global-prefix@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-3.0.0.tgz#fc85f73064df69f50421f47f883fe5b913ba9b97" - integrity sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg== - dependencies: - ini "^1.3.5" - kind-of "^6.0.2" - which "^1.3.1" - -globals@^11.1.0: - version "11.12.0" - resolved "https://registry.yarnpkg.com/globals/-/globals-11.12.0.tgz#ab8795338868a0babd8525758018c2a7eb95c42e" - integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA== - -globby@^11.0.1, globby@^11.0.4, globby@^11.1.0: - version "11.1.0" - resolved "https://registry.yarnpkg.com/globby/-/globby-11.1.0.tgz#bd4be98bb042f83d796f7e3811991fbe82a0d34b" - integrity sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g== - dependencies: - array-union "^2.1.0" - dir-glob "^3.0.1" - fast-glob "^3.2.9" - ignore "^5.2.0" - merge2 "^1.4.1" - slash "^3.0.0" - -globby@^13.1.1: - version "13.2.2" - resolved "https://registry.yarnpkg.com/globby/-/globby-13.2.2.tgz#63b90b1bf68619c2135475cbd4e71e66aa090592" - integrity sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w== - dependencies: - dir-glob "^3.0.1" - fast-glob "^3.3.0" - ignore "^5.2.4" - merge2 "^1.4.1" - slash "^4.0.0" - -gopd@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/gopd/-/gopd-1.0.1.tgz#29ff76de69dac7489b7c0918a5788e56477c332c" - integrity sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA== - dependencies: - get-intrinsic "^1.1.3" - -got@^9.6.0: - version "9.6.0" - resolved "https://registry.yarnpkg.com/got/-/got-9.6.0.tgz#edf45e7d67f99545705de1f7bbeeeb121765ed85" - integrity sha512-R7eWptXuGYxwijs0eV+v3o6+XH1IqVK8dJOEecQfTmkncw9AV4dcw/Dhxi8MdlqPthxxpZyizMzyg8RTmEsG+Q== - dependencies: - "@sindresorhus/is" "^0.14.0" - "@szmarczak/http-timer" "^1.1.2" - cacheable-request "^6.0.0" - decompress-response "^3.3.0" - duplexer3 "^0.1.4" - get-stream "^4.1.0" - lowercase-keys "^1.0.1" - mimic-response "^1.0.1" - p-cancelable "^1.0.0" - to-readable-stream "^1.0.0" - url-parse-lax "^3.0.0" - -graceful-fs@^4.1.2, graceful-fs@^4.1.6, graceful-fs@^4.2.0, graceful-fs@^4.2.11, graceful-fs@^4.2.4, graceful-fs@^4.2.6, graceful-fs@^4.2.9: - version "4.2.11" - resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.11.tgz#4183e4e8bf08bb6e05bbb2f7d2e0c8f712ca40e3" - integrity sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ== - -gray-matter@^4.0.3: - version "4.0.3" - resolved "https://registry.yarnpkg.com/gray-matter/-/gray-matter-4.0.3.tgz#e893c064825de73ea1f5f7d88c7a9f7274288798" - integrity sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q== - dependencies: - js-yaml "^3.13.1" - kind-of "^6.0.2" - section-matter "^1.0.0" - strip-bom-string "^1.0.0" - -gzip-size@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/gzip-size/-/gzip-size-6.0.0.tgz#065367fd50c239c0671cbcbad5be3e2eeb10e462" - integrity sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q== - dependencies: - duplexer "^0.1.2" - -handle-thing@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/handle-thing/-/handle-thing-2.0.1.tgz#857f79ce359580c340d43081cc648970d0bb234e" - integrity sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg== - -has-flag@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd" - integrity sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw== - -has-flag@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz#944771fd9c81c81265c4d6941860da06bb59479b" - integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ== - -has-property-descriptors@^1.0.0, has-property-descriptors@^1.0.2: - version "1.0.2" - resolved "https://registry.yarnpkg.com/has-property-descriptors/-/has-property-descriptors-1.0.2.tgz#963ed7d071dc7bf5f084c5bfbe0d1b6222586854" - integrity sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg== - dependencies: - es-define-property "^1.0.0" - -has-proto@^1.0.1: - version "1.0.3" - resolved "https://registry.yarnpkg.com/has-proto/-/has-proto-1.0.3.tgz#b31ddfe9b0e6e9914536a6ab286426d0214f77fd" - integrity sha512-SJ1amZAJUiZS+PhsVLf5tGydlaVB8EdFpaSO4gmiUKUOxk8qzn5AIy4ZeJUmh22znIdk/uMAUT2pl3FxzVUH+Q== - -has-symbols@^1.0.3: - version "1.0.3" - resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.3.tgz#bb7b2c4349251dce87b125f7bdf874aa7c8b39f8" - integrity sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A== - -has-yarn@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/has-yarn/-/has-yarn-2.1.0.tgz#137e11354a7b5bf11aa5cb649cf0c6f3ff2b2e77" - integrity sha512-UqBRqi4ju7T+TqGNdqAO0PaSVGsDGJUBQvk9eUWNGRY1CFGDzYhLWoM7JQEemnlvVcv/YEmc2wNW8BC24EnUsw== - -hasown@^2.0.0, hasown@^2.0.2: - version "2.0.2" - resolved "https://registry.yarnpkg.com/hasown/-/hasown-2.0.2.tgz#003eaf91be7adc372e84ec59dc37252cedb80003" - integrity sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ== - dependencies: - function-bind "^1.1.2" - -hast-to-hyperscript@^9.0.0: - version "9.0.1" - resolved "https://registry.yarnpkg.com/hast-to-hyperscript/-/hast-to-hyperscript-9.0.1.tgz#9b67fd188e4c81e8ad66f803855334173920218d" - integrity sha512-zQgLKqF+O2F72S1aa4y2ivxzSlko3MAvxkwG8ehGmNiqd98BIN3JM1rAJPmplEyLmGLO2QZYJtIneOSZ2YbJuA== - dependencies: - "@types/unist" "^2.0.3" - comma-separated-tokens "^1.0.0" - property-information "^5.3.0" - space-separated-tokens "^1.0.0" - style-to-object "^0.3.0" - unist-util-is "^4.0.0" - web-namespaces "^1.0.0" - -hast-util-from-parse5@^6.0.0: - version "6.0.1" - resolved "https://registry.yarnpkg.com/hast-util-from-parse5/-/hast-util-from-parse5-6.0.1.tgz#554e34abdeea25ac76f5bd950a1f0180e0b3bc2a" - integrity sha512-jeJUWiN5pSxW12Rh01smtVkZgZr33wBokLzKLwinYOUfSzm1Nl/c3GUGebDyOKjdsRgMvoVbV0VpAcpjF4NrJA== - dependencies: - "@types/parse5" "^5.0.0" - hastscript "^6.0.0" - property-information "^5.0.0" - vfile "^4.0.0" - vfile-location "^3.2.0" - web-namespaces "^1.0.0" - -hast-util-parse-selector@^2.0.0: - version "2.2.5" - resolved "https://registry.yarnpkg.com/hast-util-parse-selector/-/hast-util-parse-selector-2.2.5.tgz#d57c23f4da16ae3c63b3b6ca4616683313499c3a" - integrity sha512-7j6mrk/qqkSehsM92wQjdIgWM2/BW61u/53G6xmC8i1OmEdKLHbk419QKQUjz6LglWsfqoiHmyMRkP1BGjecNQ== - -hast-util-raw@6.0.1: - version "6.0.1" - resolved "https://registry.yarnpkg.com/hast-util-raw/-/hast-util-raw-6.0.1.tgz#973b15930b7529a7b66984c98148b46526885977" - integrity sha512-ZMuiYA+UF7BXBtsTBNcLBF5HzXzkyE6MLzJnL605LKE8GJylNjGc4jjxazAHUtcwT5/CEt6afRKViYB4X66dig== - dependencies: - "@types/hast" "^2.0.0" - hast-util-from-parse5 "^6.0.0" - hast-util-to-parse5 "^6.0.0" - html-void-elements "^1.0.0" - parse5 "^6.0.0" - unist-util-position "^3.0.0" - vfile "^4.0.0" - web-namespaces "^1.0.0" - xtend "^4.0.0" - zwitch "^1.0.0" - -hast-util-to-parse5@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/hast-util-to-parse5/-/hast-util-to-parse5-6.0.0.tgz#1ec44650b631d72952066cea9b1445df699f8479" - integrity sha512-Lu5m6Lgm/fWuz8eWnrKezHtVY83JeRGaNQ2kn9aJgqaxvVkFCZQBEhgodZUDUvoodgyROHDb3r5IxAEdl6suJQ== - dependencies: - hast-to-hyperscript "^9.0.0" - property-information "^5.0.0" - web-namespaces "^1.0.0" - xtend "^4.0.0" - zwitch "^1.0.0" - -hastscript@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/hastscript/-/hastscript-6.0.0.tgz#e8768d7eac56c3fdeac8a92830d58e811e5bf640" - integrity sha512-nDM6bvd7lIqDUiYEiu5Sl/+6ReP0BMk/2f4U/Rooccxkj0P5nm+acM5PrGJ/t5I8qPGiqZSE6hVAwZEdZIvP4w== - dependencies: - "@types/hast" "^2.0.0" - comma-separated-tokens "^1.0.0" - hast-util-parse-selector "^2.0.0" - property-information "^5.0.0" - space-separated-tokens "^1.0.0" - -he@^1.2.0: - version "1.2.0" - resolved "https://registry.yarnpkg.com/he/-/he-1.2.0.tgz#84ae65fa7eafb165fddb61566ae14baf05664f0f" - integrity sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw== - -history@^4.9.0: - version "4.10.1" - resolved "https://registry.yarnpkg.com/history/-/history-4.10.1.tgz#33371a65e3a83b267434e2b3f3b1b4c58aad4cf3" - integrity sha512-36nwAD620w12kuzPAsyINPWJqlNbij+hpK1k9XRloDtym8mxzGYl2c17LnV6IAGB2Dmg4tEa7G7DlawS0+qjew== - dependencies: - "@babel/runtime" "^7.1.2" - loose-envify "^1.2.0" - resolve-pathname "^3.0.0" - tiny-invariant "^1.0.2" - tiny-warning "^1.0.0" - value-equal "^1.0.1" - -hoist-non-react-statics@^3.1.0: - version "3.3.2" - resolved "https://registry.yarnpkg.com/hoist-non-react-statics/-/hoist-non-react-statics-3.3.2.tgz#ece0acaf71d62c2969c2ec59feff42a4b1a85b45" - integrity sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw== - dependencies: - react-is "^16.7.0" - -hpack.js@^2.1.6: - version "2.1.6" - resolved "https://registry.yarnpkg.com/hpack.js/-/hpack.js-2.1.6.tgz#87774c0949e513f42e84575b3c45681fade2a0b2" - integrity sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ== - dependencies: - inherits "^2.0.1" - obuf "^1.0.0" - readable-stream "^2.0.1" - wbuf "^1.1.0" - -htm@^3.1.1: - version "3.1.1" - resolved "https://registry.yarnpkg.com/htm/-/htm-3.1.1.tgz#49266582be0dc66ed2235d5ea892307cc0c24b78" - integrity sha512-983Vyg8NwUE7JkZ6NmOqpCZ+sh1bKv2iYTlUkzlWmA5JD2acKoxd4KVxbMmxX/85mtfdnDmTFoNKcg5DGAvxNQ== - -html-entities@^2.3.2: - version "2.5.2" - resolved "https://registry.yarnpkg.com/html-entities/-/html-entities-2.5.2.tgz#201a3cf95d3a15be7099521620d19dfb4f65359f" - integrity sha512-K//PSRMQk4FZ78Kyau+mZurHn3FH0Vwr+H36eE0rPbeYkRRi9YxceYPhuN60UwWorxyKHhqoAJl2OFKa4BVtaA== - -html-escaper@^2.0.2: - version "2.0.2" - resolved "https://registry.yarnpkg.com/html-escaper/-/html-escaper-2.0.2.tgz#dfd60027da36a36dfcbe236262c00a5822681453" - integrity sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg== - -html-minifier-terser@^6.0.2, html-minifier-terser@^6.1.0: - version "6.1.0" - resolved "https://registry.yarnpkg.com/html-minifier-terser/-/html-minifier-terser-6.1.0.tgz#bfc818934cc07918f6b3669f5774ecdfd48f32ab" - integrity sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw== - dependencies: - camel-case "^4.1.2" - clean-css "^5.2.2" - commander "^8.3.0" - he "^1.2.0" - param-case "^3.0.4" - relateurl "^0.2.7" - terser "^5.10.0" - -html-tags@^3.2.0: - version "3.3.1" - resolved "https://registry.yarnpkg.com/html-tags/-/html-tags-3.3.1.tgz#a04026a18c882e4bba8a01a3d39cfe465d40b5ce" - integrity sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ== - -html-void-elements@^1.0.0: - version "1.0.5" - resolved "https://registry.yarnpkg.com/html-void-elements/-/html-void-elements-1.0.5.tgz#ce9159494e86d95e45795b166c2021c2cfca4483" - integrity sha512-uE/TxKuyNIcx44cIWnjr/rfIATDH7ZaOMmstu0CwhFG1Dunhlp4OC6/NMbhiwoq5BpW0ubi303qnEk/PZj614w== - -html-webpack-plugin@^5.5.0: - version "5.6.2" - resolved "https://registry.yarnpkg.com/html-webpack-plugin/-/html-webpack-plugin-5.6.2.tgz#174a67c8e55aa3fa2ba94c8e8e42894bfe4978ea" - integrity sha512-q7xp/FO9RGBVoTKNItkdX1jKLscLFkgn/dLVFNYbHVbfHLBk6DYW5nsQ8kCzIWcgKP/kUBocetjvav6lD8YfCQ== - dependencies: - "@types/html-minifier-terser" "^6.0.0" - html-minifier-terser "^6.0.2" - lodash "^4.17.21" - pretty-error "^4.0.0" - tapable "^2.0.0" - -htmlparser2@^6.1.0: - version "6.1.0" - resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-6.1.0.tgz#c4d762b6c3371a05dbe65e94ae43a9f845fb8fb7" - integrity sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A== - dependencies: - domelementtype "^2.0.1" - domhandler "^4.0.0" - domutils "^2.5.2" - entities "^2.0.0" - -htmlparser2@^9.1.0: - version "9.1.0" - resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-9.1.0.tgz#cdb498d8a75a51f739b61d3f718136c369bc8c23" - integrity sha512-5zfg6mHUoaer/97TxnGpxmbR7zJtPwIYFMZ/H5ucTlPZhKvtum05yiPK3Mgai3a0DyVxv7qYqoweaEd2nrYQzQ== - dependencies: - domelementtype "^2.3.0" - domhandler "^5.0.3" - domutils "^3.1.0" - entities "^4.5.0" - -http-cache-semantics@^4.0.0: - version "4.1.1" - resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-4.1.1.tgz#abe02fcb2985460bf0323be664436ec3476a6d5a" - integrity sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ== - -http-deceiver@^1.2.7: - version "1.2.7" - resolved "https://registry.yarnpkg.com/http-deceiver/-/http-deceiver-1.2.7.tgz#fa7168944ab9a519d337cb0bec7284dc3e723d87" - integrity sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw== - -http-errors@2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-2.0.0.tgz#b7774a1486ef73cf7667ac9ae0858c012c57b9d3" - integrity sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ== - dependencies: - depd "2.0.0" - inherits "2.0.4" - setprototypeof "1.2.0" - statuses "2.0.1" - toidentifier "1.0.1" - -http-errors@~1.6.2: - version "1.6.3" - resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.6.3.tgz#8b55680bb4be283a0b5bf4ea2e38580be1d9320d" - integrity sha512-lks+lVC8dgGyh97jxvxeYTWQFvh4uw4yC12gVl63Cg30sjPX4wuGcdkICVXDAESr6OJGjqGA8Iz5mkeN6zlD7A== - dependencies: - depd "~1.1.2" - inherits "2.0.3" - setprototypeof "1.1.0" - statuses ">= 1.4.0 < 2" - -http-parser-js@>=0.5.1: - version "0.5.8" - resolved "https://registry.yarnpkg.com/http-parser-js/-/http-parser-js-0.5.8.tgz#af23090d9ac4e24573de6f6aecc9d84a48bf20e3" - integrity sha512-SGeBX54F94Wgu5RH3X5jsDtf4eHyRogWX1XGT3b4HuW3tQPM4AaBzoUji/4AAJNXCEOWZ5O0DgZmJw1947gD5Q== - -http-proxy-middleware@^2.0.3: - version "2.0.7" - resolved "https://registry.yarnpkg.com/http-proxy-middleware/-/http-proxy-middleware-2.0.7.tgz#915f236d92ae98ef48278a95dedf17e991936ec6" - integrity sha512-fgVY8AV7qU7z/MmXJ/rxwbrtQH4jBQ9m7kp3llF0liB7glmFeVZFBepQb32T3y8n8k2+AEYuMPCpinYW+/CuRA== - dependencies: - "@types/http-proxy" "^1.17.8" - http-proxy "^1.18.1" - is-glob "^4.0.1" - is-plain-obj "^3.0.0" - micromatch "^4.0.2" - -http-proxy@^1.18.1: - version "1.18.1" - resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.18.1.tgz#401541f0534884bbf95260334e72f88ee3976549" - integrity sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ== - dependencies: - eventemitter3 "^4.0.0" - follow-redirects "^1.0.0" - requires-port "^1.0.0" - -human-signals@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/human-signals/-/human-signals-2.1.0.tgz#dc91fcba42e4d06e4abaed33b3e7a3c02f514ea0" - integrity sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw== - -iconv-lite@0.4.24: - version "0.4.24" - resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz#2022b4b25fbddc21d2f524974a474aafe733908b" - integrity sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA== - dependencies: - safer-buffer ">= 2.1.2 < 3" - -iconv-lite@0.6.3, iconv-lite@^0.6.3: - version "0.6.3" - resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.6.3.tgz#a52f80bf38da1952eb5c681790719871a1a72501" - integrity sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw== - dependencies: - safer-buffer ">= 2.1.2 < 3.0.0" - -icss-utils@^5.0.0, icss-utils@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/icss-utils/-/icss-utils-5.1.0.tgz#c6be6858abd013d768e98366ae47e25d5887b1ae" - integrity sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA== - -ieee754@^1.1.13: - version "1.2.1" - resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.2.1.tgz#8eb7a10a63fff25d15a57b001586d177d1b0d352" - integrity sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA== - -ignore@^5.2.0, ignore@^5.2.4: - version "5.3.2" - resolved "https://registry.yarnpkg.com/ignore/-/ignore-5.3.2.tgz#3cd40e729f3643fd87cb04e50bf0eb722bc596f5" - integrity sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g== - -image-size@^1.0.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/image-size/-/image-size-1.1.1.tgz#ddd67d4dc340e52ac29ce5f546a09f4e29e840ac" - integrity sha512-541xKlUw6jr/6gGuk92F+mYM5zaFAc5ahphvkqvNe2bQ6gVBkd6bfrmVJ2t4KDAfikAYZyIqTnktX3i6/aQDrQ== - dependencies: - queue "6.0.2" - -immer@^9.0.7: - version "9.0.21" - resolved "https://registry.yarnpkg.com/immer/-/immer-9.0.21.tgz#1e025ea31a40f24fb064f1fef23e931496330176" - integrity sha512-bc4NBHqOqSfRW7POMkHd51LvClaeMXpm8dx0e8oE2GORbq5aRK7Bxl4FyzVLdGtLmvLKL7BTDBG5ACQm4HWjTA== - -import-fresh@^3.1.0, import-fresh@^3.2.1, import-fresh@^3.3.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/import-fresh/-/import-fresh-3.3.0.tgz#37162c25fcb9ebaa2e6e53d5b4d88ce17d9e0c2b" - integrity sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw== - dependencies: - parent-module "^1.0.0" - resolve-from "^4.0.0" - -import-lazy@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/import-lazy/-/import-lazy-2.1.0.tgz#05698e3d45c88e8d7e9d92cb0584e77f096f3e43" - integrity sha512-m7ZEHgtw69qOGw+jwxXkHlrlIPdTGkyh66zXZ1ajZbxkDBNjSY/LGbmjc7h0s2ELsUDTAhFr55TrPSSqJGPG0A== - -imurmurhash@^0.1.4: - version "0.1.4" - resolved "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz#9218b9b2b928a238b13dc4fb6b6d576f231453ea" - integrity sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA== - -indent-string@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/indent-string/-/indent-string-4.0.0.tgz#624f8f4497d619b2d9768531d58f4122854d7251" - integrity sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg== - -infima@0.2.0-alpha.43: - version "0.2.0-alpha.43" - resolved "https://registry.yarnpkg.com/infima/-/infima-0.2.0-alpha.43.tgz#f7aa1d7b30b6c08afef441c726bac6150228cbe0" - integrity sha512-2uw57LvUqW0rK/SWYnd/2rRfxNA5DDNOh33jxF7fy46VWoNhGxiUQyVZHbBMjQ33mQem0cjdDVwgWVAmlRfgyQ== - -inflight@^1.0.4: - version "1.0.6" - resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9" - integrity sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA== - dependencies: - once "^1.3.0" - wrappy "1" - -inherits@2, inherits@2.0.4, inherits@^2.0.0, inherits@^2.0.1, inherits@^2.0.3, inherits@^2.0.4, inherits@~2.0.3: - version "2.0.4" - resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c" - integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ== - -inherits@2.0.3: - version "2.0.3" - resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de" - integrity sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw== - -ini@2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/ini/-/ini-2.0.0.tgz#e5fd556ecdd5726be978fa1001862eacb0a94bc5" - integrity sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA== - -ini@^1.3.5, ini@~1.3.0: - version "1.3.8" - resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.8.tgz#a29da425b48806f34767a4efce397269af28432c" - integrity sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew== - -inline-style-parser@0.1.1: - version "0.1.1" - resolved "https://registry.yarnpkg.com/inline-style-parser/-/inline-style-parser-0.1.1.tgz#ec8a3b429274e9c0a1f1c4ffa9453a7fef72cea1" - integrity sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q== - -interpret@^1.0.0: - version "1.4.0" - resolved "https://registry.yarnpkg.com/interpret/-/interpret-1.4.0.tgz#665ab8bc4da27a774a40584e812e3e0fa45b1a1e" - integrity sha512-agE4QfB2Lkp9uICn7BAqoscw4SZP9kTE2hxiFI3jBPmXJfdqiahTbUuKGsMoN2GtqL9AxhYioAcVvgsb1HvRbA== - -invariant@^2.2.4: - version "2.2.4" - resolved "https://registry.yarnpkg.com/invariant/-/invariant-2.2.4.tgz#610f3c92c9359ce1db616e538008d23ff35158e6" - integrity sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA== - dependencies: - loose-envify "^1.0.0" - -ipaddr.js@1.9.1: - version "1.9.1" - resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.9.1.tgz#bff38543eeb8984825079ff3a2a8e6cbd46781b3" - integrity sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g== - -ipaddr.js@^2.0.1: - version "2.2.0" - resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-2.2.0.tgz#d33fa7bac284f4de7af949638c9d68157c6b92e8" - integrity sha512-Ag3wB2o37wslZS19hZqorUnrnzSkpOVy+IiiDEiTqNubEYpYuHWIf6K4psgN2ZWKExS4xhVCrRVfb/wfW8fWJA== - -is-alphabetical@1.0.4, is-alphabetical@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-alphabetical/-/is-alphabetical-1.0.4.tgz#9e7d6b94916be22153745d184c298cbf986a686d" - integrity sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg== - -is-alphanumerical@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-alphanumerical/-/is-alphanumerical-1.0.4.tgz#7eb9a2431f855f6b1ef1a78e326df515696c4dbf" - integrity sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A== - dependencies: - is-alphabetical "^1.0.0" - is-decimal "^1.0.0" - -is-arrayish@^0.2.1: - version "0.2.1" - resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.2.1.tgz#77c99840527aa8ecb1a8ba697b80645a7a926a9d" - integrity sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg== - -is-arrayish@^0.3.1: - version "0.3.2" - resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.3.2.tgz#4574a2ae56f7ab206896fb431eaeed066fdf8f03" - integrity sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ== - -is-binary-path@~2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-2.1.0.tgz#ea1f7f3b80f064236e83470f86c09c254fb45b09" - integrity sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw== - dependencies: - binary-extensions "^2.0.0" - -is-buffer@^2.0.0: - version "2.0.5" - resolved "https://registry.yarnpkg.com/is-buffer/-/is-buffer-2.0.5.tgz#ebc252e400d22ff8d77fa09888821a24a658c191" - integrity sha512-i2R6zNFDwgEHJyQUtJEk0XFi1i0dPFn/oqjK3/vPCcDeJvW5NQ83V8QbicfF1SupOaB0h8ntgBC2YiE7dfyctQ== - -is-ci@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/is-ci/-/is-ci-2.0.0.tgz#6bc6334181810e04b5c22b3d589fdca55026404c" - integrity sha512-YfJT7rkpQB0updsdHLGWrvhBJfcfzNNawYDNIyQXJz0IViGf75O8EBPKSdvw2rF+LGCsX4FZ8tcr3b19LcZq4w== - dependencies: - ci-info "^2.0.0" - -is-core-module@^2.13.0: - version "2.15.1" - resolved "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.15.1.tgz#a7363a25bee942fefab0de13bf6aa372c82dcc37" - integrity sha512-z0vtXSwucUJtANQWldhbtbt7BnL0vxiFjIdDLAatwhDYty2bad6s+rijD6Ri4YuYJubLzIJLUidCh09e1djEVQ== - dependencies: - hasown "^2.0.2" - -is-decimal@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-decimal/-/is-decimal-1.0.4.tgz#65a3a5958a1c5b63a706e1b333d7cd9f630d3fa5" - integrity sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw== - -is-docker@^2.0.0, is-docker@^2.1.1: - version "2.2.1" - resolved "https://registry.yarnpkg.com/is-docker/-/is-docker-2.2.1.tgz#33eeabe23cfe86f14bde4408a02c0cfb853acdaa" - integrity sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ== - -is-extendable@^0.1.0: - version "0.1.1" - resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-0.1.1.tgz#62b110e289a471418e3ec36a617d472e301dfc89" - integrity sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw== - -is-extglob@^2.1.1: - version "2.1.1" - resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2" - integrity sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ== - -is-fullwidth-code-point@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz#f116f8064fe90b3f7844a38997c0b75051269f1d" - integrity sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg== - -is-glob@^4.0.1, is-glob@^4.0.3, is-glob@~4.0.1: - version "4.0.3" - resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.3.tgz#64f61e42cbbb2eec2071a9dac0b28ba1e65d5084" - integrity sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg== - dependencies: - is-extglob "^2.1.1" - -is-hexadecimal@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-hexadecimal/-/is-hexadecimal-1.0.4.tgz#cc35c97588da4bd49a8eedd6bc4082d44dcb23a7" - integrity sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw== - -is-installed-globally@^0.4.0: - version "0.4.0" - resolved "https://registry.yarnpkg.com/is-installed-globally/-/is-installed-globally-0.4.0.tgz#9a0fd407949c30f86eb6959ef1b7994ed0b7b520" - integrity sha512-iwGqO3J21aaSkC7jWnHP/difazwS7SFeIqxv6wEtLU8Y5KlzFTjyqcSIT0d8s4+dDhKytsk9PJZ2BkS5eZwQRQ== - dependencies: - global-dirs "^3.0.0" - is-path-inside "^3.0.2" - -is-npm@^5.0.0: - version "5.0.0" - resolved "https://registry.yarnpkg.com/is-npm/-/is-npm-5.0.0.tgz#43e8d65cc56e1b67f8d47262cf667099193f45a8" - integrity sha512-WW/rQLOazUq+ST/bCAVBp/2oMERWLsR7OrKyt052dNDk4DHcDE0/7QSXITlmi+VBcV13DfIbysG3tZJm5RfdBA== - -is-number@^7.0.0: - version "7.0.0" - resolved "https://registry.yarnpkg.com/is-number/-/is-number-7.0.0.tgz#7535345b896734d5f80c4d06c50955527a14f12b" - integrity sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng== - -is-obj@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/is-obj/-/is-obj-1.0.1.tgz#3e4729ac1f5fde025cd7d83a896dab9f4f67db0f" - integrity sha512-l4RyHgRqGN4Y3+9JHVrNqO+tN0rV5My76uW5/nuO4K1b6vw5G8d/cmFjP9tRfEsdhZNt0IFdZuK/c2Vr4Nb+Qg== - -is-obj@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/is-obj/-/is-obj-2.0.0.tgz#473fb05d973705e3fd9620545018ca8e22ef4982" - integrity sha512-drqDG3cbczxxEJRoOXcOjtdp1J/lyp1mNn0xaznRs8+muBhgQcrnbspox5X5fOw0HnMnbfDzvnEMEtqDEJEo8w== - -is-path-cwd@^2.2.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/is-path-cwd/-/is-path-cwd-2.2.0.tgz#67d43b82664a7b5191fd9119127eb300048a9fdb" - integrity sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ== - -is-path-inside@^3.0.2: - version "3.0.3" - resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-3.0.3.tgz#d231362e53a07ff2b0e0ea7fed049161ffd16283" - integrity sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ== - -is-plain-obj@^2.0.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-2.1.0.tgz#45e42e37fccf1f40da8e5f76ee21515840c09287" - integrity sha512-YWnfyRwxL/+SsrWYfOpUtz5b3YD+nyfkHvjbcanzk8zgyO4ASD67uVMRt8k5bM4lLMDnXfriRhOpemw+NfT1eA== - -is-plain-obj@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-3.0.0.tgz#af6f2ea14ac5a646183a5bbdb5baabbc156ad9d7" - integrity sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA== - -is-plain-object@^2.0.4: - version "2.0.4" - resolved "https://registry.yarnpkg.com/is-plain-object/-/is-plain-object-2.0.4.tgz#2c163b3fafb1b606d9d17928f05c2a1c38e07677" - integrity sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og== - dependencies: - isobject "^3.0.1" - -is-regexp@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/is-regexp/-/is-regexp-1.0.0.tgz#fd2d883545c46bac5a633e7b9a09e87fa2cb5069" - integrity sha512-7zjFAPO4/gwyQAAgRRmqeEeyIICSdmCqa3tsVHMdBzaXXRiqopZL4Cyghg/XulGWrtABTpbnYYzzIRffLkP4oA== - -is-root@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/is-root/-/is-root-2.1.0.tgz#809e18129cf1129644302a4f8544035d51984a9c" - integrity sha512-AGOriNp96vNBd3HtU+RzFEc75FfR5ymiYv8E553I71SCeXBiMsVDUtdio1OEFvrPyLIQ9tVR5RxXIFe5PUFjMg== - -is-stream@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-2.0.1.tgz#fac1e3d53b97ad5a9d0ae9cef2389f5810a5c077" - integrity sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg== - -is-typedarray@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/is-typedarray/-/is-typedarray-1.0.0.tgz#e479c80858df0c1b11ddda6940f96011fcda4a9a" - integrity sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA== - -is-whitespace-character@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-whitespace-character/-/is-whitespace-character-1.0.4.tgz#0858edd94a95594c7c9dd0b5c174ec6e45ee4aa7" - integrity sha512-SDweEzfIZM0SJV0EUga669UTKlmL0Pq8Lno0QDQsPnvECB3IM2aP0gdx5TrU0A01MAPfViaZiI2V1QMZLaKK5w== - -is-word-character@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/is-word-character/-/is-word-character-1.0.4.tgz#ce0e73216f98599060592f62ff31354ddbeb0230" - integrity sha512-5SMO8RVennx3nZrqtKwCGyyetPE9VDba5ugvKLaD4KopPG5kR4mQ7tNt/r7feL5yt5h3lpuBbIUmCOG2eSzXHA== - -is-wsl@^2.2.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-2.2.0.tgz#74a4c76e77ca9fd3f932f290c17ea326cd157271" - integrity sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww== - dependencies: - is-docker "^2.0.0" - -is-yarn-global@^0.3.0: - version "0.3.0" - resolved "https://registry.yarnpkg.com/is-yarn-global/-/is-yarn-global-0.3.0.tgz#d502d3382590ea3004893746754c89139973e232" - integrity sha512-VjSeb/lHmkoyd8ryPVIKvOCn4D1koMqY+vqyjjUfc3xyKtP4dYOxM44sZrnqQSzSds3xyOrUTLTC9LVCVgLngw== - -isarray@0.0.1: - version "0.0.1" - resolved "https://registry.yarnpkg.com/isarray/-/isarray-0.0.1.tgz#8a18acfca9a8f4177e09abfc6038939b05d1eedf" - integrity sha512-D2S+3GLxWH+uhrNEcoh/fnmYeP8E8/zHl644d/jdA0g2uyXvy3sb0qxotE+ne0LtccHknQzWwZEzhak7oJ0COQ== - -isarray@~1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11" - integrity sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ== - -isexe@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10" - integrity sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw== - -isobject@^3.0.1: - version "3.0.1" - resolved "https://registry.yarnpkg.com/isobject/-/isobject-3.0.1.tgz#4e431e92b11a9731636aa1f9c8d1ccbcfdab78df" - integrity sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg== - -jest-util@^29.7.0: - version "29.7.0" - resolved "https://registry.yarnpkg.com/jest-util/-/jest-util-29.7.0.tgz#23c2b62bfb22be82b44de98055802ff3710fc0bc" - integrity sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA== - dependencies: - "@jest/types" "^29.6.3" - "@types/node" "*" - chalk "^4.0.0" - ci-info "^3.2.0" - graceful-fs "^4.2.9" - picomatch "^2.2.3" - -jest-worker@^27.4.5: - version "27.5.1" - resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-27.5.1.tgz#8d146f0900e8973b106b6f73cc1e9a8cb86f8db0" - integrity sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg== - dependencies: - "@types/node" "*" - merge-stream "^2.0.0" - supports-color "^8.0.0" - -jest-worker@^29.1.2: - version "29.7.0" - resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-29.7.0.tgz#acad073acbbaeb7262bd5389e1bcf43e10058d4a" - integrity sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw== - dependencies: - "@types/node" "*" - jest-util "^29.7.0" - merge-stream "^2.0.0" - supports-color "^8.0.0" - -jiti@^1.20.0: - version "1.21.6" - resolved "https://registry.yarnpkg.com/jiti/-/jiti-1.21.6.tgz#6c7f7398dd4b3142767f9a168af2f317a428d268" - integrity sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w== - -joi@^17.6.0: - version "17.13.3" - resolved "https://registry.yarnpkg.com/joi/-/joi-17.13.3.tgz#0f5cc1169c999b30d344366d384b12d92558bcec" - integrity sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA== - dependencies: - "@hapi/hoek" "^9.3.0" - "@hapi/topo" "^5.1.0" - "@sideway/address" "^4.1.5" - "@sideway/formula" "^3.0.1" - "@sideway/pinpoint" "^2.0.0" - -"js-tokens@^3.0.0 || ^4.0.0", js-tokens@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499" - integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ== - -js-yaml@^3.13.1: - version "3.14.1" - resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-3.14.1.tgz#dae812fdb3825fa306609a8717383c50c36a0537" - integrity sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g== - dependencies: - argparse "^1.0.7" - esprima "^4.0.0" - -js-yaml@^4.1.0: - version "4.1.0" - resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-4.1.0.tgz#c1fb65f8f5017901cdd2c951864ba18458a10602" - integrity sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA== - dependencies: - argparse "^2.0.1" - -jsesc@^3.0.2, jsesc@~3.0.2: - version "3.0.2" - resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-3.0.2.tgz#bb8b09a6597ba426425f2e4a07245c3d00b9343e" - integrity sha512-xKqzzWXDttJuOcawBt4KnKHHIf5oQ/Cxax+0PWFG+DFDgHNAdi+TXECADI+RYiFUMmx8792xsMbbgXj4CwnP4g== - -json-buffer@3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.0.tgz#5b1f397afc75d677bde8bcfc0e47e1f9a3d9a898" - integrity sha512-CuUqjv0FUZIdXkHPI8MezCnFCdaTAacej1TZYulLoAg1h/PhwkdXFN4V/gzY4g+fMBCOV2xF+rp7t2XD2ns/NQ== - -json-parse-even-better-errors@^2.3.0, json-parse-even-better-errors@^2.3.1: - version "2.3.1" - resolved "https://registry.yarnpkg.com/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz#7c47805a94319928e05777405dc12e1f7a4ee02d" - integrity sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w== - -json-schema-traverse@^0.4.1: - version "0.4.1" - resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz#69f6a87d9513ab8bb8fe63bdb0979c448e684660" - integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg== - -json-schema-traverse@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz#ae7bcb3656ab77a73ba5c49bf654f38e6b6860e2" - integrity sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug== - -json5@^2.1.2, json5@^2.2.3: - version "2.2.3" - resolved "https://registry.yarnpkg.com/json5/-/json5-2.2.3.tgz#78cd6f1a19bdc12b73db5ad0c61efd66c1e29283" - integrity sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg== - -jsonfile@^6.0.1: - version "6.1.0" - resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-6.1.0.tgz#bc55b2634793c679ec6403094eb13698a6ec0aae" - integrity sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ== - dependencies: - universalify "^2.0.0" - optionalDependencies: - graceful-fs "^4.1.6" - -keyv@^3.0.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/keyv/-/keyv-3.1.0.tgz#ecc228486f69991e49e9476485a5be1e8fc5c4d9" - integrity sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA== - dependencies: - json-buffer "3.0.0" - -kind-of@^6.0.0, kind-of@^6.0.2: - version "6.0.3" - resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-6.0.3.tgz#07c05034a6c349fa06e24fa35aa76db4580ce4dd" - integrity sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw== - -kleur@^3.0.3: - version "3.0.3" - resolved "https://registry.yarnpkg.com/kleur/-/kleur-3.0.3.tgz#a79c9ecc86ee1ce3fa6206d1216c501f147fc07e" - integrity sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w== - -latest-version@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/latest-version/-/latest-version-5.1.0.tgz#119dfe908fe38d15dfa43ecd13fa12ec8832face" - integrity sha512-weT+r0kTkRQdCdYCNtkMwWXQTMEswKrFBkm4ckQOMVhhqhIMI1UT2hMj+1iigIhgSZm5gTmrRXBNoGUgaTY1xA== - dependencies: - package-json "^6.3.0" - -launch-editor@^2.6.0: - version "2.9.1" - resolved "https://registry.yarnpkg.com/launch-editor/-/launch-editor-2.9.1.tgz#253f173bd441e342d4344b4dae58291abb425047" - integrity sha512-Gcnl4Bd+hRO9P9icCP/RVVT2o8SFlPXofuCxvA2SaZuH45whSvf5p8x5oih5ftLiVhEI4sp5xDY+R+b3zJBh5w== - dependencies: - picocolors "^1.0.0" - shell-quote "^1.8.1" - -leven@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/leven/-/leven-3.1.0.tgz#77891de834064cccba82ae7842bb6b14a13ed7f2" - integrity sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A== - -lilconfig@^2.0.3: - version "2.1.0" - resolved "https://registry.yarnpkg.com/lilconfig/-/lilconfig-2.1.0.tgz#78e23ac89ebb7e1bfbf25b18043de756548e7f52" - integrity sha512-utWOt/GHzuUxnLKxB6dk81RoOeoNeHgbrXiuGk4yyF5qlRz+iIVWu56E2fqGHFrXz0QNUhLB/8nKqvRH66JKGQ== - -lines-and-columns@^1.1.6: - version "1.2.4" - resolved "https://registry.yarnpkg.com/lines-and-columns/-/lines-and-columns-1.2.4.tgz#eca284f75d2965079309dc0ad9255abb2ebc1632" - integrity sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg== - -loader-runner@^4.2.0: - version "4.3.0" - resolved "https://registry.yarnpkg.com/loader-runner/-/loader-runner-4.3.0.tgz#c1b4a163b99f614830353b16755e7149ac2314e1" - integrity sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg== - -loader-utils@^2.0.0, loader-utils@^2.0.4: - version "2.0.4" - resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-2.0.4.tgz#8b5cb38b5c34a9a018ee1fc0e6a066d1dfcc528c" - integrity sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw== - dependencies: - big.js "^5.2.2" - emojis-list "^3.0.0" - json5 "^2.1.2" - -loader-utils@^3.2.0: - version "3.3.1" - resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-3.3.1.tgz#735b9a19fd63648ca7adbd31c2327dfe281304e5" - integrity sha512-FMJTLMXfCLMLfJxcX9PFqX5qD88Z5MRGaZCVzfuqeZSPsyiBzs+pahDQjbIWz2QIzPZz0NX9Zy4FX3lmK6YHIg== - -locate-path@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-3.0.0.tgz#dbec3b3ab759758071b58fe59fc41871af21400e" - integrity sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A== - dependencies: - p-locate "^3.0.0" - path-exists "^3.0.0" - -locate-path@^5.0.0: - version "5.0.0" - resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-5.0.0.tgz#1afba396afd676a6d42504d0a67a3a7eb9f62aa0" - integrity sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g== - dependencies: - p-locate "^4.1.0" - -locate-path@^6.0.0: - version "6.0.0" - resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-6.0.0.tgz#55321eb309febbc59c4801d931a72452a681d286" - integrity sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw== - dependencies: - p-locate "^5.0.0" - -lodash.curry@^4.0.1: - version "4.1.1" - resolved "https://registry.yarnpkg.com/lodash.curry/-/lodash.curry-4.1.1.tgz#248e36072ede906501d75966200a86dab8b23170" - integrity sha512-/u14pXGviLaweY5JI0IUzgzF2J6Ne8INyzAZjImcryjgkZ+ebruBxy2/JaOOkTqScddcYtakjhSaeemV8lR0tA== - -lodash.debounce@^4.0.8: - version "4.0.8" - resolved "https://registry.yarnpkg.com/lodash.debounce/-/lodash.debounce-4.0.8.tgz#82d79bff30a67c4005ffd5e2515300ad9ca4d7af" - integrity sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow== - -lodash.flow@^3.3.0: - version "3.5.0" - resolved "https://registry.yarnpkg.com/lodash.flow/-/lodash.flow-3.5.0.tgz#87bf40292b8cf83e4e8ce1a3ae4209e20071675a" - integrity sha512-ff3BX/tSioo+XojX4MOsOMhJw0nZoUEF011LX8g8d3gvjVbxd89cCio4BCXronjxcTUIJUoqKEUA+n4CqvvRPw== - -lodash.memoize@^4.1.2: - version "4.1.2" - resolved "https://registry.yarnpkg.com/lodash.memoize/-/lodash.memoize-4.1.2.tgz#bcc6c49a42a2840ed997f323eada5ecd182e0bfe" - integrity sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag== - -lodash.uniq@4.5.0, lodash.uniq@^4.5.0: - version "4.5.0" - resolved "https://registry.yarnpkg.com/lodash.uniq/-/lodash.uniq-4.5.0.tgz#d0225373aeb652adc1bc82e4945339a842754773" - integrity sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ== - -lodash@^4.17.19, lodash@^4.17.20, lodash@^4.17.21: - version "4.17.21" - resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.21.tgz#679591c564c3bffaae8454cf0b3df370c3d6911c" - integrity sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg== - -loose-envify@^1.0.0, loose-envify@^1.1.0, loose-envify@^1.2.0, loose-envify@^1.3.1, loose-envify@^1.4.0: - version "1.4.0" - resolved "https://registry.yarnpkg.com/loose-envify/-/loose-envify-1.4.0.tgz#71ee51fa7be4caec1a63839f7e682d8132d30caf" - integrity sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q== - dependencies: - js-tokens "^3.0.0 || ^4.0.0" - -lower-case@^2.0.2: - version "2.0.2" - resolved "https://registry.yarnpkg.com/lower-case/-/lower-case-2.0.2.tgz#6fa237c63dbdc4a82ca0fd882e4722dc5e634e28" - integrity sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg== - dependencies: - tslib "^2.0.3" - -lowercase-keys@^1.0.0, lowercase-keys@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-1.0.1.tgz#6f9e30b47084d971a7c820ff15a6c5167b74c26f" - integrity sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA== - -lowercase-keys@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-2.0.0.tgz#2603e78b7b4b0006cbca2fbcc8a3202558ac9479" - integrity sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA== - -lru-cache@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-5.1.1.tgz#1da27e6710271947695daf6848e847f01d84b920" - integrity sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w== - dependencies: - yallist "^3.0.2" - -lunr-languages@^1.4.0: - version "1.14.0" - resolved "https://registry.yarnpkg.com/lunr-languages/-/lunr-languages-1.14.0.tgz#6e97635f434631729dd0e5654daedd291cd6f2d0" - integrity sha512-hWUAb2KqM3L7J5bcrngszzISY4BxrXn/Xhbb9TTCJYEGqlR1nG67/M14sp09+PTIRklobrn57IAxcdcO/ZFyNA== - -make-dir@^3.0.0, make-dir@^3.0.2, make-dir@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-3.1.0.tgz#415e967046b3a7f1d185277d84aa58203726a13f" - integrity sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw== - dependencies: - semver "^6.0.0" - -mark.js@^8.11.1: - version "8.11.1" - resolved "https://registry.yarnpkg.com/mark.js/-/mark.js-8.11.1.tgz#180f1f9ebef8b0e638e4166ad52db879beb2ffc5" - integrity sha512-1I+1qpDt4idfgLQG+BNWmrqku+7/2bi5nLf4YwF8y8zXvmfiTBY3PV3ZibfrjBueCByROpuBjLLFCajqkgYoLQ== - -markdown-escapes@^1.0.0: - version "1.0.4" - resolved "https://registry.yarnpkg.com/markdown-escapes/-/markdown-escapes-1.0.4.tgz#c95415ef451499d7602b91095f3c8e8975f78535" - integrity sha512-8z4efJYk43E0upd0NbVXwgSTQs6cT3T06etieCMEg7dRbzCbxUCK/GHlX8mhHRDcp+OLlHkPKsvqQTCvsRl2cg== - -mdast-squeeze-paragraphs@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/mdast-squeeze-paragraphs/-/mdast-squeeze-paragraphs-4.0.0.tgz#7c4c114679c3bee27ef10b58e2e015be79f1ef97" - integrity sha512-zxdPn69hkQ1rm4J+2Cs2j6wDEv7O17TfXTJ33tl/+JPIoEmtV9t2ZzBM5LPHE8QlHsmVD8t3vPKCyY3oH+H8MQ== - dependencies: - unist-util-remove "^2.0.0" - -mdast-util-definitions@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/mdast-util-definitions/-/mdast-util-definitions-4.0.0.tgz#c5c1a84db799173b4dcf7643cda999e440c24db2" - integrity sha512-k8AJ6aNnUkB7IE+5azR9h81O5EQ/cTDXtWdMq9Kk5KcEW/8ritU5CeLg/9HhOC++nALHBlaogJ5jz0Ybk3kPMQ== - dependencies: - unist-util-visit "^2.0.0" - -mdast-util-to-hast@10.0.1: - version "10.0.1" - resolved "https://registry.yarnpkg.com/mdast-util-to-hast/-/mdast-util-to-hast-10.0.1.tgz#0cfc82089494c52d46eb0e3edb7a4eb2aea021eb" - integrity sha512-BW3LM9SEMnjf4HXXVApZMt8gLQWVNXc3jryK0nJu/rOXPOnlkUjmdkDlmxMirpbU9ILncGFIwLH/ubnWBbcdgA== - dependencies: - "@types/mdast" "^3.0.0" - "@types/unist" "^2.0.0" - mdast-util-definitions "^4.0.0" - mdurl "^1.0.0" - unist-builder "^2.0.0" - unist-util-generated "^1.0.0" - unist-util-position "^3.0.0" - unist-util-visit "^2.0.0" - -mdast-util-to-string@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/mdast-util-to-string/-/mdast-util-to-string-2.0.0.tgz#b8cfe6a713e1091cb5b728fc48885a4767f8b97b" - integrity sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w== - -mdn-data@2.0.14: - version "2.0.14" - resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.14.tgz#7113fc4281917d63ce29b43446f701e68c25ba50" - integrity sha512-dn6wd0uw5GsdswPFfsgMp5NSB0/aDe6fK94YJV/AJDYXL6HVLWBsxeq7js7Ad+mU2K9LAlwpk6kN2D5mwCPVow== - -mdn-data@2.0.28: - version "2.0.28" - resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.28.tgz#5ec48e7bef120654539069e1ae4ddc81ca490eba" - integrity sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g== - -mdn-data@2.0.30: - version "2.0.30" - resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.30.tgz#ce4df6f80af6cfbe218ecd5c552ba13c4dfa08cc" - integrity sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA== - -mdurl@^1.0.0: - version "1.0.1" - resolved "https://registry.yarnpkg.com/mdurl/-/mdurl-1.0.1.tgz#fe85b2ec75a59037f2adfec100fd6c601761152e" - integrity sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g== - -media-typer@0.3.0: - version "0.3.0" - resolved "https://registry.yarnpkg.com/media-typer/-/media-typer-0.3.0.tgz#8710d7af0aa626f8fffa1ce00168545263255748" - integrity sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ== - -medium-zoom@^1.0.8: - version "1.1.0" - resolved "https://registry.yarnpkg.com/medium-zoom/-/medium-zoom-1.1.0.tgz#6efb6bbda861a02064ee71a2617a8dc4381ecc71" - integrity sha512-ewyDsp7k4InCUp3jRmwHBRFGyjBimKps/AJLjRSox+2q/2H4p/PNpQf+pwONWlJiOudkBXtbdmVbFjqyybfTmQ== - -memfs@^3.1.2, memfs@^3.4.3: - version "3.6.0" - resolved "https://registry.yarnpkg.com/memfs/-/memfs-3.6.0.tgz#d7a2110f86f79dd950a8b6df6d57bc984aa185f6" - integrity sha512-EGowvkkgbMcIChjMTMkESFDbZeSh8xZ7kNSF0hAiAN4Jh6jgHCRS0Ga/+C8y6Au+oqpezRHCfPsmJ2+DwAgiwQ== - dependencies: - fs-monkey "^1.0.4" - -merge-descriptors@1.0.3: - version "1.0.3" - resolved "https://registry.yarnpkg.com/merge-descriptors/-/merge-descriptors-1.0.3.tgz#d80319a65f3c7935351e5cfdac8f9318504dbed5" - integrity sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ== - -merge-stream@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/merge-stream/-/merge-stream-2.0.0.tgz#52823629a14dd00c9770fb6ad47dc6310f2c1f60" - integrity sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w== - -merge2@^1.3.0, merge2@^1.4.1: - version "1.4.1" - resolved "https://registry.yarnpkg.com/merge2/-/merge2-1.4.1.tgz#4368892f885e907455a6fd7dc55c0c9d404990ae" - integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg== - -methods@~1.1.2: - version "1.1.2" - resolved "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz#5529a4d67654134edcc5266656835b0f851afcee" - integrity sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w== - -micromatch@^4.0.2, micromatch@^4.0.4, micromatch@^4.0.5: - version "4.0.8" - resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-4.0.8.tgz#d66fa18f3a47076789320b9b1af32bd86d9fa202" - integrity sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA== - dependencies: - braces "^3.0.3" - picomatch "^2.3.1" - -mime-db@1.52.0: - version "1.52.0" - resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.52.0.tgz#bbabcdc02859f4987301c856e3387ce5ec43bf70" - integrity sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg== - -"mime-db@>= 1.43.0 < 2": - version "1.53.0" - resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.53.0.tgz#3cb63cd820fc29896d9d4e8c32ab4fcd74ccb447" - integrity sha512-oHlN/w+3MQ3rba9rqFr6V/ypF10LSkdwUysQL7GkXoTgIWeV+tcXGA852TBxH+gsh8UWoyhR1hKcoMJTuWflpg== - -mime-db@~1.33.0: - version "1.33.0" - resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.33.0.tgz#a3492050a5cb9b63450541e39d9788d2272783db" - integrity sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ== - -mime-types@2.1.18: - version "2.1.18" - resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.18.tgz#6f323f60a83d11146f831ff11fd66e2fe5503bb8" - integrity sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ== - dependencies: - mime-db "~1.33.0" - -mime-types@^2.1.27, mime-types@^2.1.31, mime-types@~2.1.17, mime-types@~2.1.24, mime-types@~2.1.34: - version "2.1.35" - resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.35.tgz#381a871b62a734450660ae3deee44813f70d959a" - integrity sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw== - dependencies: - mime-db "1.52.0" - -mime@1.6.0: - version "1.6.0" - resolved "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz#32cd9e5c64553bd58d19a568af452acff04981b1" - integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg== - -mimic-fn@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz#7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b" - integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg== - -mimic-response@^1.0.0, mimic-response@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-1.0.1.tgz#4923538878eef42063cb8a3e3b0798781487ab1b" - integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ== - -mimic-response@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-3.1.0.tgz#2d1d59af9c1b129815accc2c46a022a5ce1fa3c9" - integrity sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ== - -mini-css-extract-plugin@^2.6.1: - version "2.9.1" - resolved "https://registry.yarnpkg.com/mini-css-extract-plugin/-/mini-css-extract-plugin-2.9.1.tgz#4d184f12ce90582e983ccef0f6f9db637b4be758" - integrity sha512-+Vyi+GCCOHnrJ2VPS+6aPoXN2k2jgUzDRhTFLjjTBn23qyXJXkjUWQgTL+mXpF5/A8ixLdCc6kWsoeOjKGejKQ== - dependencies: - schema-utils "^4.0.0" - tapable "^2.2.1" - -minimalistic-assert@^1.0.0: - version "1.0.1" - resolved "https://registry.yarnpkg.com/minimalistic-assert/-/minimalistic-assert-1.0.1.tgz#2e194de044626d4a10e7f7fbc00ce73e83e4d5c7" - integrity sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A== - -minimatch@3.1.2, minimatch@^3.0.4, minimatch@^3.0.5, minimatch@^3.1.1: - version "3.1.2" - resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.1.2.tgz#19cd194bfd3e428f049a70817c038d89ab4be35b" - integrity sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw== - dependencies: - brace-expansion "^1.1.7" - -minimist@^1.2.0, minimist@^1.2.3, minimist@^1.2.5: - version "1.2.8" - resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.8.tgz#c1a464e7693302e082a075cee0c057741ac4772c" - integrity sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA== - -mkdirp-classic@^0.5.2, mkdirp-classic@^0.5.3: - version "0.5.3" - resolved "https://registry.yarnpkg.com/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz#fa10c9115cc6d8865be221ba47ee9bed78601113" - integrity sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A== - -mrmime@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/mrmime/-/mrmime-2.0.0.tgz#151082a6e06e59a9a39b46b3e14d5cfe92b3abb4" - integrity sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw== - -ms@2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz#5608aeadfc00be6c2901df5f9861788de0d597c8" - integrity sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A== - -ms@2.1.3, ms@^2.1.3: - version "2.1.3" - resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.3.tgz#574c8138ce1d2b5861f0b44579dbadd60c6615b2" - integrity sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA== - -multicast-dns@^7.2.5: - version "7.2.5" - resolved "https://registry.yarnpkg.com/multicast-dns/-/multicast-dns-7.2.5.tgz#77eb46057f4d7adbd16d9290fa7299f6fa64cced" - integrity sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg== - dependencies: - dns-packet "^5.2.2" - thunky "^1.0.2" - -nanoid@^3.3.7: - version "3.3.7" - resolved "https://registry.yarnpkg.com/nanoid/-/nanoid-3.3.7.tgz#d0c301a691bc8d54efa0a2226ccf3fe2fd656bd8" - integrity sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g== - -napi-build-utils@^1.0.1: - version "1.0.2" - resolved "https://registry.yarnpkg.com/napi-build-utils/-/napi-build-utils-1.0.2.tgz#b1fddc0b2c46e380a0b7a76f984dd47c41a13806" - integrity sha512-ONmRUqK7zj7DWX0D9ADe03wbwOBZxNAfF20PlGfCWQcD3+/MakShIHrMqx9YwPTfxDdF1zLeL+RGZiR9kGMLdg== - -negotiator@0.6.3: - version "0.6.3" - resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.3.tgz#58e323a72fedc0d6f9cd4d31fe49f51479590ccd" - integrity sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg== - -neo-async@^2.6.2: - version "2.6.2" - resolved "https://registry.yarnpkg.com/neo-async/-/neo-async-2.6.2.tgz#b4aafb93e3aeb2d8174ca53cf163ab7d7308305f" - integrity sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw== - -no-case@^3.0.4: - version "3.0.4" - resolved "https://registry.yarnpkg.com/no-case/-/no-case-3.0.4.tgz#d361fd5c9800f558551a8369fc0dcd4662b6124d" - integrity sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg== - dependencies: - lower-case "^2.0.2" - tslib "^2.0.3" - -node-abi@^3.3.0: - version "3.71.0" - resolved "https://registry.yarnpkg.com/node-abi/-/node-abi-3.71.0.tgz#52d84bbcd8575efb71468fbaa1f9a49b2c242038" - integrity sha512-SZ40vRiy/+wRTf21hxkkEjPJZpARzUMVcJoQse2EF8qkUWbbO2z7vd5oA/H6bVH6SZQ5STGcu0KRDS7biNRfxw== - dependencies: - semver "^7.3.5" - -node-addon-api@^5.0.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/node-addon-api/-/node-addon-api-5.1.0.tgz#49da1ca055e109a23d537e9de43c09cca21eb762" - integrity sha512-eh0GgfEkpnoWDq+VY8OyvYhFEzBk6jIYbRKdIlyTiAXIVJ8PyBaKb0rp7oDtoddbdoHWhq8wwr+XZ81F1rpNdA== - -node-emoji@^1.10.0: - version "1.11.0" - resolved "https://registry.yarnpkg.com/node-emoji/-/node-emoji-1.11.0.tgz#69a0150e6946e2f115e9d7ea4df7971e2628301c" - integrity sha512-wo2DpQkQp7Sjm2A0cq+sN7EHKO6Sl0ctXeBdFZrL9T9+UywORbufTcTZxom8YqpLQt/FqNMUkOpkZrJVYSKD3A== - dependencies: - lodash "^4.17.21" - -node-fetch@^2.6.12: - version "2.7.0" - resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.7.0.tgz#d0f0fa6e3e2dc1d27efcd8ad99d550bda94d187d" - integrity sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A== - dependencies: - whatwg-url "^5.0.0" - -node-forge@^1: - version "1.3.1" - resolved "https://registry.yarnpkg.com/node-forge/-/node-forge-1.3.1.tgz#be8da2af243b2417d5f646a770663a92b7e9ded3" - integrity sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA== - -node-releases@^2.0.18: - version "2.0.18" - resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-2.0.18.tgz#f010e8d35e2fe8d6b2944f03f70213ecedc4ca3f" - integrity sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g== - -normalize-path@^3.0.0, normalize-path@~3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz#0dcd69ff23a1c9b11fd0978316644a0388216a65" - integrity sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA== - -normalize-range@^0.1.2: - version "0.1.2" - resolved "https://registry.yarnpkg.com/normalize-range/-/normalize-range-0.1.2.tgz#2d10c06bdfd312ea9777695a4d28439456b75942" - integrity sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA== - -normalize-url@^4.1.0: - version "4.5.1" - resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-4.5.1.tgz#0dd90cf1288ee1d1313b87081c9a5932ee48518a" - integrity sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA== - -normalize-url@^6.0.1: - version "6.1.0" - resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-6.1.0.tgz#40d0885b535deffe3f3147bec877d05fe4c5668a" - integrity sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A== - -npm-run-path@^4.0.1: - version "4.0.1" - resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-4.0.1.tgz#b7ecd1e5ed53da8e37a55e1c2269e0b97ed748ea" - integrity sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw== - dependencies: - path-key "^3.0.0" - -nprogress@^0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/nprogress/-/nprogress-0.2.0.tgz#cb8f34c53213d895723fcbab907e9422adbcafb1" - integrity sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA== - -nth-check@^2.0.1: - version "2.1.1" - resolved "https://registry.yarnpkg.com/nth-check/-/nth-check-2.1.1.tgz#c9eab428effce36cd6b92c924bdb000ef1f1ed1d" - integrity sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w== - dependencies: - boolbase "^1.0.0" - -object-assign@^4.1.0, object-assign@^4.1.1: - version "4.1.1" - resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863" - integrity sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg== - -object-inspect@^1.13.1: - version "1.13.2" - resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.13.2.tgz#dea0088467fb991e67af4058147a24824a3043ff" - integrity sha512-IRZSRuzJiynemAXPYtPe5BoI/RESNYR7TYm50MC5Mqbd3Jmw5y790sErYw3V6SryFJD64b74qQQs9wn5Bg/k3g== - -object-keys@^1.1.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz#1c47f272df277f3b1daf061677d9c82e2322c60e" - integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA== - -object.assign@^4.1.0: - version "4.1.5" - resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.5.tgz#3a833f9ab7fdb80fc9e8d2300c803d216d8fdbb0" - integrity sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ== - dependencies: - call-bind "^1.0.5" - define-properties "^1.2.1" - has-symbols "^1.0.3" - object-keys "^1.1.1" - -obuf@^1.0.0, obuf@^1.1.2: - version "1.1.2" - resolved "https://registry.yarnpkg.com/obuf/-/obuf-1.1.2.tgz#09bea3343d41859ebd446292d11c9d4db619084e" - integrity sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg== - -on-finished@2.4.1: - version "2.4.1" - resolved "https://registry.yarnpkg.com/on-finished/-/on-finished-2.4.1.tgz#58c8c44116e54845ad57f14ab10b03533184ac3f" - integrity sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg== - dependencies: - ee-first "1.1.1" - -on-headers@~1.0.2: - version "1.0.2" - resolved "https://registry.yarnpkg.com/on-headers/-/on-headers-1.0.2.tgz#772b0ae6aaa525c399e489adfad90c403eb3c28f" - integrity sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA== - -once@^1.3.0, once@^1.3.1, once@^1.4.0: - version "1.4.0" - resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1" - integrity sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w== - dependencies: - wrappy "1" - -onetime@^5.1.2: - version "5.1.2" - resolved "https://registry.yarnpkg.com/onetime/-/onetime-5.1.2.tgz#d0e96ebb56b07476df1dd9c4806e5237985ca45e" - integrity sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg== - dependencies: - mimic-fn "^2.1.0" - -open@^8.0.9, open@^8.4.0: - version "8.4.2" - resolved "https://registry.yarnpkg.com/open/-/open-8.4.2.tgz#5b5ffe2a8f793dcd2aad73e550cb87b59cb084f9" - integrity sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ== - dependencies: - define-lazy-prop "^2.0.0" - is-docker "^2.1.1" - is-wsl "^2.2.0" - -opener@^1.5.2: - version "1.5.2" - resolved "https://registry.yarnpkg.com/opener/-/opener-1.5.2.tgz#5d37e1f35077b9dcac4301372271afdeb2a13598" - integrity sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A== - -p-cancelable@^1.0.0: - version "1.1.0" - resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-1.1.0.tgz#d078d15a3af409220c886f1d9a0ca2e441ab26cc" - integrity sha512-s73XxOZ4zpt1edZYZzvhqFa6uvQc1vwUa0K0BdtIZgQMAJj9IbebH+JkgKZc9h+B05PKHLOTl4ajG1BmNrVZlw== - -p-limit@^2.0.0, p-limit@^2.2.0: - version "2.3.0" - resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-2.3.0.tgz#3dd33c647a214fdfffd835933eb086da0dc21db1" - integrity sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w== - dependencies: - p-try "^2.0.0" - -p-limit@^3.0.2: - version "3.1.0" - resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-3.1.0.tgz#e1daccbe78d0d1388ca18c64fea38e3e57e3706b" - integrity sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ== - dependencies: - yocto-queue "^0.1.0" - -p-locate@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-3.0.0.tgz#322d69a05c0264b25997d9f40cd8a891ab0064a4" - integrity sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ== - dependencies: - p-limit "^2.0.0" - -p-locate@^4.1.0: - version "4.1.0" - resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-4.1.0.tgz#a3428bb7088b3a60292f66919278b7c297ad4f07" - integrity sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A== - dependencies: - p-limit "^2.2.0" - -p-locate@^5.0.0: - version "5.0.0" - resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-5.0.0.tgz#83c8315c6785005e3bd021839411c9e110e6d834" - integrity sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw== - dependencies: - p-limit "^3.0.2" - -p-map@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/p-map/-/p-map-4.0.0.tgz#bb2f95a5eda2ec168ec9274e06a747c3e2904d2b" - integrity sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ== - dependencies: - aggregate-error "^3.0.0" - -p-retry@^4.5.0: - version "4.6.2" - resolved "https://registry.yarnpkg.com/p-retry/-/p-retry-4.6.2.tgz#9baae7184057edd4e17231cee04264106e092a16" - integrity sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ== - dependencies: - "@types/retry" "0.12.0" - retry "^0.13.1" - -p-try@^2.0.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/p-try/-/p-try-2.2.0.tgz#cb2868540e313d61de58fafbe35ce9004d5540e6" - integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ== - -package-json@^6.3.0: - version "6.5.0" - resolved "https://registry.yarnpkg.com/package-json/-/package-json-6.5.0.tgz#6feedaca35e75725876d0b0e64974697fed145b0" - integrity sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ== - dependencies: - got "^9.6.0" - registry-auth-token "^4.0.0" - registry-url "^5.0.0" - semver "^6.2.0" - -param-case@^3.0.4: - version "3.0.4" - resolved "https://registry.yarnpkg.com/param-case/-/param-case-3.0.4.tgz#7d17fe4aa12bde34d4a77d91acfb6219caad01c5" - integrity sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A== - dependencies: - dot-case "^3.0.4" - tslib "^2.0.3" - -parent-module@^1.0.0: - version "1.0.1" - resolved "https://registry.yarnpkg.com/parent-module/-/parent-module-1.0.1.tgz#691d2709e78c79fae3a156622452d00762caaaa2" - integrity sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g== - dependencies: - callsites "^3.0.0" - -parse-entities@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/parse-entities/-/parse-entities-2.0.0.tgz#53c6eb5b9314a1f4ec99fa0fdf7ce01ecda0cbe8" - integrity sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ== - dependencies: - character-entities "^1.0.0" - character-entities-legacy "^1.0.0" - character-reference-invalid "^1.0.0" - is-alphanumerical "^1.0.0" - is-decimal "^1.0.0" - is-hexadecimal "^1.0.0" - -parse-json@^5.0.0, parse-json@^5.2.0: - version "5.2.0" - resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-5.2.0.tgz#c76fc66dee54231c962b22bcc8a72cf2f99753cd" - integrity sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg== - dependencies: - "@babel/code-frame" "^7.0.0" - error-ex "^1.3.1" - json-parse-even-better-errors "^2.3.0" - lines-and-columns "^1.1.6" - -parse-numeric-range@^1.3.0: - version "1.3.0" - resolved "https://registry.yarnpkg.com/parse-numeric-range/-/parse-numeric-range-1.3.0.tgz#7c63b61190d61e4d53a1197f0c83c47bb670ffa3" - integrity sha512-twN+njEipszzlMJd4ONUYgSfZPDxgHhT9Ahed5uTigpQn90FggW4SA/AIPq/6a149fTbE9qBEcSwE3FAEp6wQQ== - -parse5-htmlparser2-tree-adapter@^7.0.0: - version "7.1.0" - resolved "https://registry.yarnpkg.com/parse5-htmlparser2-tree-adapter/-/parse5-htmlparser2-tree-adapter-7.1.0.tgz#b5a806548ed893a43e24ccb42fbb78069311e81b" - integrity sha512-ruw5xyKs6lrpo9x9rCZqZZnIUntICjQAd0Wsmp396Ul9lN/h+ifgVV1x1gZHi8euej6wTfpqX8j+BFQxF0NS/g== - dependencies: - domhandler "^5.0.3" - parse5 "^7.0.0" - -parse5-parser-stream@^7.1.2: - version "7.1.2" - resolved "https://registry.yarnpkg.com/parse5-parser-stream/-/parse5-parser-stream-7.1.2.tgz#d7c20eadc37968d272e2c02660fff92dd27e60e1" - integrity sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow== - dependencies: - parse5 "^7.0.0" - -parse5@^6.0.0: - version "6.0.1" - resolved "https://registry.yarnpkg.com/parse5/-/parse5-6.0.1.tgz#e1a1c085c569b3dc08321184f19a39cc27f7c30b" - integrity sha512-Ofn/CTFzRGTTxwpNEs9PP93gXShHcTq255nzRYSKe8AkVpZY7e1fpmTfOyoIvjP5HG7Z2ZM7VS9PPhQGW2pOpw== - -parse5@^7.0.0, parse5@^7.1.2: - version "7.2.0" - resolved "https://registry.yarnpkg.com/parse5/-/parse5-7.2.0.tgz#8a0591ce9b7c5e2027173ab737d4d3fc3d826fab" - integrity sha512-ZkDsAOcxsUMZ4Lz5fVciOehNcJ+Gb8gTzcA4yl3wnc273BAybYWrQ+Ks/OjCjSEpjvQkDSeZbybK9qj2VHHdGA== - dependencies: - entities "^4.5.0" - -parseurl@~1.3.2, parseurl@~1.3.3: - version "1.3.3" - resolved "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.3.tgz#9da19e7bee8d12dff0513ed5b76957793bc2e8d4" - integrity sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ== - -pascal-case@^3.1.2: - version "3.1.2" - resolved "https://registry.yarnpkg.com/pascal-case/-/pascal-case-3.1.2.tgz#b48e0ef2b98e205e7c1dae747d0b1508237660eb" - integrity sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g== - dependencies: - no-case "^3.0.4" - tslib "^2.0.3" - -path-exists@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-3.0.0.tgz#ce0ebeaa5f78cb18925ea7d810d7b59b010fd515" - integrity sha512-bpC7GYwiDYQ4wYLe+FA8lhRjhQCMcQGuSgGGqDkg/QerRWw9CmGRT0iSOVRSZJ29NMLZgIzqaljJ63oaL4NIJQ== - -path-exists@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-4.0.0.tgz#513bdbe2d3b95d7762e8c1137efa195c6c61b5b3" - integrity sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w== - -path-is-absolute@^1.0.0: - version "1.0.1" - resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f" - integrity sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg== - -path-is-inside@1.0.2: - version "1.0.2" - resolved "https://registry.yarnpkg.com/path-is-inside/-/path-is-inside-1.0.2.tgz#365417dede44430d1c11af61027facf074bdfc53" - integrity sha512-DUWJr3+ULp4zXmol/SZkFf3JGsS9/SIv+Y3Rt93/UjPpDpklB5f1er4O3POIbUuUJ3FXgqte2Q7SrU6zAqwk8w== - -path-key@^3.0.0, path-key@^3.1.0: - version "3.1.1" - resolved "https://registry.yarnpkg.com/path-key/-/path-key-3.1.1.tgz#581f6ade658cbba65a0d3380de7753295054f375" - integrity sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q== - -path-parse@^1.0.7: - version "1.0.7" - resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.7.tgz#fbc114b60ca42b30d9daf5858e4bd68bbedb6735" - integrity sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw== - -path-to-regexp@0.1.10: - version "0.1.10" - resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-0.1.10.tgz#67e9108c5c0551b9e5326064387de4763c4d5f8b" - integrity sha512-7lf7qcQidTku0Gu3YDPc8DJ1q7OOucfa/BSsIwjuh56VU7katFvuM8hULfkwB3Fns/rsVF7PwPKVw1sl5KQS9w== - -path-to-regexp@3.3.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-3.3.0.tgz#f7f31d32e8518c2660862b644414b6d5c63a611b" - integrity sha512-qyCH421YQPS2WFDxDjftfc1ZR5WKQzVzqsp4n9M2kQhVOo/ByahFoUNJfl58kOcEGfQ//7weFTDhm+ss8Ecxgw== - -path-to-regexp@^1.7.0: - version "1.9.0" - resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-1.9.0.tgz#5dc0753acbf8521ca2e0f137b4578b917b10cf24" - integrity sha512-xIp7/apCFJuUHdDLWe8O1HIkb0kQrOMb/0u6FXQjemHn/ii5LrIzU6bdECnsiTF/GjZkMEKg1xdiZwNqDYlZ6g== - dependencies: - isarray "0.0.1" - -path-type@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/path-type/-/path-type-4.0.0.tgz#84ed01c0a7ba380afe09d90a8c180dcd9d03043b" - integrity sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw== - -picocolors@^1.0.0, picocolors@^1.0.1, picocolors@^1.1.0: - version "1.1.1" - resolved "https://registry.yarnpkg.com/picocolors/-/picocolors-1.1.1.tgz#3d321af3eab939b083c8f929a1d12cda81c26b6b" - integrity sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA== - -picomatch@^2.0.4, picomatch@^2.2.1, picomatch@^2.2.3, picomatch@^2.3.1: - version "2.3.1" - resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.1.tgz#3ba3833733646d9d3e4995946c1365a67fb07a42" - integrity sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA== - -pkg-dir@^4.1.0: - version "4.2.0" - resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-4.2.0.tgz#f099133df7ede422e81d1d8448270eeb3e4261f3" - integrity sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ== - dependencies: - find-up "^4.0.0" - -pkg-up@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/pkg-up/-/pkg-up-3.1.0.tgz#100ec235cc150e4fd42519412596a28512a0def5" - integrity sha512-nDywThFk1i4BQK4twPQ6TA4RT8bDY96yeuCVBWL3ePARCiEKDRSrNGbFIgUJpLp+XeIR65v8ra7WuJOFUBtkMA== - dependencies: - find-up "^3.0.0" - -"plugin-image-zoom@https://github.com/flexanalytics/plugin-image-zoom.git": - version "1.1.0" - resolved "https://github.com/flexanalytics/plugin-image-zoom.git#8e1b866c79ed6d42cefc4c52f851f1dfd1d0c7de" - dependencies: - medium-zoom "^1.0.8" - -postcss-calc@^8.2.3: - version "8.2.4" - resolved "https://registry.yarnpkg.com/postcss-calc/-/postcss-calc-8.2.4.tgz#77b9c29bfcbe8a07ff6693dc87050828889739a5" - integrity sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q== - dependencies: - postcss-selector-parser "^6.0.9" - postcss-value-parser "^4.2.0" - -postcss-colormin@^5.3.1: - version "5.3.1" - resolved "https://registry.yarnpkg.com/postcss-colormin/-/postcss-colormin-5.3.1.tgz#86c27c26ed6ba00d96c79e08f3ffb418d1d1988f" - integrity sha512-UsWQG0AqTFQmpBegeLLc1+c3jIqBNB0zlDGRWR+dQ3pRKJL1oeMzyqmH3o2PIfn9MBdNrVPWhDbT769LxCTLJQ== - dependencies: - browserslist "^4.21.4" - caniuse-api "^3.0.0" - colord "^2.9.1" - postcss-value-parser "^4.2.0" - -postcss-convert-values@^5.1.3: - version "5.1.3" - resolved "https://registry.yarnpkg.com/postcss-convert-values/-/postcss-convert-values-5.1.3.tgz#04998bb9ba6b65aa31035d669a6af342c5f9d393" - integrity sha512-82pC1xkJZtcJEfiLw6UXnXVXScgtBrjlO5CBmuDQc+dlb88ZYheFsjTn40+zBVi3DkfF7iezO0nJUPLcJK3pvA== - dependencies: - browserslist "^4.21.4" - postcss-value-parser "^4.2.0" - -postcss-discard-comments@^5.1.2: - version "5.1.2" - resolved "https://registry.yarnpkg.com/postcss-discard-comments/-/postcss-discard-comments-5.1.2.tgz#8df5e81d2925af2780075840c1526f0660e53696" - integrity sha512-+L8208OVbHVF2UQf1iDmRcbdjJkuBF6IS29yBDSiWUIzpYaAhtNl6JYnYm12FnkeCwQqF5LeklOu6rAqgfBZqQ== - -postcss-discard-duplicates@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-discard-duplicates/-/postcss-discard-duplicates-5.1.0.tgz#9eb4fe8456706a4eebd6d3b7b777d07bad03e848" - integrity sha512-zmX3IoSI2aoenxHV6C7plngHWWhUOV3sP1T8y2ifzxzbtnuhk1EdPwm0S1bIUNaJ2eNbWeGLEwzw8huPD67aQw== - -postcss-discard-empty@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-discard-empty/-/postcss-discard-empty-5.1.1.tgz#e57762343ff7f503fe53fca553d18d7f0c369c6c" - integrity sha512-zPz4WljiSuLWsI0ir4Mcnr4qQQ5e1Ukc3i7UfE2XcrwKK2LIPIqE5jxMRxO6GbI3cv//ztXDsXwEWT3BHOGh3A== - -postcss-discard-overridden@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-discard-overridden/-/postcss-discard-overridden-5.1.0.tgz#7e8c5b53325747e9d90131bb88635282fb4a276e" - integrity sha512-21nOL7RqWR1kasIVdKs8HNqQJhFxLsyRfAnUDm4Fe4t4mCWL9OJiHvlHPjcd8zc5Myu89b/7wZDnOSjFgeWRtw== - -postcss-discard-unused@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-discard-unused/-/postcss-discard-unused-5.1.0.tgz#8974e9b143d887677304e558c1166d3762501142" - integrity sha512-KwLWymI9hbwXmJa0dkrzpRbSJEh0vVUd7r8t0yOGPcfKzyJJxFM8kLyC5Ev9avji6nY95pOp1W6HqIrfT+0VGw== - dependencies: - postcss-selector-parser "^6.0.5" - -postcss-loader@^7.0.0: - version "7.3.4" - resolved "https://registry.yarnpkg.com/postcss-loader/-/postcss-loader-7.3.4.tgz#aed9b79ce4ed7e9e89e56199d25ad1ec8f606209" - integrity sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A== - dependencies: - cosmiconfig "^8.3.5" - jiti "^1.20.0" - semver "^7.5.4" - -postcss-merge-idents@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-merge-idents/-/postcss-merge-idents-5.1.1.tgz#7753817c2e0b75d0853b56f78a89771e15ca04a1" - integrity sha512-pCijL1TREiCoog5nQp7wUe+TUonA2tC2sQ54UGeMmryK3UFGIYKqDyjnqd6RcuI4znFn9hWSLNN8xKE/vWcUQw== - dependencies: - cssnano-utils "^3.1.0" - postcss-value-parser "^4.2.0" - -postcss-merge-longhand@^5.1.7: - version "5.1.7" - resolved "https://registry.yarnpkg.com/postcss-merge-longhand/-/postcss-merge-longhand-5.1.7.tgz#24a1bdf402d9ef0e70f568f39bdc0344d568fb16" - integrity sha512-YCI9gZB+PLNskrK0BB3/2OzPnGhPkBEwmwhfYk1ilBHYVAZB7/tkTHFBAnCrvBBOmeYyMYw3DMjT55SyxMBzjQ== - dependencies: - postcss-value-parser "^4.2.0" - stylehacks "^5.1.1" - -postcss-merge-rules@^5.1.4: - version "5.1.4" - resolved "https://registry.yarnpkg.com/postcss-merge-rules/-/postcss-merge-rules-5.1.4.tgz#2f26fa5cacb75b1402e213789f6766ae5e40313c" - integrity sha512-0R2IuYpgU93y9lhVbO/OylTtKMVcHb67zjWIfCiKR9rWL3GUk1677LAqD/BcHizukdZEjT8Ru3oHRoAYoJy44g== - dependencies: - browserslist "^4.21.4" - caniuse-api "^3.0.0" - cssnano-utils "^3.1.0" - postcss-selector-parser "^6.0.5" - -postcss-minify-font-values@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-minify-font-values/-/postcss-minify-font-values-5.1.0.tgz#f1df0014a726083d260d3bd85d7385fb89d1f01b" - integrity sha512-el3mYTgx13ZAPPirSVsHqFzl+BBBDrXvbySvPGFnQcTI4iNslrPaFq4muTkLZmKlGk4gyFAYUBMH30+HurREyA== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-minify-gradients@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-minify-gradients/-/postcss-minify-gradients-5.1.1.tgz#f1fe1b4f498134a5068240c2f25d46fcd236ba2c" - integrity sha512-VGvXMTpCEo4qHTNSa9A0a3D+dxGFZCYwR6Jokk+/3oB6flu2/PnPXAh2x7x52EkY5xlIHLm+Le8tJxe/7TNhzw== - dependencies: - colord "^2.9.1" - cssnano-utils "^3.1.0" - postcss-value-parser "^4.2.0" - -postcss-minify-params@^5.1.4: - version "5.1.4" - resolved "https://registry.yarnpkg.com/postcss-minify-params/-/postcss-minify-params-5.1.4.tgz#c06a6c787128b3208b38c9364cfc40c8aa5d7352" - integrity sha512-+mePA3MgdmVmv6g+30rn57USjOGSAyuxUmkfiWpzalZ8aiBkdPYjXWtHuwJGm1v5Ojy0Z0LaSYhHaLJQB0P8Jw== - dependencies: - browserslist "^4.21.4" - cssnano-utils "^3.1.0" - postcss-value-parser "^4.2.0" - -postcss-minify-selectors@^5.2.1: - version "5.2.1" - resolved "https://registry.yarnpkg.com/postcss-minify-selectors/-/postcss-minify-selectors-5.2.1.tgz#d4e7e6b46147b8117ea9325a915a801d5fe656c6" - integrity sha512-nPJu7OjZJTsVUmPdm2TcaiohIwxP+v8ha9NehQ2ye9szv4orirRU3SDdtUmKH+10nzn0bAyOXZ0UEr7OpvLehg== - dependencies: - postcss-selector-parser "^6.0.5" - -postcss-modules-extract-imports@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/postcss-modules-extract-imports/-/postcss-modules-extract-imports-3.1.0.tgz#b4497cb85a9c0c4b5aabeb759bb25e8d89f15002" - integrity sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q== - -postcss-modules-local-by-default@^4.0.5: - version "4.0.5" - resolved "https://registry.yarnpkg.com/postcss-modules-local-by-default/-/postcss-modules-local-by-default-4.0.5.tgz#f1b9bd757a8edf4d8556e8d0f4f894260e3df78f" - integrity sha512-6MieY7sIfTK0hYfafw1OMEG+2bg8Q1ocHCpoWLqOKj3JXlKu4G7btkmM/B7lFubYkYWmRSPLZi5chid63ZaZYw== - dependencies: - icss-utils "^5.0.0" - postcss-selector-parser "^6.0.2" - postcss-value-parser "^4.1.0" - -postcss-modules-scope@^3.2.0: - version "3.2.0" - resolved "https://registry.yarnpkg.com/postcss-modules-scope/-/postcss-modules-scope-3.2.0.tgz#a43d28289a169ce2c15c00c4e64c0858e43457d5" - integrity sha512-oq+g1ssrsZOsx9M96c5w8laRmvEu9C3adDSjI8oTcbfkrTE8hx/zfyobUoWIxaKPO8bt6S62kxpw5GqypEw1QQ== - dependencies: - postcss-selector-parser "^6.0.4" - -postcss-modules-values@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/postcss-modules-values/-/postcss-modules-values-4.0.0.tgz#d7c5e7e68c3bb3c9b27cbf48ca0bb3ffb4602c9c" - integrity sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ== - dependencies: - icss-utils "^5.0.0" - -postcss-normalize-charset@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-normalize-charset/-/postcss-normalize-charset-5.1.0.tgz#9302de0b29094b52c259e9b2cf8dc0879879f0ed" - integrity sha512-mSgUJ+pd/ldRGVx26p2wz9dNZ7ji6Pn8VWBajMXFf8jk7vUoSrZ2lt/wZR7DtlZYKesmZI680qjr2CeFF2fbUg== - -postcss-normalize-display-values@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-normalize-display-values/-/postcss-normalize-display-values-5.1.0.tgz#72abbae58081960e9edd7200fcf21ab8325c3da8" - integrity sha512-WP4KIM4o2dazQXWmFaqMmcvsKmhdINFblgSeRgn8BJ6vxaMyaJkwAzpPpuvSIoG/rmX3M+IrRZEz2H0glrQNEA== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-normalize-positions@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-normalize-positions/-/postcss-normalize-positions-5.1.1.tgz#ef97279d894087b59325b45c47f1e863daefbb92" - integrity sha512-6UpCb0G4eofTCQLFVuI3EVNZzBNPiIKcA1AKVka+31fTVySphr3VUgAIULBhxZkKgwLImhzMR2Bw1ORK+37INg== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-normalize-repeat-style@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-normalize-repeat-style/-/postcss-normalize-repeat-style-5.1.1.tgz#e9eb96805204f4766df66fd09ed2e13545420fb2" - integrity sha512-mFpLspGWkQtBcWIRFLmewo8aC3ImN2i/J3v8YCFUwDnPu3Xz4rLohDO26lGjwNsQxB3YF0KKRwspGzE2JEuS0g== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-normalize-string@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-normalize-string/-/postcss-normalize-string-5.1.0.tgz#411961169e07308c82c1f8c55f3e8a337757e228" - integrity sha512-oYiIJOf4T9T1N4i+abeIc7Vgm/xPCGih4bZz5Nm0/ARVJ7K6xrDlLwvwqOydvyL3RHNf8qZk6vo3aatiw/go3w== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-normalize-timing-functions@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-normalize-timing-functions/-/postcss-normalize-timing-functions-5.1.0.tgz#d5614410f8f0b2388e9f240aa6011ba6f52dafbb" - integrity sha512-DOEkzJ4SAXv5xkHl0Wa9cZLF3WCBhF3o1SKVxKQAa+0pYKlueTpCgvkFAHfk+Y64ezX9+nITGrDZeVGgITJXjg== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-normalize-unicode@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-normalize-unicode/-/postcss-normalize-unicode-5.1.1.tgz#f67297fca3fea7f17e0d2caa40769afc487aa030" - integrity sha512-qnCL5jzkNUmKVhZoENp1mJiGNPcsJCs1aaRmURmeJGES23Z/ajaln+EPTD+rBeNkSryI+2WTdW+lwcVdOikrpA== - dependencies: - browserslist "^4.21.4" - postcss-value-parser "^4.2.0" - -postcss-normalize-url@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-normalize-url/-/postcss-normalize-url-5.1.0.tgz#ed9d88ca82e21abef99f743457d3729a042adcdc" - integrity sha512-5upGeDO+PVthOxSmds43ZeMeZfKH+/DKgGRD7TElkkyS46JXAUhMzIKiCa7BabPeIy3AQcTkXwVVN7DbqsiCew== - dependencies: - normalize-url "^6.0.1" - postcss-value-parser "^4.2.0" - -postcss-normalize-whitespace@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-normalize-whitespace/-/postcss-normalize-whitespace-5.1.1.tgz#08a1a0d1ffa17a7cc6efe1e6c9da969cc4493cfa" - integrity sha512-83ZJ4t3NUDETIHTa3uEg6asWjSBYL5EdkVB0sDncx9ERzOKBVJIUeDO9RyA9Zwtig8El1d79HBp0JEi8wvGQnA== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-ordered-values@^5.1.3: - version "5.1.3" - resolved "https://registry.yarnpkg.com/postcss-ordered-values/-/postcss-ordered-values-5.1.3.tgz#b6fd2bd10f937b23d86bc829c69e7732ce76ea38" - integrity sha512-9UO79VUhPwEkzbb3RNpqqghc6lcYej1aveQteWY+4POIwlqkYE21HKWaLDF6lWNuqCobEAyTovVhtI32Rbv2RQ== - dependencies: - cssnano-utils "^3.1.0" - postcss-value-parser "^4.2.0" - -postcss-reduce-idents@^5.2.0: - version "5.2.0" - resolved "https://registry.yarnpkg.com/postcss-reduce-idents/-/postcss-reduce-idents-5.2.0.tgz#c89c11336c432ac4b28792f24778859a67dfba95" - integrity sha512-BTrLjICoSB6gxbc58D5mdBK8OhXRDqud/zodYfdSi52qvDHdMwk+9kB9xsM8yJThH/sZU5A6QVSmMmaN001gIg== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-reduce-initial@^5.1.2: - version "5.1.2" - resolved "https://registry.yarnpkg.com/postcss-reduce-initial/-/postcss-reduce-initial-5.1.2.tgz#798cd77b3e033eae7105c18c9d371d989e1382d6" - integrity sha512-dE/y2XRaqAi6OvjzD22pjTUQ8eOfc6m/natGHgKFBK9DxFmIm69YmaRVQrGgFlEfc1HePIurY0TmDeROK05rIg== - dependencies: - browserslist "^4.21.4" - caniuse-api "^3.0.0" - -postcss-reduce-transforms@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-reduce-transforms/-/postcss-reduce-transforms-5.1.0.tgz#333b70e7758b802f3dd0ddfe98bb1ccfef96b6e9" - integrity sha512-2fbdbmgir5AvpW9RLtdONx1QoYG2/EtqpNQbFASDlixBbAYuTcJ0dECwlqNqH7VbaUnEnh8SrxOe2sRIn24XyQ== - dependencies: - postcss-value-parser "^4.2.0" - -postcss-selector-parser@^6.0.2, postcss-selector-parser@^6.0.4, postcss-selector-parser@^6.0.5, postcss-selector-parser@^6.0.9: - version "6.1.2" - resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz#27ecb41fb0e3b6ba7a1ec84fff347f734c7929de" - integrity sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg== - dependencies: - cssesc "^3.0.0" - util-deprecate "^1.0.2" - -postcss-sort-media-queries@^4.2.1: - version "4.4.1" - resolved "https://registry.yarnpkg.com/postcss-sort-media-queries/-/postcss-sort-media-queries-4.4.1.tgz#04a5a78db3921eb78f28a1a781a2e68e65258128" - integrity sha512-QDESFzDDGKgpiIh4GYXsSy6sek2yAwQx1JASl5AxBtU1Lq2JfKBljIPNdil989NcSKRQX1ToiaKphImtBuhXWw== - dependencies: - sort-css-media-queries "2.1.0" - -postcss-svgo@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-svgo/-/postcss-svgo-5.1.0.tgz#0a317400ced789f233a28826e77523f15857d80d" - integrity sha512-D75KsH1zm5ZrHyxPakAxJWtkyXew5qwS70v56exwvw542d9CRtTo78K0WeFxZB4G7JXKKMbEZtZayTGdIky/eA== - dependencies: - postcss-value-parser "^4.2.0" - svgo "^2.7.0" - -postcss-unique-selectors@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/postcss-unique-selectors/-/postcss-unique-selectors-5.1.1.tgz#a9f273d1eacd09e9aa6088f4b0507b18b1b541b6" - integrity sha512-5JiODlELrz8L2HwxfPnhOWZYWDxVHWL83ufOv84NrcgipI7TaeRsatAhK4Tr2/ZiYldpK/wBvw5BD3qfaK96GA== - dependencies: - postcss-selector-parser "^6.0.5" - -postcss-value-parser@^4.1.0, postcss-value-parser@^4.2.0: - version "4.2.0" - resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz#723c09920836ba6d3e5af019f92bc0971c02e514" - integrity sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ== - -postcss-zindex@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/postcss-zindex/-/postcss-zindex-5.1.0.tgz#4a5c7e5ff1050bd4c01d95b1847dfdcc58a496ff" - integrity sha512-fgFMf0OtVSBR1va1JNHYgMxYk73yhn/qb4uQDq1DLGYolz8gHCyr/sesEuGUaYs58E3ZJRcpoGuPVoB7Meiq9A== - -postcss@^8.3.11, postcss@^8.4.14, postcss@^8.4.17, postcss@^8.4.33: - version "8.4.47" - resolved "https://registry.yarnpkg.com/postcss/-/postcss-8.4.47.tgz#5bf6c9a010f3e724c503bf03ef7947dcb0fea365" - integrity sha512-56rxCq7G/XfB4EkXq9Egn5GCqugWvDFjafDOThIdMBsI15iqPqR5r15TfSr1YPYeEI19YeaXMCbY6u88Y76GLQ== - dependencies: - nanoid "^3.3.7" - picocolors "^1.1.0" - source-map-js "^1.2.1" - -preact@^10.13.2: - version "10.24.3" - resolved "https://registry.yarnpkg.com/preact/-/preact-10.24.3.tgz#086386bd47071e3b45410ef20844c21e23828f64" - integrity sha512-Z2dPnBnMUfyQfSQ+GBdsGa16hz35YmLmtTLhM169uW944hYL6xzTYkJjC07j+Wosz733pMWx0fgON3JNw1jJQA== - -prebuild-install@^7.1.1: - version "7.1.2" - resolved "https://registry.yarnpkg.com/prebuild-install/-/prebuild-install-7.1.2.tgz#a5fd9986f5a6251fbc47e1e5c65de71e68c0a056" - integrity sha512-UnNke3IQb6sgarcZIDU3gbMeTp/9SSU1DAIkil7PrqG1vZlBtY5msYccSKSHDqa3hNg436IXK+SNImReuA1wEQ== - dependencies: - detect-libc "^2.0.0" - expand-template "^2.0.3" - github-from-package "0.0.0" - minimist "^1.2.3" - mkdirp-classic "^0.5.3" - napi-build-utils "^1.0.1" - node-abi "^3.3.0" - pump "^3.0.0" - rc "^1.2.7" - simple-get "^4.0.0" - tar-fs "^2.0.0" - tunnel-agent "^0.6.0" - -prepend-http@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/prepend-http/-/prepend-http-2.0.0.tgz#e92434bfa5ea8c19f41cdfd401d741a3c819d897" - integrity sha512-ravE6m9Atw9Z/jjttRUZ+clIXogdghyZAuWJ3qEzjT+jI/dL1ifAqhZeC5VHzQp1MSt1+jxKkFNemj/iO7tVUA== - -pretty-error@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/pretty-error/-/pretty-error-4.0.0.tgz#90a703f46dd7234adb46d0f84823e9d1cb8f10d6" - integrity sha512-AoJ5YMAcXKYxKhuJGdcvse+Voc6v1RgnsR3nWcYU7q4t6z0Q6T86sv5Zq8VIRbOWWFpvdGE83LtdSMNd+6Y0xw== - dependencies: - lodash "^4.17.20" - renderkid "^3.0.0" - -pretty-time@^1.1.0: - version "1.1.0" - resolved "https://registry.yarnpkg.com/pretty-time/-/pretty-time-1.1.0.tgz#ffb7429afabb8535c346a34e41873adf3d74dd0e" - integrity sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA== - -prism-react-renderer@^1.3.5: - version "1.3.5" - resolved "https://registry.yarnpkg.com/prism-react-renderer/-/prism-react-renderer-1.3.5.tgz#786bb69aa6f73c32ba1ee813fbe17a0115435085" - integrity sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg== - -prismjs@^1.28.0: - version "1.29.0" - resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.29.0.tgz#f113555a8fa9b57c35e637bba27509dcf802dd12" - integrity sha512-Kx/1w86q/epKcmte75LNrEoT+lX8pBpavuAbvJWRXar7Hz8jrtF+e3vY751p0R8H9HdArwaCTNDDzHg/ScJK1Q== - -process-nextick-args@~2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz#7820d9b16120cc55ca9ae7792680ae7dba6d7fe2" - integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag== - -promise@^7.1.1: - version "7.3.1" - resolved "https://registry.yarnpkg.com/promise/-/promise-7.3.1.tgz#064b72602b18f90f29192b8b1bc418ffd1ebd3bf" - integrity sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg== - dependencies: - asap "~2.0.3" - -prompts@^2.4.2: - version "2.4.2" - resolved "https://registry.yarnpkg.com/prompts/-/prompts-2.4.2.tgz#7b57e73b3a48029ad10ebd44f74b01722a4cb069" - integrity sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q== - dependencies: - kleur "^3.0.3" - sisteransi "^1.0.5" - -prop-types@^15.0.0, prop-types@^15.6.2, prop-types@^15.7.2: - version "15.8.1" - resolved "https://registry.yarnpkg.com/prop-types/-/prop-types-15.8.1.tgz#67d87bf1a694f48435cf332c24af10214a3140b5" - integrity sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg== - dependencies: - loose-envify "^1.4.0" - object-assign "^4.1.1" - react-is "^16.13.1" - -property-information@^5.0.0, property-information@^5.3.0: - version "5.6.0" - resolved "https://registry.yarnpkg.com/property-information/-/property-information-5.6.0.tgz#61675545fb23002f245c6540ec46077d4da3ed69" - integrity sha512-YUHSPk+A30YPv+0Qf8i9Mbfe/C0hdPXk1s1jPVToV8pk8BQtpw10ct89Eo7OWkutrwqvT0eicAxlOg3dOAu8JA== - dependencies: - xtend "^4.0.0" - -proxy-addr@~2.0.7: - version "2.0.7" - resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.7.tgz#f19fe69ceab311eeb94b42e70e8c2070f9ba1025" - integrity sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg== - dependencies: - forwarded "0.2.0" - ipaddr.js "1.9.1" - -pump@^3.0.0: - version "3.0.2" - resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.2.tgz#836f3edd6bc2ee599256c924ffe0d88573ddcbf8" - integrity sha512-tUPXtzlGM8FE3P0ZL6DVs/3P58k9nk8/jZeQCurTJylQA8qFYzHFfhBJkuqyE0FifOsQ0uKWekiZ5g8wtr28cw== - dependencies: - end-of-stream "^1.1.0" - once "^1.3.1" - -punycode@^2.1.0: - version "2.3.1" - resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.3.1.tgz#027422e2faec0b25e1549c3e1bd8309b9133b6e5" - integrity sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg== - -pupa@^2.1.1: - version "2.1.1" - resolved "https://registry.yarnpkg.com/pupa/-/pupa-2.1.1.tgz#f5e8fd4afc2c5d97828faa523549ed8744a20d62" - integrity sha512-l1jNAspIBSFqbT+y+5FosojNpVpF94nlI+wDUpqP9enwOTfHx9f0gh5nB96vl+6yTpsJsypeNrwfzPrKuHB41A== - dependencies: - escape-goat "^2.0.0" - -pure-color@^1.2.0: - version "1.3.0" - resolved "https://registry.yarnpkg.com/pure-color/-/pure-color-1.3.0.tgz#1fe064fb0ac851f0de61320a8bf796836422f33e" - integrity sha512-QFADYnsVoBMw1srW7OVKEYjG+MbIa49s54w1MA1EDY6r2r/sTcKKYqRX1f4GYvnXP7eN/Pe9HFcX+hwzmrXRHA== - -qs@6.13.0: - version "6.13.0" - resolved "https://registry.yarnpkg.com/qs/-/qs-6.13.0.tgz#6ca3bd58439f7e245655798997787b0d88a51906" - integrity sha512-+38qI9SOr8tfZ4QmJNplMUxqjbe7LKvvZgWdExBOmd+egZTtjLB67Gu0HRX3u/XOq7UU2Nx6nsjvS16Z9uwfpg== - dependencies: - side-channel "^1.0.6" - -queue-microtask@^1.2.2: - version "1.2.3" - resolved "https://registry.yarnpkg.com/queue-microtask/-/queue-microtask-1.2.3.tgz#4929228bbc724dfac43e0efb058caf7b6cfb6243" - integrity sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A== - -queue@6.0.2: - version "6.0.2" - resolved "https://registry.yarnpkg.com/queue/-/queue-6.0.2.tgz#b91525283e2315c7553d2efa18d83e76432fed65" - integrity sha512-iHZWu+q3IdFZFX36ro/lKBkSvfkztY5Y7HMiPlOUjhupPcG2JMfst2KKEpu5XndviX/3UhFbRngUPNKtgvtZiA== - dependencies: - inherits "~2.0.3" - -randombytes@^2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/randombytes/-/randombytes-2.1.0.tgz#df6f84372f0270dc65cdf6291349ab7a473d4f2a" - integrity sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ== - dependencies: - safe-buffer "^5.1.0" - -range-parser@1.2.0: - version "1.2.0" - resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.0.tgz#f49be6b487894ddc40dcc94a322f611092e00d5e" - integrity sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A== - -range-parser@^1.2.1, range-parser@~1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.1.tgz#3cf37023d199e1c24d1a55b84800c2f3e6468031" - integrity sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg== - -raw-body@2.5.2: - version "2.5.2" - resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.5.2.tgz#99febd83b90e08975087e8f1f9419a149366b68a" - integrity sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA== - dependencies: - bytes "3.1.2" - http-errors "2.0.0" - iconv-lite "0.4.24" - unpipe "1.0.0" - -rc@1.2.8, rc@^1.2.7, rc@^1.2.8: - version "1.2.8" - resolved "https://registry.yarnpkg.com/rc/-/rc-1.2.8.tgz#cd924bf5200a075b83c188cd6b9e211b7fc0d3ed" - integrity sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw== - dependencies: - deep-extend "^0.6.0" - ini "~1.3.0" - minimist "^1.2.0" - strip-json-comments "~2.0.1" - -react-base16-styling@^0.6.0: - version "0.6.0" - resolved "https://registry.yarnpkg.com/react-base16-styling/-/react-base16-styling-0.6.0.tgz#ef2156d66cf4139695c8a167886cb69ea660792c" - integrity sha512-yvh/7CArceR/jNATXOKDlvTnPKPmGZz7zsenQ3jUwLzHkNUR0CvY3yGYJbWJ/nnxsL8Sgmt5cO3/SILVuPO6TQ== - dependencies: - base16 "^1.0.0" - lodash.curry "^4.0.1" - lodash.flow "^3.3.0" - pure-color "^1.2.0" - -react-dev-utils@^12.0.1: - version "12.0.1" - resolved "https://registry.yarnpkg.com/react-dev-utils/-/react-dev-utils-12.0.1.tgz#ba92edb4a1f379bd46ccd6bcd4e7bc398df33e73" - integrity sha512-84Ivxmr17KjUupyqzFode6xKhjwuEJDROWKJy/BthkL7Wn6NJ8h4WE6k/exAv6ImS+0oZLRRW5j/aINMHyeGeQ== - dependencies: - "@babel/code-frame" "^7.16.0" - address "^1.1.2" - browserslist "^4.18.1" - chalk "^4.1.2" - cross-spawn "^7.0.3" - detect-port-alt "^1.1.6" - escape-string-regexp "^4.0.0" - filesize "^8.0.6" - find-up "^5.0.0" - fork-ts-checker-webpack-plugin "^6.5.0" - global-modules "^2.0.0" - globby "^11.0.4" - gzip-size "^6.0.0" - immer "^9.0.7" - is-root "^2.1.0" - loader-utils "^3.2.0" - open "^8.4.0" - pkg-up "^3.1.0" - prompts "^2.4.2" - react-error-overlay "^6.0.11" - recursive-readdir "^2.2.2" - shell-quote "^1.7.3" - strip-ansi "^6.0.1" - text-table "^0.2.0" - -react-dom@^17.0.2: - version "17.0.2" - resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-17.0.2.tgz#ecffb6845e3ad8dbfcdc498f0d0a939736502c23" - integrity sha512-s4h96KtLDUQlsENhMn1ar8t2bEa+q/YAtj8pPPdIjPDGBDIVNsrD9aXNWqspUe6AzKCIG0C1HZZLqLV7qpOBGA== - dependencies: - loose-envify "^1.1.0" - object-assign "^4.1.1" - scheduler "^0.20.2" - -react-error-overlay@^6.0.11: - version "6.0.11" - resolved "https://registry.yarnpkg.com/react-error-overlay/-/react-error-overlay-6.0.11.tgz#92835de5841c5cf08ba00ddd2d677b6d17ff9adb" - integrity sha512-/6UZ2qgEyH2aqzYZgQPxEnz33NJ2gNsnHA2o5+o4wW9bLM/JYQitNP9xPhsXwC08hMMovfGe/8retsdDsczPRg== - -react-fast-compare@^3.2.0, react-fast-compare@^3.2.2: - version "3.2.2" - resolved "https://registry.yarnpkg.com/react-fast-compare/-/react-fast-compare-3.2.2.tgz#929a97a532304ce9fee4bcae44234f1ce2c21d49" - integrity sha512-nsO+KSNgo1SbJqJEYRE9ERzo7YtYbou/OqjSQKxV7jcKox7+usiUVZOAC+XnDOABXggQTno0Y1CpVnuWEc1boQ== - -react-helmet-async@*: - version "2.0.5" - resolved "https://registry.yarnpkg.com/react-helmet-async/-/react-helmet-async-2.0.5.tgz#cfc70cd7bb32df7883a8ed55502a1513747223ec" - integrity sha512-rYUYHeus+i27MvFE+Jaa4WsyBKGkL6qVgbJvSBoX8mbsWoABJXdEO0bZyi0F6i+4f0NuIb8AvqPMj3iXFHkMwg== - dependencies: - invariant "^2.2.4" - react-fast-compare "^3.2.2" - shallowequal "^1.1.0" - -react-helmet-async@^1.3.0: - version "1.3.0" - resolved "https://registry.yarnpkg.com/react-helmet-async/-/react-helmet-async-1.3.0.tgz#7bd5bf8c5c69ea9f02f6083f14ce33ef545c222e" - integrity sha512-9jZ57/dAn9t3q6hneQS0wukqC2ENOBgMNVEhb/ZG9ZSxUetzVIw4iAmEU38IaVg3QGYauQPhSeUTuIUtFglWpg== - dependencies: - "@babel/runtime" "^7.12.5" - invariant "^2.2.4" - prop-types "^15.7.2" - react-fast-compare "^3.2.0" - shallowequal "^1.1.0" - -react-is@^16.13.1, react-is@^16.6.0, react-is@^16.7.0: - version "16.13.1" - resolved "https://registry.yarnpkg.com/react-is/-/react-is-16.13.1.tgz#789729a4dc36de2999dc156dd6c1d9c18cea56a4" - integrity sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ== - -"react-is@^17.0.1 || ^18.0.0": - version "18.3.1" - resolved "https://registry.yarnpkg.com/react-is/-/react-is-18.3.1.tgz#e83557dc12eae63a99e003a46388b1dcbb44db7e" - integrity sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg== - -react-json-view@^1.21.3: - version "1.21.3" - resolved "https://registry.yarnpkg.com/react-json-view/-/react-json-view-1.21.3.tgz#f184209ee8f1bf374fb0c41b0813cff54549c475" - integrity sha512-13p8IREj9/x/Ye4WI/JpjhoIwuzEgUAtgJZNBJckfzJt1qyh24BdTm6UQNGnyTq9dapQdrqvquZTo3dz1X6Cjw== - dependencies: - flux "^4.0.1" - react-base16-styling "^0.6.0" - react-lifecycles-compat "^3.0.4" - react-textarea-autosize "^8.3.2" - -react-lifecycles-compat@^3.0.4: - version "3.0.4" - resolved "https://registry.yarnpkg.com/react-lifecycles-compat/-/react-lifecycles-compat-3.0.4.tgz#4f1a273afdfc8f3488a8c516bfda78f872352362" - integrity sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA== - -react-loadable-ssr-addon-v5-slorber@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/react-loadable-ssr-addon-v5-slorber/-/react-loadable-ssr-addon-v5-slorber-1.0.1.tgz#2cdc91e8a744ffdf9e3556caabeb6e4278689883" - integrity sha512-lq3Lyw1lGku8zUEJPDxsNm1AfYHBrO9Y1+olAYwpUJ2IGFBskM0DMKok97A6LWUpHm+o7IvQBOWu9MLenp9Z+A== - dependencies: - "@babel/runtime" "^7.10.3" - -react-router-config@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/react-router-config/-/react-router-config-5.1.1.tgz#0f4263d1a80c6b2dc7b9c1902c9526478194a988" - integrity sha512-DuanZjaD8mQp1ppHjgnnUnyOlqYXZVjnov/JzFhjLEwd3Z4dYjMSnqrEzzGThH47vpCOqPPwJM2FtthLeJ8Pbg== - dependencies: - "@babel/runtime" "^7.1.2" - -react-router-dom@^5.3.3: - version "5.3.4" - resolved "https://registry.yarnpkg.com/react-router-dom/-/react-router-dom-5.3.4.tgz#2ed62ffd88cae6db134445f4a0c0ae8b91d2e5e6" - integrity sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ== - dependencies: - "@babel/runtime" "^7.12.13" - history "^4.9.0" - loose-envify "^1.3.1" - prop-types "^15.6.2" - react-router "5.3.4" - tiny-invariant "^1.0.2" - tiny-warning "^1.0.0" - -react-router@5.3.4, react-router@^5.3.3: - version "5.3.4" - resolved "https://registry.yarnpkg.com/react-router/-/react-router-5.3.4.tgz#8ca252d70fcc37841e31473c7a151cf777887bb5" - integrity sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA== - dependencies: - "@babel/runtime" "^7.12.13" - history "^4.9.0" - hoist-non-react-statics "^3.1.0" - loose-envify "^1.3.1" - path-to-regexp "^1.7.0" - prop-types "^15.6.2" - react-is "^16.6.0" - tiny-invariant "^1.0.2" - tiny-warning "^1.0.0" - -react-textarea-autosize@^8.3.2: - version "8.5.4" - resolved "https://registry.yarnpkg.com/react-textarea-autosize/-/react-textarea-autosize-8.5.4.tgz#1c568ad838857b6ce86ee2a96e504179305e0bf4" - integrity sha512-eSSjVtRLcLfFwFcariT77t9hcbVJHQV76b51QjQGarQIHml2+gM2lms0n3XrhnDmgK5B+/Z7TmQk5OHNzqYm/A== - dependencies: - "@babel/runtime" "^7.20.13" - use-composed-ref "^1.3.0" - use-latest "^1.2.1" - -react-waypoint@^10.3.0: - version "10.3.0" - resolved "https://registry.yarnpkg.com/react-waypoint/-/react-waypoint-10.3.0.tgz#fcc60e86c6c9ad2174fa58d066dc6ae54e3df71d" - integrity sha512-iF1y2c1BsoXuEGz08NoahaLFIGI9gTUAAOKip96HUmylRT6DUtpgoBPjk/Y8dfcFVmfVDvUzWjNXpZyKTOV0SQ== - dependencies: - "@babel/runtime" "^7.12.5" - consolidated-events "^1.1.0 || ^2.0.0" - prop-types "^15.0.0" - react-is "^17.0.1 || ^18.0.0" - -react@^17.0.2: - version "17.0.2" - resolved "https://registry.yarnpkg.com/react/-/react-17.0.2.tgz#d0b5cc516d29eb3eee383f75b62864cfb6800037" - integrity sha512-gnhPt75i/dq/z3/6q/0asP78D0u592D5L1pd7M8P+dck6Fu/jJeL6iVVK23fptSUZj8Vjf++7wXA8UNclGQcbA== - dependencies: - loose-envify "^1.1.0" - object-assign "^4.1.1" - -readable-stream@^2.0.1: - version "2.3.8" - resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.8.tgz#91125e8042bba1b9887f49345f6277027ce8be9b" - integrity sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA== - dependencies: - core-util-is "~1.0.0" - inherits "~2.0.3" - isarray "~1.0.0" - process-nextick-args "~2.0.0" - safe-buffer "~5.1.1" - string_decoder "~1.1.1" - util-deprecate "~1.0.1" - -readable-stream@^3.0.6, readable-stream@^3.1.1, readable-stream@^3.4.0: - version "3.6.2" - resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.2.tgz#56a9b36ea965c00c5a93ef31eb111a0f11056967" - integrity sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA== - dependencies: - inherits "^2.0.3" - string_decoder "^1.1.1" - util-deprecate "^1.0.1" - -readdirp@~3.6.0: - version "3.6.0" - resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-3.6.0.tgz#74a370bd857116e245b29cc97340cd431a02a6c7" - integrity sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA== - dependencies: - picomatch "^2.2.1" - -reading-time@^1.5.0: - version "1.5.0" - resolved "https://registry.yarnpkg.com/reading-time/-/reading-time-1.5.0.tgz#d2a7f1b6057cb2e169beaf87113cc3411b5bc5bb" - integrity sha512-onYyVhBNr4CmAxFsKS7bz+uTLRakypIe4R+5A824vBSkQy/hB3fZepoVEf8OVAxzLvK+H/jm9TzpI3ETSm64Kg== - -rechoir@^0.6.2: - version "0.6.2" - resolved "https://registry.yarnpkg.com/rechoir/-/rechoir-0.6.2.tgz#85204b54dba82d5742e28c96756ef43af50e3384" - integrity sha512-HFM8rkZ+i3zrV+4LQjwQ0W+ez98pApMGM3HUrN04j3CqzPOzl9nmP15Y8YXNm8QHGv/eacOVEjqhmWpkRV0NAw== - dependencies: - resolve "^1.1.6" - -recursive-readdir@^2.2.2: - version "2.2.3" - resolved "https://registry.yarnpkg.com/recursive-readdir/-/recursive-readdir-2.2.3.tgz#e726f328c0d69153bcabd5c322d3195252379372" - integrity sha512-8HrF5ZsXk5FAH9dgsx3BlUer73nIhuj+9OrQwEbLTPOBzGkL1lsFCR01am+v+0m2Cmbs1nP12hLDl5FA7EszKA== - dependencies: - minimatch "^3.0.5" - -regenerate-unicode-properties@^10.2.0: - version "10.2.0" - resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-10.2.0.tgz#626e39df8c372338ea9b8028d1f99dc3fd9c3db0" - integrity sha512-DqHn3DwbmmPVzeKj9woBadqmXxLvQoQIwu7nopMc72ztvxVmVk2SBhSnx67zuye5TP+lJsb/TBQsjLKhnDf3MA== - dependencies: - regenerate "^1.4.2" - -regenerate@^1.4.2: - version "1.4.2" - resolved "https://registry.yarnpkg.com/regenerate/-/regenerate-1.4.2.tgz#b9346d8827e8f5a32f7ba29637d398b69014848a" - integrity sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A== - -regenerator-runtime@^0.14.0: - version "0.14.1" - resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.14.1.tgz#356ade10263f685dda125100cd862c1db895327f" - integrity sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw== - -regenerator-transform@^0.15.2: - version "0.15.2" - resolved "https://registry.yarnpkg.com/regenerator-transform/-/regenerator-transform-0.15.2.tgz#5bbae58b522098ebdf09bca2f83838929001c7a4" - integrity sha512-hfMp2BoF0qOk3uc5V20ALGDS2ddjQaLrdl7xrGXvAIow7qeWRM2VA2HuCHkUKk9slq3VwEwLNK3DFBqDfPGYtg== - dependencies: - "@babel/runtime" "^7.8.4" - -regexpu-core@^6.1.1: - version "6.1.1" - resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-6.1.1.tgz#b469b245594cb2d088ceebc6369dceb8c00becac" - integrity sha512-k67Nb9jvwJcJmVpw0jPttR1/zVfnKf8Km0IPatrU/zJ5XeG3+Slx0xLXs9HByJSzXzrlz5EDvN6yLNMDc2qdnw== - dependencies: - regenerate "^1.4.2" - regenerate-unicode-properties "^10.2.0" - regjsgen "^0.8.0" - regjsparser "^0.11.0" - unicode-match-property-ecmascript "^2.0.0" - unicode-match-property-value-ecmascript "^2.1.0" - -registry-auth-token@^4.0.0: - version "4.2.2" - resolved "https://registry.yarnpkg.com/registry-auth-token/-/registry-auth-token-4.2.2.tgz#f02d49c3668884612ca031419491a13539e21fac" - integrity sha512-PC5ZysNb42zpFME6D/XlIgtNGdTl8bBOCw90xQLVMpzuuubJKYDWFAEuUNc+Cn8Z8724tg2SDhDRrkVEsqfDMg== - dependencies: - rc "1.2.8" - -registry-url@^5.0.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/registry-url/-/registry-url-5.1.0.tgz#e98334b50d5434b81136b44ec638d9c2009c5009" - integrity sha512-8acYXXTI0AkQv6RAOjE3vOaIXZkT9wo4LOFbBKYQEEnnMNBpKqdUrI6S4NT0KPIo/WVvJ5tE/X5LF/TQUf0ekw== - dependencies: - rc "^1.2.8" - -regjsgen@^0.8.0: - version "0.8.0" - resolved "https://registry.yarnpkg.com/regjsgen/-/regjsgen-0.8.0.tgz#df23ff26e0c5b300a6470cad160a9d090c3a37ab" - integrity sha512-RvwtGe3d7LvWiDQXeQw8p5asZUmfU1G/l6WbUXeHta7Y2PEIvBTwH6E2EfmYUK8pxcxEdEmaomqyp0vZZ7C+3Q== - -regjsparser@^0.11.0: - version "0.11.1" - resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.11.1.tgz#ae55c74f646db0c8fcb922d4da635e33da405149" - integrity sha512-1DHODs4B8p/mQHU9kr+jv8+wIC9mtG4eBHxWxIq5mhjE3D5oORhCc6deRKzTjs9DcfRFmj9BHSDguZklqCGFWQ== - dependencies: - jsesc "~3.0.2" - -relateurl@^0.2.7: - version "0.2.7" - resolved "https://registry.yarnpkg.com/relateurl/-/relateurl-0.2.7.tgz#54dbf377e51440aca90a4cd274600d3ff2d888a9" - integrity sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog== - -remark-emoji@^2.2.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/remark-emoji/-/remark-emoji-2.2.0.tgz#1c702090a1525da5b80e15a8f963ef2c8236cac7" - integrity sha512-P3cj9s5ggsUvWw5fS2uzCHJMGuXYRb0NnZqYlNecewXt8QBU9n5vW3DUUKOhepS8F9CwdMx9B8a3i7pqFWAI5w== - dependencies: - emoticon "^3.2.0" - node-emoji "^1.10.0" - unist-util-visit "^2.0.3" - -remark-footnotes@2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/remark-footnotes/-/remark-footnotes-2.0.0.tgz#9001c4c2ffebba55695d2dd80ffb8b82f7e6303f" - integrity sha512-3Clt8ZMH75Ayjp9q4CorNeyjwIxHFcTkaektplKGl2A1jNGEUey8cKL0ZC5vJwfcD5GFGsNLImLG/NGzWIzoMQ== - -remark-mdx@1.6.22: - version "1.6.22" - resolved "https://registry.yarnpkg.com/remark-mdx/-/remark-mdx-1.6.22.tgz#06a8dab07dcfdd57f3373af7f86bd0e992108bbd" - integrity sha512-phMHBJgeV76uyFkH4rvzCftLfKCr2RZuF+/gmVcaKrpsihyzmhXjA0BEMDaPTXG5y8qZOKPVo83NAOX01LPnOQ== - dependencies: - "@babel/core" "7.12.9" - "@babel/helper-plugin-utils" "7.10.4" - "@babel/plugin-proposal-object-rest-spread" "7.12.1" - "@babel/plugin-syntax-jsx" "7.12.1" - "@mdx-js/util" "1.6.22" - is-alphabetical "1.0.4" - remark-parse "8.0.3" - unified "9.2.0" - -remark-parse@8.0.3: - version "8.0.3" - resolved "https://registry.yarnpkg.com/remark-parse/-/remark-parse-8.0.3.tgz#9c62aa3b35b79a486454c690472906075f40c7e1" - integrity sha512-E1K9+QLGgggHxCQtLt++uXltxEprmWzNfg+MxpfHsZlrddKzZ/hZyWHDbK3/Ap8HJQqYJRXP+jHczdL6q6i85Q== - dependencies: - ccount "^1.0.0" - collapse-white-space "^1.0.2" - is-alphabetical "^1.0.0" - is-decimal "^1.0.0" - is-whitespace-character "^1.0.0" - is-word-character "^1.0.0" - markdown-escapes "^1.0.0" - parse-entities "^2.0.0" - repeat-string "^1.5.4" - state-toggle "^1.0.0" - trim "0.0.1" - trim-trailing-lines "^1.0.0" - unherit "^1.0.4" - unist-util-remove-position "^2.0.0" - vfile-location "^3.0.0" - xtend "^4.0.1" - -remark-squeeze-paragraphs@4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/remark-squeeze-paragraphs/-/remark-squeeze-paragraphs-4.0.0.tgz#76eb0e085295131c84748c8e43810159c5653ead" - integrity sha512-8qRqmL9F4nuLPIgl92XUuxI3pFxize+F1H0e/W3llTk0UsjJaj01+RrirkMw7P21RKe4X6goQhYRSvNWX+70Rw== - dependencies: - mdast-squeeze-paragraphs "^4.0.0" - -renderkid@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/renderkid/-/renderkid-3.0.0.tgz#5fd823e4d6951d37358ecc9a58b1f06836b6268a" - integrity sha512-q/7VIQA8lmM1hF+jn+sFSPWGlMkSAeNYcPLmDQx2zzuiDfaLrOmumR8iaUKlenFgh0XRPIUeSPlH3A+AW3Z5pg== - dependencies: - css-select "^4.1.3" - dom-converter "^0.2.0" - htmlparser2 "^6.1.0" - lodash "^4.17.21" - strip-ansi "^6.0.1" - -repeat-string@^1.5.4: - version "1.6.1" - resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637" - integrity sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w== - -require-from-string@^2.0.2: - version "2.0.2" - resolved "https://registry.yarnpkg.com/require-from-string/-/require-from-string-2.0.2.tgz#89a7fdd938261267318eafe14f9c32e598c36909" - integrity sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw== - -"require-like@>= 0.1.1": - version "0.1.2" - resolved "https://registry.yarnpkg.com/require-like/-/require-like-0.1.2.tgz#ad6f30c13becd797010c468afa775c0c0a6b47fa" - integrity sha512-oyrU88skkMtDdauHDuKVrgR+zuItqr6/c//FXzvmxRGMexSDc6hNvJInGW3LL46n+8b50RykrvwSUIIQH2LQ5A== - -requires-port@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff" - integrity sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ== - -resolve-from@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-4.0.0.tgz#4abcd852ad32dd7baabfe9b40e00a36db5f392e6" - integrity sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g== - -resolve-pathname@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/resolve-pathname/-/resolve-pathname-3.0.0.tgz#99d02224d3cf263689becbb393bc560313025dcd" - integrity sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng== - -resolve@^1.1.6, resolve@^1.14.2, resolve@^1.3.2: - version "1.22.8" - resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.22.8.tgz#b6c87a9f2aa06dfab52e3d70ac8cde321fa5a48d" - integrity sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw== - dependencies: - is-core-module "^2.13.0" - path-parse "^1.0.7" - supports-preserve-symlinks-flag "^1.0.0" - -responselike@^1.0.2: - version "1.0.2" - resolved "https://registry.yarnpkg.com/responselike/-/responselike-1.0.2.tgz#918720ef3b631c5642be068f15ade5a46f4ba1e7" - integrity sha512-/Fpe5guzJk1gPqdJLJR5u7eG/gNY4nImjbRDaVWVMRhne55TCmj2i9Q+54PBRfatRC8v/rIiv9BN0pMd9OV5EQ== - dependencies: - lowercase-keys "^1.0.0" - -retry@^0.13.1: - version "0.13.1" - resolved "https://registry.yarnpkg.com/retry/-/retry-0.13.1.tgz#185b1587acf67919d63b357349e03537b2484658" - integrity sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg== - -reusify@^1.0.4: - version "1.0.4" - resolved "https://registry.yarnpkg.com/reusify/-/reusify-1.0.4.tgz#90da382b1e126efc02146e90845a88db12925d76" - integrity sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw== - -rimraf@^3.0.2: - version "3.0.2" - resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-3.0.2.tgz#f1a5402ba6220ad52cc1282bac1ae3aa49fd061a" - integrity sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA== - dependencies: - glob "^7.1.3" - -rtl-detect@^1.0.4: - version "1.1.2" - resolved "https://registry.yarnpkg.com/rtl-detect/-/rtl-detect-1.1.2.tgz#ca7f0330af5c6bb626c15675c642ba85ad6273c6" - integrity sha512-PGMBq03+TTG/p/cRB7HCLKJ1MgDIi07+QU1faSjiYRfmY5UsAttV9Hs08jDAHVwcOwmVLcSJkpwyfXszVjWfIQ== - -rtlcss@^3.5.0: - version "3.5.0" - resolved "https://registry.yarnpkg.com/rtlcss/-/rtlcss-3.5.0.tgz#c9eb91269827a102bac7ae3115dd5d049de636c3" - integrity sha512-wzgMaMFHQTnyi9YOwsx9LjOxYXJPzS8sYnFaKm6R5ysvTkwzHiB0vxnbHwchHQT65PTdBjDG21/kQBWI7q9O7A== - dependencies: - find-up "^5.0.0" - picocolors "^1.0.0" - postcss "^8.3.11" - strip-json-comments "^3.1.1" - -run-parallel@^1.1.9: - version "1.2.0" - resolved "https://registry.yarnpkg.com/run-parallel/-/run-parallel-1.2.0.tgz#66d1368da7bdf921eb9d95bd1a9229e7f21a43ee" - integrity sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA== - dependencies: - queue-microtask "^1.2.2" - -rxjs@^7.5.4: - version "7.8.1" - resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz#6f6f3d99ea8044291efd92e7c7fcf562c4057543" - integrity sha512-AA3TVj+0A2iuIoQkWEK/tqFjBq2j+6PO6Y0zJcvzLAFhEFIO3HL0vls9hWLncZbAAbK0mar7oZ4V079I/qPMxg== - dependencies: - tslib "^2.1.0" - -safe-buffer@5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1: - version "5.1.2" - resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d" - integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g== - -safe-buffer@5.2.1, safe-buffer@>=5.1.0, safe-buffer@^5.0.1, safe-buffer@^5.1.0, safe-buffer@~5.2.0: - version "5.2.1" - resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.1.tgz#1eaf9fa9bdb1fdd4ec75f58f9cdb4e6b7827eec6" - integrity sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ== - -"safer-buffer@>= 2.1.2 < 3", "safer-buffer@>= 2.1.2 < 3.0.0": - version "2.1.2" - resolved "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a" - integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg== - -sax@^1.2.4: - version "1.4.1" - resolved "https://registry.yarnpkg.com/sax/-/sax-1.4.1.tgz#44cc8988377f126304d3b3fc1010c733b929ef0f" - integrity sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg== - -scheduler@^0.20.2: - version "0.20.2" - resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.20.2.tgz#4baee39436e34aa93b4874bddcbf0fe8b8b50e91" - integrity sha512-2eWfGgAqqWFGqtdMmcL5zCMK1U8KlXv8SQFGglL3CEtd0aDVDWgeF/YoCmvln55m5zSk3J/20hTaSBeSObsQDQ== - dependencies: - loose-envify "^1.1.0" - object-assign "^4.1.1" - -schema-utils@2.7.0: - version "2.7.0" - resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-2.7.0.tgz#17151f76d8eae67fbbf77960c33c676ad9f4efc7" - integrity sha512-0ilKFI6QQF5nxDZLFn2dMjvc4hjg/Wkg7rHd3jK6/A4a1Hl9VFdQWvgB1UMGoU94pad1P/8N7fMcEnLnSiju8A== - dependencies: - "@types/json-schema" "^7.0.4" - ajv "^6.12.2" - ajv-keywords "^3.4.1" - -schema-utils@^2.6.5: - version "2.7.1" - resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-2.7.1.tgz#1ca4f32d1b24c590c203b8e7a50bf0ea4cd394d7" - integrity sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg== - dependencies: - "@types/json-schema" "^7.0.5" - ajv "^6.12.4" - ajv-keywords "^3.5.2" - -schema-utils@^3.0.0, schema-utils@^3.1.1, schema-utils@^3.2.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-3.3.0.tgz#f50a88877c3c01652a15b622ae9e9795df7a60fe" - integrity sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg== - dependencies: - "@types/json-schema" "^7.0.8" - ajv "^6.12.5" - ajv-keywords "^3.5.2" - -schema-utils@^4.0.0: - version "4.2.0" - resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-4.2.0.tgz#70d7c93e153a273a805801882ebd3bff20d89c8b" - integrity sha512-L0jRsrPpjdckP3oPug3/VxNKt2trR8TcabrM6FOAAlvC/9Phcmm+cuAgTlxBqdBR1WJx7Naj9WHw+aOmheSVbw== - dependencies: - "@types/json-schema" "^7.0.9" - ajv "^8.9.0" - ajv-formats "^2.1.1" - ajv-keywords "^5.1.0" - -section-matter@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/section-matter/-/section-matter-1.0.0.tgz#e9041953506780ec01d59f292a19c7b850b84167" - integrity sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA== - dependencies: - extend-shallow "^2.0.1" - kind-of "^6.0.0" - -select-hose@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/select-hose/-/select-hose-2.0.0.tgz#625d8658f865af43ec962bfc376a37359a4994ca" - integrity sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg== - -selfsigned@^2.1.1: - version "2.4.1" - resolved "https://registry.yarnpkg.com/selfsigned/-/selfsigned-2.4.1.tgz#560d90565442a3ed35b674034cec4e95dceb4ae0" - integrity sha512-th5B4L2U+eGLq1TVh7zNRGBapioSORUeymIydxgFpwww9d2qyKvtuPU2jJuHvYAwwqi2Y596QBL3eEqcPEYL8Q== - dependencies: - "@types/node-forge" "^1.3.0" - node-forge "^1" - -semver-diff@^3.1.1: - version "3.1.1" - resolved "https://registry.yarnpkg.com/semver-diff/-/semver-diff-3.1.1.tgz#05f77ce59f325e00e2706afd67bb506ddb1ca32b" - integrity sha512-GX0Ix/CJcHyB8c4ykpHGIAvLyOwOobtM/8d+TQkAd81/bEjgPHrfba41Vpesr7jX/t8Uh+R3EX9eAS5be+jQYg== - dependencies: - semver "^6.3.0" - -semver@^5.4.1: - version "5.7.2" - resolved "https://registry.yarnpkg.com/semver/-/semver-5.7.2.tgz#48d55db737c3287cd4835e17fa13feace1c41ef8" - integrity sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g== - -semver@^6.0.0, semver@^6.2.0, semver@^6.3.0, semver@^6.3.1: - version "6.3.1" - resolved "https://registry.yarnpkg.com/semver/-/semver-6.3.1.tgz#556d2ef8689146e46dcea4bfdd095f3434dffcb4" - integrity sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA== - -semver@^7.3.2, semver@^7.3.4, semver@^7.3.5, semver@^7.3.7, semver@^7.5.4: - version "7.6.3" - resolved "https://registry.yarnpkg.com/semver/-/semver-7.6.3.tgz#980f7b5550bc175fb4dc09403085627f9eb33143" - integrity sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A== - -send@0.19.0: - version "0.19.0" - resolved "https://registry.yarnpkg.com/send/-/send-0.19.0.tgz#bbc5a388c8ea6c048967049dbeac0e4a3f09d7f8" - integrity sha512-dW41u5VfLXu8SJh5bwRmyYUbAoSB3c9uQh6L8h/KtsFREPWpbX1lrljJo186Jc4nmci/sGUZ9a0a0J2zgfq2hw== - dependencies: - debug "2.6.9" - depd "2.0.0" - destroy "1.2.0" - encodeurl "~1.0.2" - escape-html "~1.0.3" - etag "~1.8.1" - fresh "0.5.2" - http-errors "2.0.0" - mime "1.6.0" - ms "2.1.3" - on-finished "2.4.1" - range-parser "~1.2.1" - statuses "2.0.1" - -serialize-javascript@^6.0.0, serialize-javascript@^6.0.1: - version "6.0.2" - resolved "https://registry.yarnpkg.com/serialize-javascript/-/serialize-javascript-6.0.2.tgz#defa1e055c83bf6d59ea805d8da862254eb6a6c2" - integrity sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g== - dependencies: - randombytes "^2.1.0" - -serve-handler@^6.1.3: - version "6.1.6" - resolved "https://registry.yarnpkg.com/serve-handler/-/serve-handler-6.1.6.tgz#50803c1d3e947cd4a341d617f8209b22bd76cfa1" - integrity sha512-x5RL9Y2p5+Sh3D38Fh9i/iQ5ZK+e4xuXRd/pGbM4D13tgo/MGwbttUk8emytcr1YYzBYs+apnUngBDFYfpjPuQ== - dependencies: - bytes "3.0.0" - content-disposition "0.5.2" - mime-types "2.1.18" - minimatch "3.1.2" - path-is-inside "1.0.2" - path-to-regexp "3.3.0" - range-parser "1.2.0" - -serve-index@^1.9.1: - version "1.9.1" - resolved "https://registry.yarnpkg.com/serve-index/-/serve-index-1.9.1.tgz#d3768d69b1e7d82e5ce050fff5b453bea12a9239" - integrity sha512-pXHfKNP4qujrtteMrSBb0rc8HJ9Ms/GrXwcUtUtD5s4ewDJI8bT3Cz2zTVRMKtri49pLx2e0Ya8ziP5Ya2pZZw== - dependencies: - accepts "~1.3.4" - batch "0.6.1" - debug "2.6.9" - escape-html "~1.0.3" - http-errors "~1.6.2" - mime-types "~2.1.17" - parseurl "~1.3.2" - -serve-static@1.16.2: - version "1.16.2" - resolved "https://registry.yarnpkg.com/serve-static/-/serve-static-1.16.2.tgz#b6a5343da47f6bdd2673848bf45754941e803296" - integrity sha512-VqpjJZKadQB/PEbEwvFdO43Ax5dFBZ2UECszz8bQ7pi7wt//PWe1P6MN7eCnjsatYtBT6EuiClbjSWP2WrIoTw== - dependencies: - encodeurl "~2.0.0" - escape-html "~1.0.3" - parseurl "~1.3.3" - send "0.19.0" - -set-function-length@^1.2.1: - version "1.2.2" - resolved "https://registry.yarnpkg.com/set-function-length/-/set-function-length-1.2.2.tgz#aac72314198eaed975cf77b2c3b6b880695e5449" - integrity sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg== - dependencies: - define-data-property "^1.1.4" - es-errors "^1.3.0" - function-bind "^1.1.2" - get-intrinsic "^1.2.4" - gopd "^1.0.1" - has-property-descriptors "^1.0.2" - -setimmediate@^1.0.5: - version "1.0.5" - resolved "https://registry.yarnpkg.com/setimmediate/-/setimmediate-1.0.5.tgz#290cbb232e306942d7d7ea9b83732ab7856f8285" - integrity sha512-MATJdZp8sLqDl/68LfQmbP8zKPLQNV6BIZoIgrscFDQ+RsvK/BxeDQOgyxKKoh0y/8h3BqVFnCqQ/gd+reiIXA== - -setprototypeof@1.1.0: - version "1.1.0" - resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.0.tgz#d0bd85536887b6fe7c0d818cb962d9d91c54e656" - integrity sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ== - -setprototypeof@1.2.0: - version "1.2.0" - resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.2.0.tgz#66c9a24a73f9fc28cbe66b09fed3d33dcaf1b424" - integrity sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw== - -shallow-clone@^3.0.0: - version "3.0.1" - resolved "https://registry.yarnpkg.com/shallow-clone/-/shallow-clone-3.0.1.tgz#8f2981ad92531f55035b01fb230769a40e02efa3" - integrity sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA== - dependencies: - kind-of "^6.0.2" - -shallowequal@^1.1.0: - version "1.1.0" - resolved "https://registry.yarnpkg.com/shallowequal/-/shallowequal-1.1.0.tgz#188d521de95b9087404fd4dcb68b13df0ae4e7f8" - integrity sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ== - -sharp@^0.30.7: - version "0.30.7" - resolved "https://registry.yarnpkg.com/sharp/-/sharp-0.30.7.tgz#7862bda98804fdd1f0d5659c85e3324b90d94c7c" - integrity sha512-G+MY2YW33jgflKPTXXptVO28HvNOo9G3j0MybYAHeEmby+QuD2U98dT6ueht9cv/XDqZspSpIhoSW+BAKJ7Hig== - dependencies: - color "^4.2.3" - detect-libc "^2.0.1" - node-addon-api "^5.0.0" - prebuild-install "^7.1.1" - semver "^7.3.7" - simple-get "^4.0.1" - tar-fs "^2.1.1" - tunnel-agent "^0.6.0" - -shebang-command@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-2.0.0.tgz#ccd0af4f8835fbdc265b82461aaf0c36663f34ea" - integrity sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA== - dependencies: - shebang-regex "^3.0.0" - -shebang-regex@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-3.0.0.tgz#ae16f1644d873ecad843b0307b143362d4c42172" - integrity sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A== - -shell-quote@^1.7.3, shell-quote@^1.8.1: - version "1.8.1" - resolved "https://registry.yarnpkg.com/shell-quote/-/shell-quote-1.8.1.tgz#6dbf4db75515ad5bac63b4f1894c3a154c766680" - integrity sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA== - -shelljs@^0.8.5: - version "0.8.5" - resolved "https://registry.yarnpkg.com/shelljs/-/shelljs-0.8.5.tgz#de055408d8361bed66c669d2f000538ced8ee20c" - integrity sha512-TiwcRcrkhHvbrZbnRcFYMLl30Dfov3HKqzp5tO5b4pt6G/SezKcYhmDg15zXVBswHmctSAQKznqNW2LO5tTDow== - dependencies: - glob "^7.0.0" - interpret "^1.0.0" - rechoir "^0.6.2" - -side-channel@^1.0.6: - version "1.0.6" - resolved "https://registry.yarnpkg.com/side-channel/-/side-channel-1.0.6.tgz#abd25fb7cd24baf45466406b1096b7831c9215f2" - integrity sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA== - dependencies: - call-bind "^1.0.7" - es-errors "^1.3.0" - get-intrinsic "^1.2.4" - object-inspect "^1.13.1" - -signal-exit@^3.0.2, signal-exit@^3.0.3: - version "3.0.7" - resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.7.tgz#a9a1767f8af84155114eaabd73f99273c8f59ad9" - integrity sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ== - -simple-concat@^1.0.0: - version "1.0.1" - resolved "https://registry.yarnpkg.com/simple-concat/-/simple-concat-1.0.1.tgz#f46976082ba35c2263f1c8ab5edfe26c41c9552f" - integrity sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q== - -simple-get@^4.0.0, simple-get@^4.0.1: - version "4.0.1" - resolved "https://registry.yarnpkg.com/simple-get/-/simple-get-4.0.1.tgz#4a39db549287c979d352112fa03fd99fd6bc3543" - integrity sha512-brv7p5WgH0jmQJr1ZDDfKDOSeWWg+OVypG99A/5vYGPqJ6pxiaHLy8nxtFjBA7oMa01ebA9gfh1uMCFqOuXxvA== - dependencies: - decompress-response "^6.0.0" - once "^1.3.1" - simple-concat "^1.0.0" - -simple-swizzle@^0.2.2: - version "0.2.2" - resolved "https://registry.yarnpkg.com/simple-swizzle/-/simple-swizzle-0.2.2.tgz#a4da6b635ffcccca33f70d17cb92592de95e557a" - integrity sha512-JA//kQgZtbuY83m+xT+tXJkmJncGMTFT+C+g2h2R9uxkYIrE2yy9sgmcLhCnw57/WSD+Eh3J97FPEDFnbXnDUg== - dependencies: - is-arrayish "^0.3.1" - -sirv@^2.0.3: - version "2.0.4" - resolved "https://registry.yarnpkg.com/sirv/-/sirv-2.0.4.tgz#5dd9a725c578e34e449f332703eb2a74e46a29b0" - integrity sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ== - dependencies: - "@polka/url" "^1.0.0-next.24" - mrmime "^2.0.0" - totalist "^3.0.0" - -sisteransi@^1.0.5: - version "1.0.5" - resolved "https://registry.yarnpkg.com/sisteransi/-/sisteransi-1.0.5.tgz#134d681297756437cc05ca01370d3a7a571075ed" - integrity sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg== - -sitemap@^7.1.1: - version "7.1.2" - resolved "https://registry.yarnpkg.com/sitemap/-/sitemap-7.1.2.tgz#6ce1deb43f6f177c68bc59cf93632f54e3ae6b72" - integrity sha512-ARCqzHJ0p4gWt+j7NlU5eDlIO9+Rkr/JhPFZKKQ1l5GCus7rJH4UdrlVAh0xC/gDS/Qir2UMxqYNHtsKr2rpCw== - dependencies: - "@types/node" "^17.0.5" - "@types/sax" "^1.2.1" - arg "^5.0.0" - sax "^1.2.4" - -slash@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/slash/-/slash-3.0.0.tgz#6539be870c165adbd5240220dbe361f1bc4d4634" - integrity sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q== - -slash@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/slash/-/slash-4.0.0.tgz#2422372176c4c6c5addb5e2ada885af984b396a7" - integrity sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew== - -snake-case@^3.0.4: - version "3.0.4" - resolved "https://registry.yarnpkg.com/snake-case/-/snake-case-3.0.4.tgz#4f2bbd568e9935abdfd593f34c691dadb49c452c" - integrity sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg== - dependencies: - dot-case "^3.0.4" - tslib "^2.0.3" - -sockjs@^0.3.24: - version "0.3.24" - resolved "https://registry.yarnpkg.com/sockjs/-/sockjs-0.3.24.tgz#c9bc8995f33a111bea0395ec30aa3206bdb5ccce" - integrity sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ== - dependencies: - faye-websocket "^0.11.3" - uuid "^8.3.2" - websocket-driver "^0.7.4" - -sort-css-media-queries@2.1.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/sort-css-media-queries/-/sort-css-media-queries-2.1.0.tgz#7c85e06f79826baabb232f5560e9745d7a78c4ce" - integrity sha512-IeWvo8NkNiY2vVYdPa27MCQiR0MN0M80johAYFVxWWXQ44KU84WNxjslwBHmc/7ZL2ccwkM7/e6S5aiKZXm7jA== - -source-map-js@^1.0.1, source-map-js@^1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/source-map-js/-/source-map-js-1.2.1.tgz#1ce5650fddd87abc099eda37dcff024c2667ae46" - integrity sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA== - -source-map-support@~0.5.20: - version "0.5.21" - resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.21.tgz#04fe7c7f9e1ed2d662233c28cb2b35b9f63f6e4f" - integrity sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w== - dependencies: - buffer-from "^1.0.0" - source-map "^0.6.0" - -source-map@^0.5.0: - version "0.5.7" - resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.5.7.tgz#8a039d2d1021d22d1ea14c80d8ea468ba2ef3fcc" - integrity sha512-LbrmJOMUSdEVxIKvdcJzQC+nQhe8FUZQTXQy6+I75skNgn3OoQ0DZA8YnFa7gp8tqtL3KPf1kmo0R5DoApeSGQ== - -source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.0: - version "0.6.1" - resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz#74722af32e9614e9c287a8d0bbde48b5e2f1a263" - integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g== - -space-separated-tokens@^1.0.0: - version "1.1.5" - resolved "https://registry.yarnpkg.com/space-separated-tokens/-/space-separated-tokens-1.1.5.tgz#85f32c3d10d9682007e917414ddc5c26d1aa6899" - integrity sha512-q/JSVd1Lptzhf5bkYm4ob4iWPjx0KiRe3sRFBNrVqbJkFaBm5vbbowy1mymoPNLRa52+oadOhJ+K49wsSeSjTA== - -spdy-transport@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/spdy-transport/-/spdy-transport-3.0.0.tgz#00d4863a6400ad75df93361a1608605e5dcdcf31" - integrity sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw== - dependencies: - debug "^4.1.0" - detect-node "^2.0.4" - hpack.js "^2.1.6" - obuf "^1.1.2" - readable-stream "^3.0.6" - wbuf "^1.7.3" - -spdy@^4.0.2: - version "4.0.2" - resolved "https://registry.yarnpkg.com/spdy/-/spdy-4.0.2.tgz#b74f466203a3eda452c02492b91fb9e84a27677b" - integrity sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA== - dependencies: - debug "^4.1.0" - handle-thing "^2.0.0" - http-deceiver "^1.2.7" - select-hose "^2.0.0" - spdy-transport "^3.0.0" - -sprintf-js@~1.0.2: - version "1.0.3" - resolved "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.0.3.tgz#04e6926f662895354f3dd015203633b857297e2c" - integrity sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g== - -stable@^0.1.8: - version "0.1.8" - resolved "https://registry.yarnpkg.com/stable/-/stable-0.1.8.tgz#836eb3c8382fe2936feaf544631017ce7d47a3cf" - integrity sha512-ji9qxRnOVfcuLDySj9qzhGSEFVobyt1kIOSkj1qZzYLzq7Tos/oUUWvotUPQLlrsidqsK6tBH89Bc9kL5zHA6w== - -state-toggle@^1.0.0: - version "1.0.3" - resolved "https://registry.yarnpkg.com/state-toggle/-/state-toggle-1.0.3.tgz#e123b16a88e143139b09c6852221bc9815917dfe" - integrity sha512-d/5Z4/2iiCnHw6Xzghyhb+GcmF89bxwgXG60wjIiZaxnymbyOmI8Hk4VqHXiVVp6u2ysaskFfXg3ekCj4WNftQ== - -statuses@2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/statuses/-/statuses-2.0.1.tgz#55cb000ccf1d48728bd23c685a063998cf1a1b63" - integrity sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ== - -"statuses@>= 1.4.0 < 2": - version "1.5.0" - resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.5.0.tgz#161c7dac177659fd9811f43771fa99381478628c" - integrity sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA== - -std-env@^3.0.1: - version "3.7.0" - resolved "https://registry.yarnpkg.com/std-env/-/std-env-3.7.0.tgz#c9f7386ced6ecf13360b6c6c55b8aaa4ef7481d2" - integrity sha512-JPbdCEQLj1w5GilpiHAx3qJvFndqybBysA3qUOnznweH4QbNYUsW/ea8QzSrnh0vNsezMMw5bcVool8lM0gwzg== - -string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.2: - version "4.2.3" - resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.3.tgz#269c7117d27b05ad2e536830a8ec895ef9c6d010" - integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g== - dependencies: - emoji-regex "^8.0.0" - is-fullwidth-code-point "^3.0.0" - strip-ansi "^6.0.1" - -string-width@^5.0.1: - version "5.1.2" - resolved "https://registry.yarnpkg.com/string-width/-/string-width-5.1.2.tgz#14f8daec6d81e7221d2a357e668cab73bdbca794" - integrity sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA== - dependencies: - eastasianwidth "^0.2.0" - emoji-regex "^9.2.2" - strip-ansi "^7.0.1" - -string_decoder@^1.1.1: - version "1.3.0" - resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz#42f114594a46cf1a8e30b0a84f56c78c3edac21e" - integrity sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA== - dependencies: - safe-buffer "~5.2.0" - -string_decoder@~1.1.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz#9cf1611ba62685d7030ae9e4ba34149c3af03fc8" - integrity sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg== - dependencies: - safe-buffer "~5.1.0" - -stringify-object@^3.3.0: - version "3.3.0" - resolved "https://registry.yarnpkg.com/stringify-object/-/stringify-object-3.3.0.tgz#703065aefca19300d3ce88af4f5b3956d7556629" - integrity sha512-rHqiFh1elqCQ9WPLIC8I0Q/g/wj5J1eMkyoiD6eoQApWHP0FtlK7rqnhmabL5VUY9JQCcqwwvlOaSuutekgyrw== - dependencies: - get-own-enumerable-property-symbols "^3.0.0" - is-obj "^1.0.1" - is-regexp "^1.0.0" - -strip-ansi@^6.0.0, strip-ansi@^6.0.1: - version "6.0.1" - resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.1.tgz#9e26c63d30f53443e9489495b2105d37b67a85d9" - integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A== - dependencies: - ansi-regex "^5.0.1" - -strip-ansi@^7.0.1: - version "7.1.0" - resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-7.1.0.tgz#d5b6568ca689d8561370b0707685d22434faff45" - integrity sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ== - dependencies: - ansi-regex "^6.0.1" - -strip-bom-string@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/strip-bom-string/-/strip-bom-string-1.0.0.tgz#e5211e9224369fbb81d633a2f00044dc8cedad92" - integrity sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g== - -strip-final-newline@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/strip-final-newline/-/strip-final-newline-2.0.0.tgz#89b852fb2fcbe936f6f4b3187afb0a12c1ab58ad" - integrity sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA== - -strip-json-comments@^3.1.1: - version "3.1.1" - resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-3.1.1.tgz#31f1281b3832630434831c310c01cccda8cbe006" - integrity sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig== - -strip-json-comments@~2.0.1: - version "2.0.1" - resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-2.0.1.tgz#3c531942e908c2697c0ec344858c286c7ca0a60a" - integrity sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ== - -style-to-object@0.3.0, style-to-object@^0.3.0: - version "0.3.0" - resolved "https://registry.yarnpkg.com/style-to-object/-/style-to-object-0.3.0.tgz#b1b790d205991cc783801967214979ee19a76e46" - integrity sha512-CzFnRRXhzWIdItT3OmF8SQfWyahHhjq3HwcMNCNLn+N7klOOqPjMeG/4JSu77D7ypZdGvSzvkrbyeTMizz2VrA== - dependencies: - inline-style-parser "0.1.1" - -stylehacks@^5.1.1: - version "5.1.1" - resolved "https://registry.yarnpkg.com/stylehacks/-/stylehacks-5.1.1.tgz#7934a34eb59d7152149fa69d6e9e56f2fc34bcc9" - integrity sha512-sBpcd5Hx7G6seo7b1LkpttvTz7ikD0LlH5RmdcBNb6fFR0Fl7LQwHDFr300q4cwUqi+IYrFGmsIHieMBfnN/Bw== - dependencies: - browserslist "^4.21.4" - postcss-selector-parser "^6.0.4" - -supports-color@^5.3.0: - version "5.5.0" - resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f" - integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow== - dependencies: - has-flag "^3.0.0" - -supports-color@^7.1.0: - version "7.2.0" - resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-7.2.0.tgz#1b7dcdcb32b8138801b3e478ba6a51caa89648da" - integrity sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw== - dependencies: - has-flag "^4.0.0" - -supports-color@^8.0.0: - version "8.1.1" - resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-8.1.1.tgz#cd6fc17e28500cff56c1b86c0a7fd4a54a73005c" - integrity sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q== - dependencies: - has-flag "^4.0.0" - -supports-preserve-symlinks-flag@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz#6eda4bd344a3c94aea376d4cc31bc77311039e09" - integrity sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w== - -svg-parser@^2.0.4: - version "2.0.4" - resolved "https://registry.yarnpkg.com/svg-parser/-/svg-parser-2.0.4.tgz#fdc2e29e13951736140b76cb122c8ee6630eb6b5" - integrity sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ== - -svgo@^2.7.0, svgo@^2.8.0: - version "2.8.0" - resolved "https://registry.yarnpkg.com/svgo/-/svgo-2.8.0.tgz#4ff80cce6710dc2795f0c7c74101e6764cfccd24" - integrity sha512-+N/Q9kV1+F+UeWYoSiULYo4xYSDQlTgb+ayMobAXPwMnLvop7oxKMo9OzIrX5x3eS4L4f2UHhc9axXwY8DpChg== - dependencies: - "@trysound/sax" "0.2.0" - commander "^7.2.0" - css-select "^4.1.3" - css-tree "^1.1.3" - csso "^4.2.0" - picocolors "^1.0.0" - stable "^0.1.8" - -svgo@^3.0.2: - version "3.3.2" - resolved "https://registry.yarnpkg.com/svgo/-/svgo-3.3.2.tgz#ad58002652dffbb5986fc9716afe52d869ecbda8" - integrity sha512-OoohrmuUlBs8B8o6MB2Aevn+pRIH9zDALSR+6hhqVfa6fRwG/Qw9VUMSMW9VNg2CFc/MTIfabtdOVl9ODIJjpw== - dependencies: - "@trysound/sax" "0.2.0" - commander "^7.2.0" - css-select "^5.1.0" - css-tree "^2.3.1" - css-what "^6.1.0" - csso "^5.0.5" - picocolors "^1.0.0" - -swc-loader@^0.2.6: - version "0.2.6" - resolved "https://registry.yarnpkg.com/swc-loader/-/swc-loader-0.2.6.tgz#bf0cba8eeff34bb19620ead81d1277fefaec6bc8" - integrity sha512-9Zi9UP2YmDpgmQVbyOPJClY0dwf58JDyDMQ7uRc4krmc72twNI2fvlBWHLqVekBpPc7h5NJkGVT1zNDxFrqhvg== - dependencies: - "@swc/counter" "^0.1.3" - -tapable@^1.0.0: - version "1.1.3" - resolved "https://registry.yarnpkg.com/tapable/-/tapable-1.1.3.tgz#a1fccc06b58db61fd7a45da2da44f5f3a3e67ba2" - integrity sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA== - -tapable@^2.0.0, tapable@^2.1.1, tapable@^2.2.0, tapable@^2.2.1: - version "2.2.1" - resolved "https://registry.yarnpkg.com/tapable/-/tapable-2.2.1.tgz#1967a73ef4060a82f12ab96af86d52fdb76eeca0" - integrity sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ== - -tar-fs@^2.0.0, tar-fs@^2.1.1: - version "2.1.1" - resolved "https://registry.yarnpkg.com/tar-fs/-/tar-fs-2.1.1.tgz#489a15ab85f1f0befabb370b7de4f9eb5cbe8784" - integrity sha512-V0r2Y9scmbDRLCNex/+hYzvp/zyYjvFbHPNgVTKfQvVrb6guiE/fxP+XblDNR011utopbkex2nM4dHNV6GDsng== - dependencies: - chownr "^1.1.1" - mkdirp-classic "^0.5.2" - pump "^3.0.0" - tar-stream "^2.1.4" - -tar-stream@^2.1.4: - version "2.2.0" - resolved "https://registry.yarnpkg.com/tar-stream/-/tar-stream-2.2.0.tgz#acad84c284136b060dc3faa64474aa9aebd77287" - integrity sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ== - dependencies: - bl "^4.0.3" - end-of-stream "^1.4.1" - fs-constants "^1.0.0" - inherits "^2.0.3" - readable-stream "^3.1.1" - -terser-webpack-plugin@^5.3.10, terser-webpack-plugin@^5.3.3: - version "5.3.10" - resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-5.3.10.tgz#904f4c9193c6fd2a03f693a2150c62a92f40d199" - integrity sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w== - dependencies: - "@jridgewell/trace-mapping" "^0.3.20" - jest-worker "^27.4.5" - schema-utils "^3.1.1" - serialize-javascript "^6.0.1" - terser "^5.26.0" - -terser@^5.10.0, terser@^5.26.0: - version "5.36.0" - resolved "https://registry.yarnpkg.com/terser/-/terser-5.36.0.tgz#8b0dbed459ac40ff7b4c9fd5a3a2029de105180e" - integrity sha512-IYV9eNMuFAV4THUspIRXkLakHnV6XO7FEdtKjf/mDyrnqUg9LnlOn6/RwRvM9SZjR4GUq8Nk8zj67FzVARr74w== - dependencies: - "@jridgewell/source-map" "^0.3.3" - acorn "^8.8.2" - commander "^2.20.0" - source-map-support "~0.5.20" - -text-table@^0.2.0: - version "0.2.0" - resolved "https://registry.yarnpkg.com/text-table/-/text-table-0.2.0.tgz#7f5ee823ae805207c00af2df4a84ec3fcfa570b4" - integrity sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw== - -thunky@^1.0.2: - version "1.1.0" - resolved "https://registry.yarnpkg.com/thunky/-/thunky-1.1.0.tgz#5abaf714a9405db0504732bbccd2cedd9ef9537d" - integrity sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA== - -tiny-invariant@^1.0.2: - version "1.3.3" - resolved "https://registry.yarnpkg.com/tiny-invariant/-/tiny-invariant-1.3.3.tgz#46680b7a873a0d5d10005995eb90a70d74d60127" - integrity sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg== - -tiny-warning@^1.0.0: - version "1.0.3" - resolved "https://registry.yarnpkg.com/tiny-warning/-/tiny-warning-1.0.3.tgz#94a30db453df4c643d0fd566060d60a875d84754" - integrity sha512-lBN9zLN/oAf68o3zNXYrdCt1kP8WsiGW8Oo2ka41b2IM5JL/S1CTyX1rW0mb/zSuJun0ZUrDxx4sqvYS2FWzPA== - -to-fast-properties@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/to-fast-properties/-/to-fast-properties-2.0.0.tgz#dc5e698cbd079265bc73e0377681a4e4e83f616e" - integrity sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog== - -to-readable-stream@^1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/to-readable-stream/-/to-readable-stream-1.0.0.tgz#ce0aa0c2f3df6adf852efb404a783e77c0475771" - integrity sha512-Iq25XBt6zD5npPhlLVXGFN3/gyR2/qODcKNNyTMd4vbm39HUaOiAM4PMq0eMVC/Tkxz+Zjdsc55g9yyz+Yq00Q== - -to-regex-range@^5.0.1: - version "5.0.1" - resolved "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-5.0.1.tgz#1648c44aae7c8d988a326018ed72f5b4dd0392e4" - integrity sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ== - dependencies: - is-number "^7.0.0" - -toidentifier@1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/toidentifier/-/toidentifier-1.0.1.tgz#3be34321a88a820ed1bd80dfaa33e479fbb8dd35" - integrity sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA== - -totalist@^3.0.0: - version "3.0.1" - resolved "https://registry.yarnpkg.com/totalist/-/totalist-3.0.1.tgz#ba3a3d600c915b1a97872348f79c127475f6acf8" - integrity sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ== - -tr46@~0.0.3: - version "0.0.3" - resolved "https://registry.yarnpkg.com/tr46/-/tr46-0.0.3.tgz#8184fd347dac9cdc185992f3a6622e14b9d9ab6a" - integrity sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw== - -trim-trailing-lines@^1.0.0: - version "1.1.4" - resolved "https://registry.yarnpkg.com/trim-trailing-lines/-/trim-trailing-lines-1.1.4.tgz#bd4abbec7cc880462f10b2c8b5ce1d8d1ec7c2c0" - integrity sha512-rjUWSqnfTNrjbB9NQWfPMH/xRK1deHeGsHoVfpxJ++XeYXE0d6B1En37AHfw3jtfTU7dzMzZL2jjpe8Qb5gLIQ== - -trim@0.0.1: - version "0.0.1" - resolved "https://registry.yarnpkg.com/trim/-/trim-0.0.1.tgz#5858547f6b290757ee95cccc666fb50084c460dd" - integrity sha512-YzQV+TZg4AxpKxaTHK3c3D+kRDCGVEE7LemdlQZoQXn0iennk10RsIoY6ikzAqJTc9Xjl9C1/waHom/J86ziAQ== - -trough@^1.0.0: - version "1.0.5" - resolved "https://registry.yarnpkg.com/trough/-/trough-1.0.5.tgz#b8b639cefad7d0bb2abd37d433ff8293efa5f406" - integrity sha512-rvuRbTarPXmMb79SmzEp8aqXNKcK+y0XaB298IXueQ8I2PsrATcPBCSPyK/dDNa2iWOhKlfNnOjdAOTBU/nkFA== - -tslib@^2.0.3, tslib@^2.1.0, tslib@^2.4.0, tslib@^2.6.3: - version "2.8.0" - resolved "https://registry.yarnpkg.com/tslib/-/tslib-2.8.0.tgz#d124c86c3c05a40a91e6fdea4021bd31d377971b" - integrity sha512-jWVzBLplnCmoaTr13V9dYbiQ99wvZRd0vNWaDRg+aVYRcjDF3nDksxFDE/+fkXnKhpnUUkmx5pK/v8mCtLVqZA== - -tunnel-agent@^0.6.0: - version "0.6.0" - resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz#27a5dea06b36b04a0a9966774b290868f0fc40fd" - integrity sha512-McnNiV1l8RYeY8tBgEpuodCC1mLUdbSN+CYBL7kJsJNInOP8UjDDEwdk6Mw60vdLLrr5NHKZhMAOSrR2NZuQ+w== - dependencies: - safe-buffer "^5.0.1" - -type-fest@^0.20.2: - version "0.20.2" - resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.20.2.tgz#1bf207f4b28f91583666cb5fbd327887301cd5f4" - integrity sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ== - -type-fest@^2.5.0: - version "2.19.0" - resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-2.19.0.tgz#88068015bb33036a598b952e55e9311a60fd3a9b" - integrity sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA== - -type-is@~1.6.18: - version "1.6.18" - resolved "https://registry.yarnpkg.com/type-is/-/type-is-1.6.18.tgz#4e552cd05df09467dcbc4ef739de89f2cf37c131" - integrity sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g== - dependencies: - media-typer "0.3.0" - mime-types "~2.1.24" - -typedarray-to-buffer@^3.1.5: - version "3.1.5" - resolved "https://registry.yarnpkg.com/typedarray-to-buffer/-/typedarray-to-buffer-3.1.5.tgz#a97ee7a9ff42691b9f783ff1bc5112fe3fca9080" - integrity sha512-zdu8XMNEDepKKR+XYOXAVPtWui0ly0NtohUscw+UmaHiAWT8hrV1rr//H6V+0DvJ3OQ19S979M0laLfX8rm82Q== - dependencies: - is-typedarray "^1.0.0" - -typeface-roboto@^1.1.13: - version "1.1.13" - resolved "https://registry.yarnpkg.com/typeface-roboto/-/typeface-roboto-1.1.13.tgz#9c4517cb91e311706c74823e857b4bac9a764ae5" - integrity sha512-YXvbd3a1QTREoD+FJoEkl0VQNJoEjewR2H11IjVv4bp6ahuIcw0yyw/3udC4vJkHw3T3cUh85FTg8eWef3pSaw== - -ua-parser-js@^1.0.35: - version "1.0.39" - resolved "https://registry.yarnpkg.com/ua-parser-js/-/ua-parser-js-1.0.39.tgz#bfc07f361549bf249bd8f4589a4cccec18fd2018" - integrity sha512-k24RCVWlEcjkdOxYmVJgeD/0a1TiSpqLg+ZalVGV9lsnr4yqu0w7tX/x2xX6G4zpkgQnRf89lxuZ1wsbjXM8lw== - -undici-types@~6.19.2: - version "6.19.8" - resolved "https://registry.yarnpkg.com/undici-types/-/undici-types-6.19.8.tgz#35111c9d1437ab83a7cdc0abae2f26d88eda0a02" - integrity sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw== - -undici@^6.19.5: - version "6.20.1" - resolved "https://registry.yarnpkg.com/undici/-/undici-6.20.1.tgz#fbb87b1e2b69d963ff2d5410a40ffb4c9e81b621" - integrity sha512-AjQF1QsmqfJys+LXfGTNum+qw4S88CojRInG/6t31W/1fk6G59s92bnAvGz5Cmur+kQv2SURXEvvudLmbrE8QA== - -unherit@^1.0.4: - version "1.1.3" - resolved "https://registry.yarnpkg.com/unherit/-/unherit-1.1.3.tgz#6c9b503f2b41b262330c80e91c8614abdaa69c22" - integrity sha512-Ft16BJcnapDKp0+J/rqFC3Rrk6Y/Ng4nzsC028k2jdDII/rdZ7Wd3pPT/6+vIIxRagwRc9K0IUX0Ra4fKvw+WQ== - dependencies: - inherits "^2.0.0" - xtend "^4.0.0" - -unicode-canonical-property-names-ecmascript@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.1.tgz#cb3173fe47ca743e228216e4a3ddc4c84d628cc2" - integrity sha512-dA8WbNeb2a6oQzAQ55YlT5vQAWGV9WXOsi3SskE3bcCdM0P4SDd+24zS/OCacdRq5BkdsRj9q3Pg6YyQoxIGqg== - -unicode-match-property-ecmascript@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz#54fd16e0ecb167cf04cf1f756bdcc92eba7976c3" - integrity sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q== - dependencies: - unicode-canonical-property-names-ecmascript "^2.0.0" - unicode-property-aliases-ecmascript "^2.0.0" - -unicode-match-property-value-ecmascript@^2.1.0: - version "2.2.0" - resolved "https://registry.yarnpkg.com/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-2.2.0.tgz#a0401aee72714598f739b68b104e4fe3a0cb3c71" - integrity sha512-4IehN3V/+kkr5YeSSDDQG8QLqO26XpL2XP3GQtqwlT/QYSECAwFztxVHjlbh0+gjJ3XmNLS0zDsbgs9jWKExLg== - -unicode-property-aliases-ecmascript@^2.0.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.1.0.tgz#43d41e3be698bd493ef911077c9b131f827e8ccd" - integrity sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w== - -unified@9.2.0: - version "9.2.0" - resolved "https://registry.yarnpkg.com/unified/-/unified-9.2.0.tgz#67a62c627c40589edebbf60f53edfd4d822027f8" - integrity sha512-vx2Z0vY+a3YoTj8+pttM3tiJHCwY5UFbYdiWrwBEbHmK8pvsPj2rtAX2BFfgXen8T39CJWblWRDT4L5WGXtDdg== - dependencies: - bail "^1.0.0" - extend "^3.0.0" - is-buffer "^2.0.0" - is-plain-obj "^2.0.0" - trough "^1.0.0" - vfile "^4.0.0" - -unified@^9.2.2: - version "9.2.2" - resolved "https://registry.yarnpkg.com/unified/-/unified-9.2.2.tgz#67649a1abfc3ab85d2969502902775eb03146975" - integrity sha512-Sg7j110mtefBD+qunSLO1lqOEKdrwBFBrR6Qd8f4uwkhWNlbkaqwHse6e7QvD3AP/MNoJdEDLaf8OxYyoWgorQ== - dependencies: - bail "^1.0.0" - extend "^3.0.0" - is-buffer "^2.0.0" - is-plain-obj "^2.0.0" - trough "^1.0.0" - vfile "^4.0.0" - -unique-string@^2.0.0: - version "2.0.0" - resolved "https://registry.yarnpkg.com/unique-string/-/unique-string-2.0.0.tgz#39c6451f81afb2749de2b233e3f7c5e8843bd89d" - integrity sha512-uNaeirEPvpZWSgzwsPGtU2zVSTrn/8L5q/IexZmH0eH6SA73CmAA5U4GwORTxQAZs95TAXLNqeLoPPNO5gZfWg== - dependencies: - crypto-random-string "^2.0.0" - -unist-builder@2.0.3, unist-builder@^2.0.0: - version "2.0.3" - resolved "https://registry.yarnpkg.com/unist-builder/-/unist-builder-2.0.3.tgz#77648711b5d86af0942f334397a33c5e91516436" - integrity sha512-f98yt5pnlMWlzP539tPc4grGMsFaQQlP/vM396b00jngsiINumNmsY8rkXjfoi1c6QaM8nQ3vaGDuoKWbe/1Uw== - -unist-util-generated@^1.0.0: - version "1.1.6" - resolved "https://registry.yarnpkg.com/unist-util-generated/-/unist-util-generated-1.1.6.tgz#5ab51f689e2992a472beb1b35f2ce7ff2f324d4b" - integrity sha512-cln2Mm1/CZzN5ttGK7vkoGw+RZ8VcUH6BtGbq98DDtRGquAAOXig1mrBQYelOwMXYS8rK+vZDyyojSjp7JX+Lg== - -unist-util-is@^4.0.0: - version "4.1.0" - resolved "https://registry.yarnpkg.com/unist-util-is/-/unist-util-is-4.1.0.tgz#976e5f462a7a5de73d94b706bac1b90671b57797" - integrity sha512-ZOQSsnce92GrxSqlnEEseX0gi7GH9zTJZ0p9dtu87WRb/37mMPO2Ilx1s/t9vBHrFhbgweUwb+t7cIn5dxPhZg== - -unist-util-position@^3.0.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/unist-util-position/-/unist-util-position-3.1.0.tgz#1c42ee6301f8d52f47d14f62bbdb796571fa2d47" - integrity sha512-w+PkwCbYSFw8vpgWD0v7zRCl1FpY3fjDSQ3/N/wNd9Ffa4gPi8+4keqt99N3XW6F99t/mUzp2xAhNmfKWp95QA== - -unist-util-remove-position@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/unist-util-remove-position/-/unist-util-remove-position-2.0.1.tgz#5d19ca79fdba712301999b2b73553ca8f3b352cc" - integrity sha512-fDZsLYIe2uT+oGFnuZmy73K6ZxOPG/Qcm+w7jbEjaFcJgbQ6cqjs/eSPzXhsmGpAsWPkqZM9pYjww5QTn3LHMA== - dependencies: - unist-util-visit "^2.0.0" - -unist-util-remove@^2.0.0: - version "2.1.0" - resolved "https://registry.yarnpkg.com/unist-util-remove/-/unist-util-remove-2.1.0.tgz#b0b4738aa7ee445c402fda9328d604a02d010588" - integrity sha512-J8NYPyBm4baYLdCbjmf1bhPu45Cr1MWTm77qd9istEkzWpnN6O9tMsEbB2JhNnBCqGENRqEWomQ+He6au0B27Q== - dependencies: - unist-util-is "^4.0.0" - -unist-util-stringify-position@^2.0.0: - version "2.0.3" - resolved "https://registry.yarnpkg.com/unist-util-stringify-position/-/unist-util-stringify-position-2.0.3.tgz#cce3bfa1cdf85ba7375d1d5b17bdc4cada9bd9da" - integrity sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g== - dependencies: - "@types/unist" "^2.0.2" - -unist-util-visit-parents@^3.0.0: - version "3.1.1" - resolved "https://registry.yarnpkg.com/unist-util-visit-parents/-/unist-util-visit-parents-3.1.1.tgz#65a6ce698f78a6b0f56aa0e88f13801886cdaef6" - integrity sha512-1KROIZWo6bcMrZEwiH2UrXDyalAa0uqzWCxCJj6lPOvTve2WkfgCytoDTPaMnodXh1WrXOq0haVYHj99ynJlsg== - dependencies: - "@types/unist" "^2.0.0" - unist-util-is "^4.0.0" - -unist-util-visit@2.0.3, unist-util-visit@^2.0.0, unist-util-visit@^2.0.3: - version "2.0.3" - resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-2.0.3.tgz#c3703893146df47203bb8a9795af47d7b971208c" - integrity sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q== - dependencies: - "@types/unist" "^2.0.0" - unist-util-is "^4.0.0" - unist-util-visit-parents "^3.0.0" - -universalify@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/universalify/-/universalify-2.0.1.tgz#168efc2180964e6386d061e094df61afe239b18d" - integrity sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw== - -unpipe@1.0.0, unpipe@~1.0.0: - version "1.0.0" - resolved "https://registry.yarnpkg.com/unpipe/-/unpipe-1.0.0.tgz#b2bf4ee8514aae6165b4817829d21b2ef49904ec" - integrity sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ== - -update-browserslist-db@^1.1.1: - version "1.1.1" - resolved "https://registry.yarnpkg.com/update-browserslist-db/-/update-browserslist-db-1.1.1.tgz#80846fba1d79e82547fb661f8d141e0945755fe5" - integrity sha512-R8UzCaa9Az+38REPiJ1tXlImTJXlVfgHZsglwBD/k6nj76ctsH1E3q4doGrukiLQd3sGQYu56r5+lo5r94l29A== - dependencies: - escalade "^3.2.0" - picocolors "^1.1.0" - -update-notifier@^5.1.0: - version "5.1.0" - resolved "https://registry.yarnpkg.com/update-notifier/-/update-notifier-5.1.0.tgz#4ab0d7c7f36a231dd7316cf7729313f0214d9ad9" - integrity sha512-ItnICHbeMh9GqUy31hFPrD1kcuZ3rpxDZbf4KUDavXwS0bW5m7SLbDQpGX3UYr072cbrF5hFUs3r5tUsPwjfHw== - dependencies: - boxen "^5.0.0" - chalk "^4.1.0" - configstore "^5.0.1" - has-yarn "^2.1.0" - import-lazy "^2.1.0" - is-ci "^2.0.0" - is-installed-globally "^0.4.0" - is-npm "^5.0.0" - is-yarn-global "^0.3.0" - latest-version "^5.1.0" - pupa "^2.1.1" - semver "^7.3.4" - semver-diff "^3.1.1" - xdg-basedir "^4.0.0" - -uri-js@^4.2.2: - version "4.4.1" - resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.4.1.tgz#9b1a52595225859e55f669d928f88c6c57f2a77e" - integrity sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg== - dependencies: - punycode "^2.1.0" - -url-loader@^4.1.1: - version "4.1.1" - resolved "https://registry.yarnpkg.com/url-loader/-/url-loader-4.1.1.tgz#28505e905cae158cf07c92ca622d7f237e70a4e2" - integrity sha512-3BTV812+AVHHOJQO8O5MkWgZ5aosP7GnROJwvzLS9hWDj00lZ6Z0wNak423Lp9PBZN05N+Jk/N5Si8jRAlGyWA== - dependencies: - loader-utils "^2.0.0" - mime-types "^2.1.27" - schema-utils "^3.0.0" - -url-parse-lax@^3.0.0: - version "3.0.0" - resolved "https://registry.yarnpkg.com/url-parse-lax/-/url-parse-lax-3.0.0.tgz#16b5cafc07dbe3676c1b1999177823d6503acb0c" - integrity sha512-NjFKA0DidqPa5ciFcSrXnAltTtzz84ogy+NebPvfEgAck0+TNg4UJ4IN+fB7zRZfbgUf0syOo9MDxFkDSMuFaQ== - dependencies: - prepend-http "^2.0.0" - -use-composed-ref@^1.3.0: - version "1.3.0" - resolved "https://registry.yarnpkg.com/use-composed-ref/-/use-composed-ref-1.3.0.tgz#3d8104db34b7b264030a9d916c5e94fbe280dbda" - integrity sha512-GLMG0Jc/jiKov/3Ulid1wbv3r54K9HlMW29IWcDFPEqFkSO2nS0MuefWgMJpeHQ9YJeXDL3ZUF+P3jdXlZX/cQ== - -use-isomorphic-layout-effect@^1.1.1: - version "1.1.2" - resolved "https://registry.yarnpkg.com/use-isomorphic-layout-effect/-/use-isomorphic-layout-effect-1.1.2.tgz#497cefb13d863d687b08477d9e5a164ad8c1a6fb" - integrity sha512-49L8yCO3iGT/ZF9QttjwLF/ZD9Iwto5LnH5LmEdk/6cFmXddqi2ulF0edxTwjj+7mqvpVVGQWvbXZdn32wRSHA== - -use-latest@^1.2.1: - version "1.2.1" - resolved "https://registry.yarnpkg.com/use-latest/-/use-latest-1.2.1.tgz#d13dfb4b08c28e3e33991546a2cee53e14038cf2" - integrity sha512-xA+AVm/Wlg3e2P/JiItTziwS7FK92LWrDB0p+hgXloIMuVCeJJ8v6f0eeHyPZaJrM+usM1FkFfbNCrJGs8A/zw== - dependencies: - use-isomorphic-layout-effect "^1.1.1" - -use-sync-external-store@^1.2.0: - version "1.2.2" - resolved "https://registry.yarnpkg.com/use-sync-external-store/-/use-sync-external-store-1.2.2.tgz#c3b6390f3a30eba13200d2302dcdf1e7b57b2ef9" - integrity sha512-PElTlVMwpblvbNqQ82d2n6RjStvdSoNe9FG28kNfz3WiXilJm4DdNkEzRhCZuIDwY8U08WVihhGR5iRqAwfDiw== - -util-deprecate@^1.0.1, util-deprecate@^1.0.2, util-deprecate@~1.0.1: - version "1.0.2" - resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf" - integrity sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw== - -utila@~0.4: - version "0.4.0" - resolved "https://registry.yarnpkg.com/utila/-/utila-0.4.0.tgz#8a16a05d445657a3aea5eecc5b12a4fa5379772c" - integrity sha512-Z0DbgELS9/L/75wZbro8xAnT50pBVFQZ+hUEueGDU5FN51YSCYM+jdxsfCiHjwNP/4LCDD0i/graKpeBnOXKRA== - -utility-types@^3.10.0: - version "3.11.0" - resolved "https://registry.yarnpkg.com/utility-types/-/utility-types-3.11.0.tgz#607c40edb4f258915e901ea7995607fdf319424c" - integrity sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw== - -utils-merge@1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.1.tgz#9f95710f50a267947b2ccc124741c1028427e713" - integrity sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA== - -uuid@^8.3.2: - version "8.3.2" - resolved "https://registry.yarnpkg.com/uuid/-/uuid-8.3.2.tgz#80d5b5ced271bb9af6c445f21a1a04c606cefbe2" - integrity sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg== - -value-equal@^1.0.1: - version "1.0.1" - resolved "https://registry.yarnpkg.com/value-equal/-/value-equal-1.0.1.tgz#1e0b794c734c5c0cade179c437d356d931a34d6c" - integrity sha512-NOJ6JZCAWr0zlxZt+xqCHNTEKOsrks2HQd4MqhP1qy4z1SkbEP467eNx6TgDKXMvUOb+OENfJCZwM+16n7fRfw== - -vary@~1.1.2: - version "1.1.2" - resolved "https://registry.yarnpkg.com/vary/-/vary-1.1.2.tgz#2299f02c6ded30d4a5961b0b9f74524a18f634fc" - integrity sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg== - -vfile-location@^3.0.0, vfile-location@^3.2.0: - version "3.2.0" - resolved "https://registry.yarnpkg.com/vfile-location/-/vfile-location-3.2.0.tgz#d8e41fbcbd406063669ebf6c33d56ae8721d0f3c" - integrity sha512-aLEIZKv/oxuCDZ8lkJGhuhztf/BW4M+iHdCwglA/eWc+vtuRFJj8EtgceYFX4LRjOhCAAiNHsKGssC6onJ+jbA== - -vfile-message@^2.0.0: - version "2.0.4" - resolved "https://registry.yarnpkg.com/vfile-message/-/vfile-message-2.0.4.tgz#5b43b88171d409eae58477d13f23dd41d52c371a" - integrity sha512-DjssxRGkMvifUOJre00juHoP9DPWuzjxKuMDrhNbk2TdaYYBNMStsNhEOt3idrtI12VQYM/1+iM0KOzXi4pxwQ== - dependencies: - "@types/unist" "^2.0.0" - unist-util-stringify-position "^2.0.0" - -vfile@^4.0.0: - version "4.2.1" - resolved "https://registry.yarnpkg.com/vfile/-/vfile-4.2.1.tgz#03f1dce28fc625c625bc6514350fbdb00fa9e624" - integrity sha512-O6AE4OskCG5S1emQ/4gl8zK586RqA3srz3nfK/Viy0UPToBc5Trp9BVFb1u0CjsKrAWwnpr4ifM/KBXPWwJbCA== - dependencies: - "@types/unist" "^2.0.0" - is-buffer "^2.0.0" - unist-util-stringify-position "^2.0.0" - vfile-message "^2.0.0" - -wait-on@^6.0.1: - version "6.0.1" - resolved "https://registry.yarnpkg.com/wait-on/-/wait-on-6.0.1.tgz#16bbc4d1e4ebdd41c5b4e63a2e16dbd1f4e5601e" - integrity sha512-zht+KASY3usTY5u2LgaNqn/Cd8MukxLGjdcZxT2ns5QzDmTFc4XoWBgC+C/na+sMRZTuVygQoMYwdcVjHnYIVw== - dependencies: - axios "^0.25.0" - joi "^17.6.0" - lodash "^4.17.21" - minimist "^1.2.5" - rxjs "^7.5.4" - -watchpack@^2.4.1: - version "2.4.2" - resolved "https://registry.yarnpkg.com/watchpack/-/watchpack-2.4.2.tgz#2feeaed67412e7c33184e5a79ca738fbd38564da" - integrity sha512-TnbFSbcOCcDgjZ4piURLCbJ3nJhznVh9kw6F6iokjiFPl8ONxe9A6nMDVXDiNbrSfLILs6vB07F7wLBrwPYzJw== - dependencies: - glob-to-regexp "^0.4.1" - graceful-fs "^4.1.2" - -wbuf@^1.1.0, wbuf@^1.7.3: - version "1.7.3" - resolved "https://registry.yarnpkg.com/wbuf/-/wbuf-1.7.3.tgz#c1d8d149316d3ea852848895cb6a0bfe887b87df" - integrity sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA== - dependencies: - minimalistic-assert "^1.0.0" - -web-namespaces@^1.0.0: - version "1.1.4" - resolved "https://registry.yarnpkg.com/web-namespaces/-/web-namespaces-1.1.4.tgz#bc98a3de60dadd7faefc403d1076d529f5e030ec" - integrity sha512-wYxSGajtmoP4WxfejAPIr4l0fVh+jeMXZb08wNc0tMg6xsfZXj3cECqIK0G7ZAqUq0PP8WlMDtaOGVBTAWztNw== - -webidl-conversions@^3.0.0: - version "3.0.1" - resolved "https://registry.yarnpkg.com/webidl-conversions/-/webidl-conversions-3.0.1.tgz#24534275e2a7bc6be7bc86611cc16ae0a5654871" - integrity sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ== - -webpack-bundle-analyzer@^4.5.0: - version "4.10.2" - resolved "https://registry.yarnpkg.com/webpack-bundle-analyzer/-/webpack-bundle-analyzer-4.10.2.tgz#633af2862c213730be3dbdf40456db171b60d5bd" - integrity sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw== - dependencies: - "@discoveryjs/json-ext" "0.5.7" - acorn "^8.0.4" - acorn-walk "^8.0.0" - commander "^7.2.0" - debounce "^1.2.1" - escape-string-regexp "^4.0.0" - gzip-size "^6.0.0" - html-escaper "^2.0.2" - opener "^1.5.2" - picocolors "^1.0.0" - sirv "^2.0.3" - ws "^7.3.1" - -webpack-dev-middleware@^5.3.4: - version "5.3.4" - resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-5.3.4.tgz#eb7b39281cbce10e104eb2b8bf2b63fce49a3517" - integrity sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q== - dependencies: - colorette "^2.0.10" - memfs "^3.4.3" - mime-types "^2.1.31" - range-parser "^1.2.1" - schema-utils "^4.0.0" - -webpack-dev-server@^4.9.3: - version "4.15.2" - resolved "https://registry.yarnpkg.com/webpack-dev-server/-/webpack-dev-server-4.15.2.tgz#9e0c70a42a012560860adb186986da1248333173" - integrity sha512-0XavAZbNJ5sDrCbkpWL8mia0o5WPOd2YGtxrEiZkBK9FjLppIUK2TgxK6qGD2P3hUXTJNNPVibrerKcx5WkR1g== - dependencies: - "@types/bonjour" "^3.5.9" - "@types/connect-history-api-fallback" "^1.3.5" - "@types/express" "^4.17.13" - "@types/serve-index" "^1.9.1" - "@types/serve-static" "^1.13.10" - "@types/sockjs" "^0.3.33" - "@types/ws" "^8.5.5" - ansi-html-community "^0.0.8" - bonjour-service "^1.0.11" - chokidar "^3.5.3" - colorette "^2.0.10" - compression "^1.7.4" - connect-history-api-fallback "^2.0.0" - default-gateway "^6.0.3" - express "^4.17.3" - graceful-fs "^4.2.6" - html-entities "^2.3.2" - http-proxy-middleware "^2.0.3" - ipaddr.js "^2.0.1" - launch-editor "^2.6.0" - open "^8.0.9" - p-retry "^4.5.0" - rimraf "^3.0.2" - schema-utils "^4.0.0" - selfsigned "^2.1.1" - serve-index "^1.9.1" - sockjs "^0.3.24" - spdy "^4.0.2" - webpack-dev-middleware "^5.3.4" - ws "^8.13.0" - -webpack-merge@^5.8.0: - version "5.10.0" - resolved "https://registry.yarnpkg.com/webpack-merge/-/webpack-merge-5.10.0.tgz#a3ad5d773241e9c682803abf628d4cd62b8a4177" - integrity sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA== - dependencies: - clone-deep "^4.0.1" - flat "^5.0.2" - wildcard "^2.0.0" - -webpack-sources@^3.2.2, webpack-sources@^3.2.3: - version "3.2.3" - resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-3.2.3.tgz#2d4daab8451fd4b240cc27055ff6a0c2ccea0cde" - integrity sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w== - -webpack@^5.73.0: - version "5.95.0" - resolved "https://registry.yarnpkg.com/webpack/-/webpack-5.95.0.tgz#8fd8c454fa60dad186fbe36c400a55848307b4c0" - integrity sha512-2t3XstrKULz41MNMBF+cJ97TyHdyQ8HCt//pqErqDvNjU9YQBnZxIHa11VXsi7F3mb5/aO2tuDxdeTPdU7xu9Q== - dependencies: - "@types/estree" "^1.0.5" - "@webassemblyjs/ast" "^1.12.1" - "@webassemblyjs/wasm-edit" "^1.12.1" - "@webassemblyjs/wasm-parser" "^1.12.1" - acorn "^8.7.1" - acorn-import-attributes "^1.9.5" - browserslist "^4.21.10" - chrome-trace-event "^1.0.2" - enhanced-resolve "^5.17.1" - es-module-lexer "^1.2.1" - eslint-scope "5.1.1" - events "^3.2.0" - glob-to-regexp "^0.4.1" - graceful-fs "^4.2.11" - json-parse-even-better-errors "^2.3.1" - loader-runner "^4.2.0" - mime-types "^2.1.27" - neo-async "^2.6.2" - schema-utils "^3.2.0" - tapable "^2.1.1" - terser-webpack-plugin "^5.3.10" - watchpack "^2.4.1" - webpack-sources "^3.2.3" - -webpackbar@^5.0.2: - version "5.0.2" - resolved "https://registry.yarnpkg.com/webpackbar/-/webpackbar-5.0.2.tgz#d3dd466211c73852741dfc842b7556dcbc2b0570" - integrity sha512-BmFJo7veBDgQzfWXl/wwYXr/VFus0614qZ8i9znqcl9fnEdiVkdbi0TedLQ6xAK92HZHDJ0QmyQ0fmuZPAgCYQ== - dependencies: - chalk "^4.1.0" - consola "^2.15.3" - pretty-time "^1.1.0" - std-env "^3.0.1" - -websocket-driver@>=0.5.1, websocket-driver@^0.7.4: - version "0.7.4" - resolved "https://registry.yarnpkg.com/websocket-driver/-/websocket-driver-0.7.4.tgz#89ad5295bbf64b480abcba31e4953aca706f5760" - integrity sha512-b17KeDIQVjvb0ssuSDF2cYXSg2iztliJ4B9WdsuB6J952qCPKmnVq4DyW5motImXHDC1cBT/1UezrJVsKw5zjg== - dependencies: - http-parser-js ">=0.5.1" - safe-buffer ">=5.1.0" - websocket-extensions ">=0.1.1" - -websocket-extensions@>=0.1.1: - version "0.1.4" - resolved "https://registry.yarnpkg.com/websocket-extensions/-/websocket-extensions-0.1.4.tgz#7f8473bc839dfd87608adb95d7eb075211578a42" - integrity sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg== - -whatwg-encoding@^3.1.1: - version "3.1.1" - resolved "https://registry.yarnpkg.com/whatwg-encoding/-/whatwg-encoding-3.1.1.tgz#d0f4ef769905d426e1688f3e34381a99b60b76e5" - integrity sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ== - dependencies: - iconv-lite "0.6.3" - -whatwg-mimetype@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/whatwg-mimetype/-/whatwg-mimetype-4.0.0.tgz#bc1bf94a985dc50388d54a9258ac405c3ca2fc0a" - integrity sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg== - -whatwg-url@^5.0.0: - version "5.0.0" - resolved "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-5.0.0.tgz#966454e8765462e37644d3626f6742ce8b70965d" - integrity sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw== - dependencies: - tr46 "~0.0.3" - webidl-conversions "^3.0.0" - -which@^1.3.1: - version "1.3.1" - resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a" - integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ== - dependencies: - isexe "^2.0.0" - -which@^2.0.1: - version "2.0.2" - resolved "https://registry.yarnpkg.com/which/-/which-2.0.2.tgz#7c6a8dd0a636a0327e10b59c9286eee93f3f51b1" - integrity sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA== - dependencies: - isexe "^2.0.0" - -widest-line@^3.1.0: - version "3.1.0" - resolved "https://registry.yarnpkg.com/widest-line/-/widest-line-3.1.0.tgz#8292333bbf66cb45ff0de1603b136b7ae1496eca" - integrity sha512-NsmoXalsWVDMGupxZ5R08ka9flZjjiLvHVAWYOKtiKM8ujtZWr9cRffak+uSE48+Ob8ObalXpwyeUiyDD6QFgg== - dependencies: - string-width "^4.0.0" - -widest-line@^4.0.1: - version "4.0.1" - resolved "https://registry.yarnpkg.com/widest-line/-/widest-line-4.0.1.tgz#a0fc673aaba1ea6f0a0d35b3c2795c9a9cc2ebf2" - integrity sha512-o0cyEG0e8GPzT4iGHphIOh0cJOV8fivsXxddQasHPHfoZf1ZexrfeA21w2NaEN1RHE+fXlfISmOE8R9N3u3Qig== - dependencies: - string-width "^5.0.1" - -wildcard@^2.0.0: - version "2.0.1" - resolved "https://registry.yarnpkg.com/wildcard/-/wildcard-2.0.1.tgz#5ab10d02487198954836b6349f74fff961e10f67" - integrity sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ== - -wrap-ansi@^7.0.0: - version "7.0.0" - resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-7.0.0.tgz#67e145cff510a6a6984bdf1152911d69d2eb9e43" - integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q== - dependencies: - ansi-styles "^4.0.0" - string-width "^4.1.0" - strip-ansi "^6.0.0" - -wrap-ansi@^8.0.1: - version "8.1.0" - resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-8.1.0.tgz#56dc22368ee570face1b49819975d9b9a5ead214" - integrity sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ== - dependencies: - ansi-styles "^6.1.0" - string-width "^5.0.1" - strip-ansi "^7.0.1" - -wrappy@1: - version "1.0.2" - resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f" - integrity sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ== - -write-file-atomic@^3.0.0: - version "3.0.3" - resolved "https://registry.yarnpkg.com/write-file-atomic/-/write-file-atomic-3.0.3.tgz#56bd5c5a5c70481cd19c571bd39ab965a5de56e8" - integrity sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q== - dependencies: - imurmurhash "^0.1.4" - is-typedarray "^1.0.0" - signal-exit "^3.0.2" - typedarray-to-buffer "^3.1.5" - -ws@^7.3.1: - version "7.5.10" - resolved "https://registry.yarnpkg.com/ws/-/ws-7.5.10.tgz#58b5c20dc281633f6c19113f39b349bd8bd558d9" - integrity sha512-+dbF1tHwZpXcbOJdVOkzLDxZP1ailvSxM6ZweXTegylPny803bFhA+vqBYw4s31NSAk4S2Qz+AKXK9a4wkdjcQ== - -ws@^8.13.0: - version "8.18.0" - resolved "https://registry.yarnpkg.com/ws/-/ws-8.18.0.tgz#0d7505a6eafe2b0e712d232b42279f53bc289bbc" - integrity sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw== - -xdg-basedir@^4.0.0: - version "4.0.0" - resolved "https://registry.yarnpkg.com/xdg-basedir/-/xdg-basedir-4.0.0.tgz#4bc8d9984403696225ef83a1573cbbcb4e79db13" - integrity sha512-PSNhEJDejZYV7h50BohL09Er9VaIefr2LMAf3OEmpCkjOi34eYyQYAXUTjEQtZJTKcF0E2UKTh+osDLsgNim9Q== - -xml-js@^1.6.11: - version "1.6.11" - resolved "https://registry.yarnpkg.com/xml-js/-/xml-js-1.6.11.tgz#927d2f6947f7f1c19a316dd8eea3614e8b18f8e9" - integrity sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g== - dependencies: - sax "^1.2.4" - -xtend@^4.0.0, xtend@^4.0.1: - version "4.0.2" - resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.2.tgz#bb72779f5fa465186b1f438f674fa347fdb5db54" - integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ== - -yallist@^3.0.2: - version "3.1.1" - resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.1.1.tgz#dbb7daf9bfd8bac9ab45ebf602b8cbad0d5d08fd" - integrity sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g== - -yaml@^1.10.0, yaml@^1.10.2, yaml@^1.7.2: - version "1.10.2" - resolved "https://registry.yarnpkg.com/yaml/-/yaml-1.10.2.tgz#2301c5ffbf12b467de8da2333a459e29e7920e4b" - integrity sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg== - -yocto-queue@^0.1.0: - version "0.1.0" - resolved "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-0.1.0.tgz#0294eb3dee05028d31ee1a5fa2c556a6aaf10a1b" - integrity sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q== - -zwitch@^1.0.0: - version "1.0.5" - resolved "https://registry.yarnpkg.com/zwitch/-/zwitch-1.0.5.tgz#d11d7381ffed16b742f6af7b3f223d5cd9fe9920" - integrity sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw==